Consider aligning markdown support with snapcraft.io

[Lukewh]

Is there an existing issue for this?

• I have searched the existing issues and found none matching what I'm reporting.

Is the feature related to a problem or existing issue?

For publishers, there is a mismatch between rendered descriptions.
canonical/snapcraft.io#4740

Describe the feature, why the feature matters to you, and what benefits the feature will bring about.

I'd like us to be consistent and hold hands and be happy while we sing the song of snap descriptions.

Describe any alternatives you've considered.

I've considered expanding the markdown implementation on snapcraft.io, but then I re-read https://forum.snapcraft.io/t/use-of-markdown-in-snap-metadata-summary-description/2128/44 and decide I want to be happy not sad.

Additional context

I recognise this is less than ideal, and perhaps it's something we could talk about on a future sprint, but for now, I think it's best to align on a pre-agreed subset before the flame war discussion is opened up again.

[d-loose]

We're using flutter_markdown to display the snap descriptions. By default it uses GitHub flavored markdown, but supports other options as well.

For publishers, there is a mismatch between rendered descriptions. canonical/snapcraft.io#4740

Having a quick look at the snap packages mentioned in that issue, I don't see any notable differences between snapcraft.io and the app center. The one-line summary above the description is not part of the markdown content and displayed differently according to the Figma designs.

snap	snapcraft.io	app center
notesnook
joplin-desktop