Stripe's Docs have been best-in-class for a long time. Obviously, the care and human hours they put into their upkeep is the main reason for the Docs being so good. But, as with any creative endeavor, the tools matter. If the Stripe team didn't like the content management system they used to keep the Docs up-to-date they'd be less likely to do it. As someone that has used their Docs for hours and hours and hours I'm thankful to their team for how good their Docs are.<p>Very cool of them to open source this. Looks great.
We get to use Markdoc every day and it is a joy to work with.<p>Shameless plug: we're looking for someone to come in and a product manager over the Stripe Docs. Imagine working on docs at the company known for docs. Very fun problems.<p><a href="https://stripe.com/jobs/listing/product-manager-docs/3928998" rel="nofollow">https://stripe.com/jobs/listing/product-manager-docs/3928998</a>
I don't understand how this is fundamentally different than MDX, which can already mix React components within Markdown.<p>We used it to build the Streamlit docs. I assumed this is how everyone was doing documentation: <a href="https://github.com/streamlit/docs" rel="nofollow">https://github.com/streamlit/docs</a>
For anyone looking for a doc generation tool:<p>I was lately evaluating several tools like VuePress, Docusaurus and AsciiDoc.<p>I ended up using Mkdocs Material (<a href="https://squidfunk.github.io/mkdocs-material/" rel="nofollow">https://squidfunk.github.io/mkdocs-material/</a>). If you haven't already, have a look. I think it is pretty impressive. From tags, tabs to the fantastic built-in search ...
I'm not sure what the difference is between this and a bunch of other ones like Jekyll or Middleman? Is it in the render phase? What am I missing?
OMG. I was just about to start my own Markdown parser because I needed custom elements and I was finding too hard to work with existing "customizable" Markdown parsers.<p>Also, I needed a React renderer for React-Native and I was also about to write my own.<p>By the looks of it, I will be able to just use Markdoc.<p>Thank you Stripe!
It looks like a static site generator - but at the same time it appears you cannot actually generate a static site from it, but you need to run a node.js server.<p>What separates this from any of the existing markdown static site generators?
This is amazing. Does this power the Stripe API reference pages? <a href="https://stripe.com/docs/api" rel="nofollow">https://stripe.com/docs/api</a><p>Or is this only for <a href="https://stripe.com/docs" rel="nofollow">https://stripe.com/docs</a>, <a href="https://stripe.com/docs/payments" rel="nofollow">https://stripe.com/docs/payments</a>, etc?
So what's the workflow for this?<p>Because this seems to be run locally, vs something hosted like a CMS.<p>You locally have a NodeJS app running, you draft a new page, it renders it for you in HTML/CSS, and then you upload the rendered output to your web server?<p>(Sorry for the naive question)
So it’s been a few hours and I really love this library! I integrated it into a React/esbuild application and it is working great. The React/Prism example for code highlighting took a little work. They have an example but it is a little buried. Their example wasn’t working for me but it was enough for me to get my own working without react-prism.<p>Shameless plug:
If anyone is interested, I published my esbuild plugin so you don’t have to transform on the server if you want to just import a markdown file.<p><a href="https://github.com/toddw/esbuild-markdoc-plugin" rel="nofollow">https://github.com/toddw/esbuild-markdoc-plugin</a>
Shameless plug: for REST APIs, I've written a tool called Instaunit which combines HTTP API integration tests with documentation generation, since these two things must always be maintained in lockstep.<p>It's got a ways to go before it generates output that looks as good as Stripe's documentation, but it makes it dead simple to create API documentation that's guaranteed to be in sync with your service, because it was generated by your tests when they ran.<p><a href="https://github.com/instaunit/instaunit" rel="nofollow">https://github.com/instaunit/instaunit</a>
Good for people who like to work with non-standard markdown. Not sure why companies do not use RestructuredText (rst), which is a proper specification [0] and has been very successful in the area of documentation.<p>In order to generate a print quality documentation from this markdoc format will be a huge task. RestructuredText already has strong support for Latex output.<p>Now people have plain markdown, gitbook and now markdoc with its own set of non standard extensions. Hopefully rst format can catch up among JavaScript developers.<p>So far haven’t seen a complete documentation tool like Python Sphinx [1].<p>[0] <a href="https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html" rel="nofollow">https://docutils.sourceforge.io/docs/ref/rst/restructuredtex...</a><p>[1] <a href="https://www.sphinx-doc.org/en/master/" rel="nofollow">https://www.sphinx-doc.org/en/master/</a>
See also HedgeDoc <a href="https://hedgedoc.org/" rel="nofollow">https://hedgedoc.org/</a> which is collaborative and supports tables.
Does anyone know of tooling like this but not for only making websites?<p>I have an asciidoc based chain that mostly works for generating both PDF manuals and standalone html docs but it's a bit of a faff to install and set up especially for non-technical users.<p>My dream is something like pandoc but with one or more diagram libraries integrated, native PDF output and all wrapped up in a single binary, maybe with a nice web UI/editor built into the binary. Oh, and if it could manage multiple documents and versioning that would be great too. Looking for a Fossil SCM kind of feel?<p>Closest thing I've used would probably be LyX but that's almost too capable!<p>I do appreciate this is a really hard thing to do and I'm wondering what toolchains other people are using?
One curiosity: I was trying to figure out how the diagram at the top of <a href="https://markdoc.io/docs/render" rel="nofollow">https://markdoc.io/docs/render</a> was generated.<p>The items inside the diagram seem curiously absent from the source of the page: <a href="https://raw.githubusercontent.com/markdoc/docs/main/pages/docs/render.md" rel="nofollow">https://raw.githubusercontent.com/markdoc/docs/main/pages/do...</a><p>Instead, when the `diagram` tag is defined, it maps the "type" parameter to a particular diagram: <a href="https://github.com/markdoc/docs/blob/main/components/Diagram.js" rel="nofollow">https://github.com/markdoc/docs/blob/main/components/Diagram...</a><p>Any reason it is done that way, rather than specifying the diagram in the source of the document using mermaid, pikchr, etc? Even inlining the SVG seems like it would be better for keeping everything together.
I am glad to know there are those that put so much thought into documentation. Documentations is just another service, and deserves all the same methodology: CI/CD, automatic tests, components and reuse, different environments etc.<p>As far as I can see, you can get similar workflow with combination of existing tools. I created this docker image that combines them for very easy consumption and created thousands of pages of technical, functional and user documentation with it:<p><a href="https://github.com/majkinetor/mm-docs" rel="nofollow">https://github.com/majkinetor/mm-docs</a>
How does this compare to DocFX? One thing I think Microsoft does very well is the Azure documentation. It's consistently structured across services, but even better, it's also all just a bunch of Markdown and for any page, you can open a Github issue right from that page. And because it's in Github, you can see the history of a page, which has been helpful to see when options change or when limitations were clarified.<p>I think MSFT just uses stock DocFX for the Azure docs site, but I'm not sure.
Does this have functionality to auto-generate docs from (python) docstrings? Currently using Sphinx with RTD (ReadTheDocs) theme for this, and quite happy with it, though the setup took a lot of hunting around for examples. Wondering if this is the best auto-doc approach for python these days. For context, I am developing a code base with the intention of later open sourcing it, so wanted to have it properly documented from the start.
I've been thinking about using this or Docusaurus to start a blog. Does anyone have an opinion on which of the two is better/easier/etc?
I'm a bit confused. Following the React tutorials <a href="https://markdoc.io/docs/render#react" rel="nofollow">https://markdoc.io/docs/render#react</a> I was able to render my own react components on custom tags, which I wanted. Nice! But I'm not being able to define how to render my own components for Markdown tags like paragraph or heading :(
From the docs, it looks like they're emphasizing the <i>document format</i> part, and less so the <i>authoring system</i> (which would make me think of SSG/CI/etc).<p>It also looks like there are functions, but they're considerably shaved down compared to JavaScript/etc.<p>I wonder if this will get more adoption in the TW community and by various static site generators.
How well does this scale to hundreds of pages? I found Jekyll and others can start to slow down here during page generation where it can take several seconds to generate not that many pages, especially if you're using a lot of template features. It's part of the reason Hugo is my default as it's so fast.
"side-by-side" is a module that seems to be used extensively throughout this projects documentation, as well as in stripes documentation. I don't see where it is defined anywhere, do they have a library of these common helpers? I looked but I guess my searchfu isn't what it used to be.
Are relative links supported?<p>The landing page uses <i>root-relative</i> links and the FAQ/examples don't seem to cover links in depth.<p>I like relative links because my editor (VS Code) will auto-complete relative links... but many Markdown-based tools don't handle the Markdown-source-to-output-HTML translation.
This looks nice but you might want to have an example of the custom syntax on the front page because as far as I can tell that is the main thing this adds, and currently the front page doesn't make it sound different to anything else.
It was good to read "Why not AsciiDoc?" in their FAQ:
<a href="https://markdoc.io/docs/faq" rel="nofollow">https://markdoc.io/docs/faq</a>
Lol, I haven't seen the text following the mouse cursor ("Try it out") in a <i>long</i> time. Glad to see some whimsy is still present on the Internet.
I have been looking for exactly this. Will test it out for sure.<p>On a side-note, mixing serifs and sans in the way the site does looks like something only a mass murderer would do.
Name collision with:<p><a href="https://github.com/haghish/markdoc" rel="nofollow">https://github.com/haghish/markdoc</a>