Different rendering in markdown preview and browser

[ghag]

As a nextcloud beginner I'm not sure if this is my own handling error...
Some markups are correctly displayed in markdown preview, but not in browser's window and vice versa. I've marked two distinctive examples in the screenshots: a picture from /assets folder (red) and a prezi video-link (yellow).

[PhrozenByte]

Pico CMS for Nextcloud v1.0.0 is arriving and I'm currently working through some old issues that can be resolved before releasing the app's first stable release. See help.nextcloud.com for more info.

Unfortunately we can't really do anything about this. Perhaps the most serious problem of Markdown is, that it never really was standardized. The only common denominator of all Markdown parsers is a descriptive document from John Gruber and his original Markdown.pl parser as some sort of a reference parser. His description of Markdown is very ambiguous, partially even contradicts itself and even the reference parser violates its own rules in many ways. The result is, that all Markdown parsers behave more or less differently - especially in cases which aren't really covered by John Gruber's document or in cases in which Markdown.pl produces impractical results.

There were some efforts being made to unify the Markdown syntax (called CommonMark), but only very few actually adapted CommonMark yet. So the issue persists...

I'll keep this issue open for future consideration.

[doftnet]

For whatever it's worth, my approach to this has been to create all my sites in a /sites folder such that the base URL of the site matches the Nextcloud path - i.e my test site exists in the Nextcloud folder /sites/test and has a base URL of /sites/test. Within the editor, I don't use the %base_url% substitution, but rather the full Nextcloud path for the file. it renders fine in the preview and on the site.

This is obviously a workaround to make the markdown editor play nice with both Nextcloud and Pico CMS, but I think the solution for this problem would probably require some modifications to the markdown editor rather than Pico in terms of telling the editor what the %base_url% should translate to.