Earlier quoted context omitted.
Update to a more recent version, they re-worked the nav to be one menu on mobile.
That was a very low-hanging fruit. Could fix and deploy it in a few minutes. There are few other improvements too related to navigation in the latest Docusaurus. Deployed here: https://docs.tooljet.com
Ask HN: What are you using for public documentation these days?
81–90 of 111 posts
Re: Ask HN: What are you using for public documentation these days?
#82We (Handsontable) now use VuePress[1] for our docs[2] and we are very happy with it. The best feature for us is the ease of customization. Our challenge right now with the docs is to get a fantastic code snippet runner there. But that's beyond the scope of your regular documentation management tool, I suppose. VuePress will make it easy for us to integrate our solution. [1] https://vuepress.vuejs.org/ [2] https://han…
Re: Ask HN: What are you using for public documentation these days?
#83We are using Docusaurus ( https://docusaurus.io/ ). - it is easy to configure/customise - looks really great out of the box - solid documentation - fast In our case, we just had to change the colors and font. Here is our Docusaurus code if that's helpful: https://github.com/ToolJet/ToolJet/tree/develop/docs and here is the live documentation: https://docs.tooljet.com/
It's technically still in beta with frequent updates, and the occasional breaking change.
For our site (https://deephaven.io/core/docs/), what I liked was the ease of adding your own plugins. We made a plugin that extracts all our code examples, and automatically tests them against new versions to notify us if any examples break or become stale.
Re: Ask HN: What are you using for public documentation these days?
#84I like the fact you can plug any vue components into the markdown. Haven’t started using that feature extensively yet, but the fact that it’s available is reassuring that I can customize things well if needed.
Re: Ask HN: What are you using for public documentation these days?
#85Basic markdown and Sphinx to build into HTML, publishing via github pages. It's an open source project so putting the docs alongside the code just makes sense. Although Sphinx isn't great for my money, it gets the job done.
I have grown to absolutely love Sphinx. The plugins are wonderful, including Sphinx gallery, jupyter integration, and Sphinx-needs for requirements management.
Re: Ask HN: What are you using for public documentation these days?
#86If you're looking for a SaaS solution, I can really recommend Archbee[0]. We've moved to it from ReadMe[1] recently, due to constraints in ReadMe's product and the challenges scaling it commercially in our model. [0]: https://www.archbee.io/ [1]: https://readme.com/
Re: Ask HN: What are you using for public documentation these days?
#87Background: I've been a technical writer for 9 years. 6 at Google, 3 as the only writer at an IoT startup. I helped Corrily with their docs [1] in August. They were interested in ReadMe.io. I wasn't keen on it because I had worked with Retool on their docs (hosted in ReadMe) a few years back and had found ReadMe lacking. But I was pleasantly surprised by how much it has progressed since then! If you're looking for a…
Re: Ask HN: What are you using for public documentation these days?
#88TL;DR: Favorite stack is Notion -> notion-markdown-cms -> VuePress -> netlify So I've gone through a bit of journey doing docs for a product company. I feel that for a product company it's really important to own your documentation and the publishing workflow as it's a key part of your product. GitBooks was my first stab. I liked git and markdown, however I disliked all the places where "proprietary" formatting/featu…
Re: Ask HN: What are you using for public documentation these days?
#89Here is our Archbee-hosted site: https://docs.invoiced.com/
Re: Ask HN: What are you using for public documentation these days?
#90I like Hugo. You can chose any of the existing themes or create your own. For deployment, I wrote a simple Go server that checks a (public) GitHub repo for changes every 15 minutes and pulls + regenerates the content if necessary. You can find it here: https://docs.pirsch.io