Skip to main content

Tables have been pretty unwieldy for us since the new editor went live. We love that we can now include lists within tables and resize the columns more easily. But you can no longer specify the size of the table you wish to add to the card (e.g. 3 columns by 5 rows). Tables default to two rows only. You cannot click to add, say, 5 additional rows at one time. Instead each row and column must be added individually. This can be quite time consuming when you are creating new table content. I know when you copy>paste from a spreadsheet it automatically adds enough rows or columns for that content, but we create a lot of things from scratch and this update has made that more cumbersome. 

Side request - it would be great if you could select a column in a table to apply formatting. Today you have to select each cell in a column and format them individually.

Thanks!

Thanks for posting Abbey, I’ve subscribed 😄

Agreed. It would be great if the Guru product team would spend some time on enhancing the editor experience instead of chasing shiny objects like AI features.

For Guru to succeed within an organization people have to adopt it. To adopt it, content needs to exist within in. For content to exist within it, people have to make it. And for people to make it, it needs to be easy and useful to do so

i.e., imagine if creating content in Guru cards was like creating content in a Notion page. How amazing would it be to have an editor that *just works.* An editor that:

  • Doesn’t bug out half the time when you type markdown `#` for heading levels.
  • Supports the full range of heading levels (H1 through H6).
  • Doesn’t bug out when you try to unhighlight something.
  • Doesn’t produce an abhorrent line height above and below a horizontal rule.
  • Can highlight text in more than one color.
  • Can adjust table row height.
  • Supports table header formatting.
  • Supports rearranging table rows (move up and move down).
  • Uses the standardized syntax for referencing an internal document (`me`).
  • Supports rich callout elements that support a callout header in addition to call body text.
  • Supports proper callout elements with icons/emojis that don’t ruin the alignment of multiline callout text.
  • Supports inline code styling that isn’t hard to see because the background gray is so light it might as well not even be there.
  • Supports caption text for images.
Terms & ConditionsCookie settings