refactor: markdown

[flornkm]

This PR introduces a new markdown rendering enabling more interop. between e.g. GitHub Readmes, Marketplace documentations, and can be used in further use cases. See #1302

[changeset-bot]

⚠️ No Changeset found

Latest commit: 57b0900

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[samuelstroschein]

@floriandwt can you copy the pacakge-lock.json fom the main branch, delete the package-lock.json in this branch, and run npm run ci afterwards?

the lock file got overwritten or something leading to "15.000 line of change"

[samuelstroschein]

Overall as expected. One remark:

The mermaid feature seems to introduce a lot (too much) complexity. I assume that you felt at one point "hm, adding a playwright dependency doesn't seem right". Speak up and discuss with your team members. Your gut feeling is usually right. The engineering goal is not to support any feature but to support a feature that is worth it given the compexity it introduces. Otherwise, the project will suffer from unreasonable long term maintainence burden(s).

[flornkm]

@samuelstroschein almost all remaining should be solved now, I will finish getting rid of mermaid on Monday and move the new tableOfContents function to the client then.

Edit: + introduce Gallery, but this is a smaller task anyway.