Modern publishing tricks and practical code tips for components and Markdown.
This is where we experiment with static MDX sites, Markdown, Next.js, JavaScript, and React, and we blog about what we learn.
We also offer templates, so you can start from a solid base and adapt it to your own projects.
This keeps content flexible while still letting you use components.
This keeps content as real files in Git, so review and history stay simple.
This makes it easier to ship predictable static builds with fewer moving parts.
This works well when the UI needs to be adapted to match each project.
This keeps the setup clear when you extend or swap parts over time.
This makes it easier for teams to review, deploy, and keep changes in sync.
Use cases where a MDX powered, file-based, static workflow makes sense.
This works well when long-form content needs to live next to code.
This keeps updates in Git history instead of a separate CMS.
This makes it easier to keep docs in the same repo as the product.
This keeps multi-section sites tidy and predictable as they grow.
Technical articles and tutorials.
In this article, we will walk through the process of creating a like button for an MDX-based Next.js application.
In this article, we'll explore how to create and use custom React components within MDX.
One of our goals for this site is to keep it fast, focused, and pleasant to read.
In this article, we'll explore how to import and use custom components in MDX files and then dive into how these components and other elements can be styled to fit seamlessly within your design system.
Images are essential in enriching the content of your markdown or MDX files, helping to convey information visually and make your articles more engaging.