- Gitbook.io doesn't support i18n well. Not SEO friendly and not language detector. - Readme.io is too expensive for just product docs. - Hosting with NextJS etc.. is a pain if you need to support i18n and edit content using markdown.
I had to build out a Next app last year with a seamless looking blog and docs site. I struggled to find real solutions, so I ended up getting in touch with Marco from Plausible to get some advice. He helped me to figure out their stack, and I replicated it to my project. I released a dope next app with a markdown powered blog and docs site that looked amazing.
I’m working on releasing a free cli tool for frontend devs based off this work. I’d love some feedback and watches on GitHub if anyone is interested. Link is in my bio.
SHOW HN and IH coming soon :)
Yeah, I have a few hypothesis that I am going to prove using the Elegant tool that I’m working on.
The first hypothesis is that I’m going to use Elegant itself to scaffold out the documentation. So when the domain is live, Elegant will be ready for beta testing. I hope to get some content up on the domain this week!
Thanks for pointing this out.
We are working on multiple aspects of the products that should cover a lot of this (improved i18n, SEO, faster rendering)!
Would love to get your feedback on what you would like to see improved exactly on our SEO friendliness and i18n support. We have an open GitHub community for feedback; https://github.com/GitbookIO/community/discussions
And for anyone, if you are interested in building a "A SaaS to host product guides ", we are hiring engineers/designers/builders: https://jobs.gitbook.com/ :)