New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more examples #479
Comments
Examples could help, another approach, taken in #428 but could also be applied to current is using Storybook to create interactive examples. |
Could also work! I definitely don’t want it exhaustive! Somewhere in between might be manageable in storybook. Where’s the line? What should go where? |
I think initially putting things in the readme is a good start.
Likewise, usually 5-25 examples in a storybook can cover the vast majority of use cases.
I usually would put a basic example in the readme, plus maybe one with an extension, and the rest would go in storybook. |
I’m assuming GFM to be the most used plugin, so it can probably go in the main Use example. We can skip footnotes as it’s very similar. Math is interesting because it means a syntax extension and handling nodes. Syntax highlighting is interesting because you’re dealing with potentially 500kb of JS. And can go with the plugin or react-syntax-highlighter approach. #191 These seem enough for the readme? |
* Lowercase filenames to scream less * Add `remark-cli`, `remark-preset-wooorm` to format prose * Use imports and fancy new JS features * Add link to a markdown cheatsheet, as many questions are about that * Add details tags showing equivalent JSX for examples, to clarify how markdown works * Refactor options list, clean signatures * Add examples on plugins, plugins w/ options, renderers (syntax highlighting), and combining plugins w/ renderers (math) * Add sections on why to use this, security, contributing, related projects * Add test for `react-katex` integration Closes GH-70. Closes GH-191. Related to GH-474. Closes GH-479. Closes GH-480. Related to GH-483.
* Lowercase filenames to scream less * Add `remark-cli`, `remark-preset-wooorm` to format prose * Use imports and fancy new JS features * Add link to a markdown cheatsheet, as many questions are about that * Add details tags showing equivalent JSX for examples, to clarify how markdown works * Refactor options list, clean signatures * Add examples on plugins, plugins w/ options, renderers (syntax highlighting), and combining plugins w/ renderers (math) * Add sections on why to use this, security, contributing, related projects * Add test for `react-katex` integration Closes GH-70. Closes GH-191. Related to GH-474. Closes GH-479. Closes GH-480. Related to GH-483.
Subject of the feature
remark has a giant ecosystem. This project is used a lot. It seems to be a good place to add common case examples of using math, footnotes, gfm, syntax highlighting, in the readme.
Problem
Confusing to newcomers. Most things can be solved by plugins. But it’s unclear how.
Expected behavior
A couple of examples. Not too many.
The text was updated successfully, but these errors were encountered: