Playground features #117
Description
This is a follow-up issue for #9 to discuss the list of features proposed for the online playgound and its integration with the docs website.
Some of these features require extra UI elements (like buttons and dropdown list) that should ideally match the website UI. So, I think we should delay their implementation till the docs website is available.
- Share URLs (demo)
- Select Ripple version (demo)
- Add a list of examples that can be loaded in the playground (related Add examples #64)
- Docs: embed interactive playgrounds or open code snippets in playground (see examples)
- Allow importing npm modules and external ripple components
- Should we enable (by default) using SCSS, Tailwind CSS, importing stylesheets, etc in components? (demo: SCSS, Tailwind CSS, import stylesheets)
- Editor intellisense (autocomplete, hover info, error checks, etc), similar to Vue implementation (also uses volar)
- Preview PRs (Preview PRs in playground #116)
What else?
Please let me know what you think.