prism-react-renderer VS nextra

Both frameworks also support code blocks with syntax highlighting. Docusaurus uses prism-react-renderer for theming, while Starlight uses an Astro package called expressive-code to control customizations.

In my previous blog post on Code Reading, I read the codebase of Docusaurus to research how the project implements Syntax Highlighting for fenced code blocks. My research taught me that Docusaurus actually uses Prism-React-Renderer, a third-party library, to provide Syntax Highlighting. This knowledge was useful because I wanted to add syntax highlighting to ctil, my Markdown-to-HTML converter, but didn't want to implement the feature from scratch. Although I can't use Prism React Renderer in my own project, researching Docusaurus gave me the idea to find a Open Source library I could use.

For non-live codeBlock, you may want to render it by prism-react-renderer which is working also under the LiveEditor. I'm not sure what is the best way to share the style and theme between them but do so anyhow.

If you already haven’t integrated MDX into your project (you should because MDX is awesome), here’s the official guide on Gatsby's documentation to add it to your project. However, if you are already using Markdown Remark in your project, consider Migrating to MDX. In this post, we will integrate PrismJS syntax highlighting with MDX using prism-react-renderer. Also, we are going to add line numbers to code blocks. This is what we are aiming for:

Syntax Highlighting - Nextra comes with in-built syntax highlighting. However, when I created my site the syntax highlighting feature doesn’t seem to be working. So, I ended up creating my own syntax-highlighting component with prism-react-renderer.

If you have a Nextjs blog (or any React Framework blog) and want to create beautiful code blocks out of your MDX posts, then this post will show you how to do that using prism-react-renderer.

To fix it, I just went to this repo, specifically to prism-react-renderer/themes/ and checked the available themes I could use, and found out that the Visual Studio themes looked the best for my purpose.

From memory you need to target the `pre` block so you can apply the styles/theme to them. I uses prism-react-renderer.

Integrating syntax highlighting in Gatsby is solvable with solutions like gatsby-remark-prismjs or prism-react-renderer. When creating the code block in Markdown you specify the desired language (e.g. js or css) after the opening three backticks. It's a nice touch to display the specified language also in the code block itself, like I do it on my blog here:

In this very short quick tip you'll learn how to set up code blocks in MDX and Gatsby that support line numbers and code highlighting using the code renderer prism-react-renderer. A preview can be found on CodeSandbox.

co-author here

we put in a lot of effort into our docs and we'd greatly appreciate any criticism or feedback! Langfuse is powerful but the docs should help beginners to quickly get started and then incrementally use more features.

docs are OSS, repo: https://github.com/langfuse/langfuse-docs

built using: https://github.com/shuding/nextra

However, this may just be due to the lack of proper documentation from the Nextra side of things (shoutout to Nextra though, regardless).

Nextra - Nextra is another option for creating documentation sites. While it might not be as well-known as Docusaurus, Nextra offers a modern and minimalist approach to building documentation. It is designed to be lightweight and user-friendly, making it a good choice for those who prefer a simple and clean documentation style. You can explore more about Nextra on their official website.

I have looked at https://nextra.site/ but that doesn't work with the app router yet. So I'm wondering if there's another alternative.

You could also have a look at Nextra. You can use mdx components to build your blog (including support for server-side fetching). I'm currently using their documentation template, but it seems they also have a blog template.

We write everything in Markdown, as it's the closest you'll get to a 'universal' format. Then, we use a static site generator to turn the docs into a website. Current projects are using Nextra for this. If you ever need to change site generators, you still have all the markdown docs and image files, so it's pretty easy to change.

https://nextra.site/ is nice

Today I found this tool for Next.js called Nextra. You can effortlessly create a blog post website or a documentation website. All you need is markdown. Simply export your markdown from Notion and utilize it with Nextra to enjoy all the cool features, including full-text search, syntax highlighting, dark/light mode, and even image support. Everything is generated at build time, making it a static website which is Blazingly fast. https://nextra.site/