For writing technical styled documentation, I've found fumadocs to be amazing.<p>It looks great out of the box and supports a product switcher, which can be used for maintaining related products or product versions. It also supports OpenAPI imports and API playgrounds.<p>The best part is that it is just a fully fledged (nextjs) app that is entirely customizable with relative ease. We just moved to it from Docusaurus and couldn't be happier.
Regarding the author’s mention of starlight missing support for mermaid — shouldn’t they be able to just use mermaidjs to render those charts? Why the need for playwright or a plugin?
For documentation versioned docs are critical. Docusaurus handles multiple versions extremely well, curious if the author has released a new major version of Glasskube and if not, will they miss this feature in the future.
> To be completely honest: The reason I looked for another documentation framework was that I was fed up with Docusaurus taking forever to start the initial development server. With the latest Node version (24), Docusaurus version (3.7), and React version (19), it took a little over 5 seconds to start the development server. Although this number doesn't seem to be that high, it was a lot higher with previous versions. I remember waiting over 20 seconds for the development server to start, which really frustrated me.<p>what is the cause for this?
I haven't used Starlight, but Docusaurus is very slow. The last time I used it, its performance on a large documentation site was terrible, even causing the GitHub Actions Runner to time out. In other words, a single build took over 30 minutes. I never considered using it again after that.
Particularly like the honest take. I wouldn’t say reading this I’d go for starlight either<p>> When I tried to create marketing pages with Starlight in addition to the technical documentation, I nearly gave up. Coming from the Docusaurus world, this wasn't an issue as the starter template comes with a front page and a blog out of the box. You can even create multiple documentations on different paths. We used /docs, for example.<p>> Starlight, on the other hand, is only built for documentation and not for marketing pages. It even took an ugly hack to make sure the default path is /docs and not /.<p>> Please don't look at this custom script configured in our astro.config.mjs we need to execute on every page to make sure that the redirection works properly<p>Love the straight talking. Refreshing in the period of ai slop blogposts