Skip to content
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

Merged
merged 36 commits into from Nov 18, 2021
Merged

Add improved docs #900

merged 36 commits into from Nov 18, 2021

Conversation

wooorm
Copy link
Member

@wooorm wooorm commented Nov 14, 2021

Initial checklist

  • I read the support docs
  • I read the contributing guide
  • I agree to follow the code of conduct
  • I searched issues and couldn’t find anything (or linked relevant results below)
  • If applicable, I’ve added docs and tests

Description of changes

Questions and to-be-discussed:

  • what to do with docs/ folder
  • More examples? Less examples?

Related-to: unifiedjs/unified#168.

/cc @nemo-omen @remcohaszing @ChristianMurphy @Murderlon @with-heart @joostdecock @mgan59

@wooorm wooorm added the 📚 area/docs This affects documentation label Nov 14, 2021
@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Nov 14, 2021
@codecov-commenter

This comment has been minimized.

@github-actions

This comment has been minimized.

packages/remark-stringify/readme.md Show resolved Hide resolved
packages/remark/readme.md Outdated Show resolved Hide resolved
Copy link

@mgan59 mgan59 left a 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
Copy link

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?

Copy link
Member Author

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!

doc/plugins.md Show resolved Hide resolved
packages/remark-cli/readme.md Show resolved Hide resolved
packages/remark-parse/readme.md Show resolved Hide resolved
packages/remark/readme.md Outdated Show resolved Hide resolved
@mgan59
Copy link

mgan59 commented Nov 15, 2021

Few additional thoughts about open-questions

What to do with docs/ folder

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 packages.

More examples, less examples?

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 docs/ folder that are more involved examples organized by function/role. Whether that is advanced plugin development, building testing / tooling workflows, etc. An example here is part of my processing pipeline requires me to use remark-cli to generate test-fixtures since we do contract-driven test-development.

Co-authored-by: Merlijn Vos <merlijn@soverin.net>
@wooorm
Copy link
Member Author

wooorm commented Nov 15, 2021

@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!

Could also be a place to put larger tutorials / examples that use the various packages.

in most cases I think those can go on unifiedjs.com: one place to collect the overarching docs.

Have you considered starting any kind of ADR/RFC process around the various sub-packages

We do have unifiedjs/rfcs, but it’s not very active. Also a lot of processes are described here in unifiedjs/collective.

readme.md Outdated Show resolved Hide resolved
doc/plugins.md Show resolved Hide resolved
doc/plugins.md Show resolved Hide resolved
doc/plugins.md Show resolved Hide resolved
wooorm and others added 2 commits November 18, 2021 09:42
Co-authored-by: Remco Haszing <remcohaszing@gmail.com>
packages/remark-cli/readme.md Show resolved Hide resolved
packages/remark-cli/test.js Show resolved Hide resolved
packages/remark-cli/readme.md Show resolved Hide resolved
Comment on lines +24 to +29
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.
Copy link
Member

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:

  1. remark is popular
  2. remark is for markdown
  3. remark uses ASTs
  4. ASTs make it easy to edit markdown
  5. Plugins can also edit things
  6. There are a lot of plugins

Is that the order we want to present things?
Maybe:

  1. remark is for markdown
  2. remark uses ASTs and plugins
  3. ASTs and plugins make editing easy
  4. remark has a large community
  5. community includes many remade plugins

?

Copy link
Member Author

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.

Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

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.

Copy link
Member Author

@wooorm wooorm Nov 18, 2021

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.

Copy link
Member Author

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?

@wooorm wooorm merged commit 87c50a5 into main Nov 18, 2021
@wooorm wooorm deleted the docs branch November 18, 2021 18:14
@wooorm wooorm added the 💪 phase/solved Post is done label Nov 18, 2021
@github-actions

This comment has been minimized.

@github-actions github-actions bot removed the 🤞 phase/open Post is being triaged manually label Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 area/docs This affects documentation 💪 phase/solved Post is done
Development

Successfully merging this pull request may close these issues.

None yet

6 participants