It would help to pull Markdown syntax into a doc on the Gatsby site, so people know how to write it! This is especially true now that MDX is a key workflow. It would be helpful to cover syntax things, like:
Functionally, it would help to know:
This doc should include enough details inline that someone who hasn't used Markdown or MDX before can get up and running. Linking to more information out on the web under "related resources" is great, too.
My current best recommendation for sidebar placement is under "Adding Components with MDX", but we could potentially create a new section for creating content and blogging. @amberleyromo any opinions on where to put a Markdown guide?
For anyone taking this on, it's recommended to follow the reference guide template: https://www.gatsbyjs.org/contributing/docs-templates/#reference-guides
And refer to the Gatsby Style Guide for additional conventions: https://www.gatsbyjs.org/contributing/gatsby-style-guide/
@Bculp and I would like to take this if it's still available!
@rlynn523 yes, it's open! We would love to have your contribution. Thanks for offering!
Hey @rlynn523 and @bculp. I would also be keen to help out with this, if there is a section that could easily be sectioned off/if you run out of time 馃檪
@marcysutton I started doing a rough draft of the syntax page and moved on to frontmatter...but the more I look through the docs, it seems like a lot of the information you want for the markdown reference guide is in the mdx docs. For example this has a pretty comprehensive table for md syntax. I believe there is also an example that shows needing to put frontmatter before imports, etc. Do you want to have an MDX section and MD section that show very similar info, or should we have a generic MD section that has info that is applicable to both MD and MDX, and then an MDX section nested under that with very MDX-specific info? Let me know what you think!
Ah, good catch! I definitely didn't realize it was in there...and I suspect it won't be easily discoverable for people who aren't looking for it in an MDX component doc. I'd recommend creating a new, longer doc with more general context (e.g. "MDXProvider" might be intimidating for people just getting started with Markdown). We can always make updates to that MDX page later on to make it less redundant, but more information in the docs on formatting Markdown is probably fine for now. Thanks for checking!
No problem! 馃憤
@marcysutton can you also assign @Bculp to this issue? We've been collaborating on it.
@rlynn523 I can't seem to add @Bculp, but that shouldn't impact your workflow.
I think we covered everything. I'm planning on putting in a PR tomorrow!
@marcysutton here is the link to the PR https://github.com/gatsbyjs/gatsby/pull/15861
Closed with #15861. Thanks so much for your work on this, @Bculp and @rlynn523!
Most helpful comment
Closed with #15861. Thanks so much for your work on this, @Bculp and @rlynn523!