Gramps Web Blog Rendering

Gramps Web
1

I create blogs in Gramps Desktop and sync to Gramps Web - this works fine.
But if I in the Note editor make a header using e.g. a larger font and bold, then when this is displayed in Gramps Web the header line is with very small characters.
Below screenshots of editing in Gramps Desktop and displaying in Gramps Web.

Editing a blog note
Editing a blog note1682Ă—1036 263 KB

Displaying a blog
Displaying a blog1752Ă—988 53.2 KB

2

Tried to use both markdown and html headers in the note, but this is ignored.

Note with markdown and html headers
Note with markdown and html headers1626Ă—862 27.5 KB

3

Yes, that’s currently the intentional behaviour.

I love Markdown and use it for everything outside Gramps, so I did think about adding partial Markdown support to Gramps Web, but it breaks compatibility with Gramps Desktop and it’s painful to have to work with two incompatible note formats in parallel.

So we’re stuck with Gramps’ own styled text format. What’s good about it is that it’s unambiguous (as opposed to Markdown’s dialects/flavours). What’s bad is that it encodes style, not intent. That’s exactly what bytes you here: you choose a 14 pt font for the sub-heading because it looks “big” compared to Gramps Desktop’s default font; but in the Gramps Web blog detail view, 14 pt is smaller than the body text.

This mismatch is also what drove Gramps Web’s current design decisions: when authoring notes, only boldface/italic/underline and links are supported via the web interface, since they render correctly everywhere. Color, font size and font face cannot be edited via the UI - just what Markdown doesn’t allow either.

For display, Gramps Web respects color and font size (with the confusing side effect you noticed) but ignores font face, since it’s system dependent.

In practice, what I do in blog posts is use a single line of boldfaced or italic text for subheadings. I feel it works well enough and is not unlike some books or magazines style it. I agree proper semantic headings would be better, but that would be an upstream change in Gramps and would need to be supported by the GUI editor, too.

4

Thanks for the clarification.
Wish that the Note editor had used same formatting (markdown) as the discourse editor.

5

Good news, the next version will support *, **, _ and __ for italic and bold, ==…== for highlight and even Obsidian/Wiki-like [[…]] for opening the link dialog.