String/span JSX component not rendered correctly in TOC and sidenav

[dbrrt]

This might be considered an edge case but something useful when defining constants as components within a mdx project, to adjust globally updating a single file.

I've got this component defining a brand name

export const BrandName = () => {
    return <span>Authdog</span>
}

This pattern worked well with nextra, framework I'm migrating from to Zudoku.

Nextra:

import {BrandName} from "../../components/brandname.jsx";

# <BrandName /> Overview

Importing the same way in Zudoku, the content is rendered correctly inside the page but not on sidenav and TOC

[mosch]

Awesome feedback @dbrrt thanks for that. I love how you use mdx to make sure the brandname can be changed easliy. (Even though I love Authdog and don't know why you would change it 😍)

[dbrrt]

Awesome feedback @dbrrt thanks for that. I love how you use mdx to make sure the brandname can be changed easliy. (Even though I love Authdog and don't know why you would change it 😍)

@mosch Really appreciate the love and support! :)
I was thinking more broadly, using a MDX component for sub-product names so they can be reused consistently across content and updated in one place.
For example, I’m working on an authorization framework (part of Authdog), and the name might still change before the public release but could eventually appear in titles (parsed to generatec TOCs).
While this approach works in Nextra, I prefer Zuplo’s structure and am currently migrating my docs over. I really like having a centralized place for platform guidance, live API docs, and identity-aware features, all backed by open-source documentation.
At this point, not having MDX components rendered in the TOC or navigation isn’t a blocker for me.

[dan-lee]

@dbrrt FYI PR #1929 will take care of this :)