If you really want to stop using Markdown to write with, then the best solution will be to use a proper conversion tool to turn these into word processing documents, such as DOCX or ODT, and then import that into Scrivener. I don't think (without plugins anyway) that Obsidian has any way of making this easier, but a good general purpose tool for this is Pandoc. Source: over 2 years ago

There is still some value in understanding aesthetic trends, it’s good to make sure your components and interactions are consistent with patterns people may be already familiar with. I like to nerd out on Design Systems Repo to view open source design system documentation. You can see how companies style their components, as well as how they work “under the hood” so to speak. I then like to compare it to their... Source: over 1 year ago

This is the site I use to browse design systems: Https://designsystemsrepo.com/. Source: over 1 year ago

Yup this. Also https://designsystemsrepo.com is worth a flick through as they have some interesting alternate takes. Source: over 1 year ago

Design Systems Repo - A frequently updated collection of Design System examples, articles, tools and talks https://designsystemsrepo.com/ Awesome Design Systems https://github.com/alexpate/awesome-design-systems. - Source: Hacker News / almost 2 years ago

So just to add to this source, you can also look around on https://designsystemsrepo.com They have a large collection of actual used design systems from companies around the world. Often times, their design systems are open to anyone. I’m not sure about the component library, but you can always check and see if they have a link. Source: over 2 years ago