Feedback on Main Content UI & Macros

Hello! :waving_hand: Some more feedback on Cristal in coming… :star_struck:


If I see that the discussion gets too focused on any of the following, I will start separate discussions for the respective issues.

Here is what this feedback covers:

  1. Spacing between paragraphs - CSS
  2. User, Pretty Name - low-hanging fruit
  3. Table Notes & Issues - bug? + low-medium improvement
  4. Escaping a macro - low-hanging fruit
  5. List item spacing - CSS
  6. Link menu waiting time - CSS
  7. Quote UI - CSS
  8. Empty lines not preserved - bug?
  9. Added spacing in view mode - bug?
  10. Just jump in edit mode, no more button - big change, started separate discussion
  11. Toggle headings, UX change - maybe big change, started separate discussion
  12. Code block confusing behaviour - bug + small change? separate discussion

#1 Spacing between paragraphs


The page’s content needs to have more whitespace/breathing space so the structure is clearer.

I would increase the margin-top of any heading so there’s a clearer distinction between sections. Notion seems to make that margin = 2 * an enter’s created space (this is just an approximation, but seems right).

#2 User - Pretty Name


I shouldn’t appear as XWiki.AdinaMilica, I should appear as Adina Milica with my name linked to afuture profile page.

#3 Table Notes & Issues


Full-width by default | When adding a table to the page, the table should appear by default in full-width in edit mode. I assume that most people would expect this.

Bug? Even when trying to make the table full width, it doesn’t stay that way oce saved. Ths cells resize to fit content, it seems like.

Bordered The default look for tables should be bordered (in view mode too)

#4 Escaping a macro


Like in Notion, after any macro, there should be an automatic line available so the user can exit macros without any issues.

#5 List item spacing


Every list item should have a bit more margin-bottom than it has so the delimitation between items is more clear. Notion does the same (just a few pixels make a difference) with padding-top and padding-bottom. See Cristal in the first pic and Notion in the second.

In the last version of Cristal this spacing is better, but can be made a bit more obvious.

#6 Link Hovering


Waiting time I think the waiting time on the menu that opens when hovering on a link is too small. It should just stay on the screen while the user hovers on the link.

#7 Quote UI


I’d like a bit more vertical padding and margin top/bottom to the quote macro.

#8 Empty lines in edit mode


Empty lines in edit mode should be preserved in view mode. I always found this weird in XWiki and now in Cristal.

#9 Spacing added in view mode (Shoelace)


In edit mode there is a certain spacing which is far smaller than in view mode.

It should be consistent in every mode.

#10 Toggle Headings - UX change


I will link this to a separate discussion.

#11 Just jump in edit mode, no more button :face_holding_back_tears:


I will link this to a separate discussion.

12 Code block - confusing behaviour


I will link this to a separate discussion.

What do you think?

We rely on the default values of the design systems. So I wouldn’t change that unless we find a way to do it in a generic way.
+1 to report the improvement on Jira to keep track of it.

Yes, this is a planned but undocumented improvement. You can create the corresponding improvement issue on Jira.

I would go for this choice only if the table is also behaving the same in view mode.

This is known; we are planning to remove all UI interactions that are not supported in view move (here, for instance, markdown does not support persisting columns/table sizes, so those changes are lost on save).

+1 to report it on Jira. Here too, we’ll only apply the change if we find a generic enough approach.

I’m not sure to understand that one, but feel free to report it on Jira.

why?

You can report it as well. I’m expecting that one to lead to some discussions since some users might expect the extraneous spaces to be ignored by default.

Yes, sounds like a bug. You can report it.