-
-
Notifications
You must be signed in to change notification settings - Fork 357
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 improved docs #900
Add improved docs #900
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋🏻 I didn't have any blockers, but wanted to read through the changes and give some feedback an in general get caught up on the discussions happening here.
More plugins can be found on GitHub tagged with the | ||
[`remark-plugin` topic][topic]. | ||
|
||
Have a good idea for a new plugin? | ||
See [Creating plugins][create] below. | ||
> 👉 **Note**: some plugins don’t work with recent versions of remark due to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to do an upgrade on my remark
and need to audit which plugins are supported 💯 -- again I'm behind so not sure if this NOTE should also go in the root README?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A link here is already referenced in the migration guide: https://github.com/remarkjs/remark/releases/tag/13.0.0. That’s probably a better place for folks to find this point instead of buried somewhere in a big monorepo readme?
good point that folks are still upgrading though!
Few additional thoughts about open-questions
I'd say keep it and continue to place documents in there that are meant for the larger mono-remark repo. Have you considered starting any kind of ADR/RFC process around the various sub-packages? Could also be a place to put larger tutorials / examples that use the various
I think it is always good to have 1-2 examples in the Readme for the package. Can always link from that section to followup/inter-related markdown documents in the root |
Co-authored-by: Merlijn Vos <merlijn@soverin.net>
@mgan59 Thanks for the review! I particularly appreciate opinions on these docs from folks that don’t actively maintain them, it’s helpful to hear what is hard, what you didn’t know before, and what’s vague!
in most cases I think those can go on
We do have |
Co-authored-by: Christian Murphy <christian.murphy.42@gmail.com>
…ark, just like gfm
Co-authored-by: Remco Haszing <remcohaszing@gmail.com>
remark is a very popular ecosystem of plugins that work with markdown as | ||
structured data, specifically ASTs (abstract syntax trees). | ||
ASTs make it easy for programs to deal with markdown. | ||
We call those programs plugins. | ||
Plugins inspect and change trees. | ||
You can use the many existing plugins or you can make your own. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Repeating back the keypoints in the order they appear:
- remark is popular
- remark is for markdown
- remark uses ASTs
- ASTs make it easy to edit markdown
- Plugins can also edit things
- There are a lot of plugins
Is that the order we want to present things?
Maybe:
- remark is for markdown
- remark uses ASTs and plugins
- ASTs and plugins make editing easy
- remark has a large community
- community includes many remade plugins
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure what this would mean practically?
I don’t think remark really has a large community. I use popular here to mention that it is used a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t think remark really has a large community. I use popular here to mention that it is used a lot.
Adopters aren't part of the community?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Who do you mean by adopters?
Community to me sounds like folks actively interacting with repos, discussions, etc, and I don’t think we have much of that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adopters as in folks downloading and using remark, maybe opening an issue or a discussion, but not yet a maintainer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So “user” in this chart, right?
There’s a divide there: folks that choose to put a markdown package in their package.json
, and folks that use packages that somewhere include remark.
remark, compared to others, has few of those adopters/explicit users: https://github.com/remarkjs/remark/network/dependents?dependent_type=PACKAGE&package_id=UGFja2FnZS0xNDIzNzIzMw%3D%3D, https://github.com/markedjs/marked/network/dependents?dependent_type=PACKAGE&package_id=UGFja2FnZS0xMzQzNjIxNw%3D%3D, https://github.com/markdown-it/markdown-it/network/dependents?dependent_type=PACKAGE&package_id=UGFja2FnZS0xODE4NTUwMQ%3D%3D
But the most of implicit users, by download counts.
I don’t think it’s fair to say we have an exceptionally vibrant community here, but it is fair to say we’re the most popular.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but this is sort of besides the point of your earlier layout of a rewrite?
Initial checklist
Description of changes
remark-parse
remark-stringify
remark
itselfremark-cli
doc/plugins
Questions and to-be-discussed:
docs/
folderRelated-to: unifiedjs/unified#168.
/cc @nemo-omen @remcohaszing @ChristianMurphy @Murderlon @with-heart @joostdecock @mgan59