Markdoc: Stripe's Markdown-based authoring framework
1–10 of 157 posts
Re: Markdoc: Stripe's Markdown-based authoring framework
#2We used it to build the Streamlit docs. I assumed this is how everyone was doing documentation: https://github.com/streamlit/docs
Re: Markdoc: Stripe's Markdown-based authoring framework
#3Re: Markdoc: Stripe's Markdown-based authoring framework
#4Re: Markdoc: Stripe's Markdown-based authoring framework
#5I don't understand how this is fundamentally different than MDX, which can already mix React components within Markdown. We used it to build the Streamlit docs. I assumed this is how everyone was doing documentation: https://github.com/streamlit/docs
> The key difference is that MDX supports arbitrarily-complex JavaScript logic (think: docs as code) while Markdoc enforces a strict separation between code and content (think: docs as data).
> Markdoc uses a fully declarative approach to composition and flow control, where MDX relies on JavaScript and React. This means MDX affords users more power and flexibility, but at the cost of complexity–content can quickly become as complex as regular code, which can lead to maintainability complications or a more difficult authoring environment.
Re: Markdoc: Stripe's Markdown-based authoring framework
#6Add a newline after the title frontmatter and type "u"
Re: Markdoc: Stripe's Markdown-based authoring framework
#7Re: Markdoc: Stripe's Markdown-based authoring framework
#8Browsing their Docs has this weird, glitchy animation. Where is it coming from?
Re: Markdoc: Stripe's Markdown-based authoring framework
#9Add a newline after the title frontmatter and type "u"
Re: Markdoc: Stripe's Markdown-based authoring framework
#10Browsing their Docs has this weird, glitchy animation. Where is it coming from?
I'm an engineer on the Docs team at Stripe. Can you say more about where you're seeing the animation and what it looks like?