Live data from Hacker News

Ask HN: What are you using for public documentation these days?

news.ycombinator.com

51–60 of 111 posts

Re: Ask HN: What are you using for public documentation these days?

#51
If 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?

#52
post #49
post #43

Earlier quoted context omitted.

It doesn't support search unless you rely on (pay for) Algolia? Wow, instant pass from me.

You can add your own search plugin or use another provider like Typesense. They just offer an optional free Algolia service for open-source projects on top. You can read more here: https://docusaurus.io/docs/search

Ah phew, thanks. The site made it sound like they only supported Algolia.

Re: Ask HN: What are you using for public documentation these days?

#53
I have a custom setup. I don't use a generator. I don't like my JS files with all these doc-comments.

The downside: quite a lot of work to create something from scratch.

The upside: I have created a playground-type API, where all options, methods & events can be tried out directly from the docs. They interact with the data grid.

https://www.datagridxl.com/api/options

Re: Ask HN: What are you using for public documentation these days?

#54
We use [TypeDoc](https://typedoc.org/) to generate documentation from all of our TypeScript. It combines type definitions with surrounding comment blocks for easily navigable, clean documentation.

For non-TypeScript codebases, we use [Docusaurus](https://docusaurus.io/).

I believe there are also plugins which can make TypeDoc output compatible with Docusaurus.

None of our docs are public at the moment, but a good example of documentation generated by TypeDoc would be Amazon's `aws-sdk`: https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/index...

Re: Ask HN: What are you using for public documentation these days?

#55

Earlier quoted context omitted.

> live documentation: https://docs.tooljet.io The two separate hamburger menus were hard to parse at first on mobile. Do your social media links really deserve higher placement than the navigation?

You are right, placing the navigation on the sidebar is more useful than the links to GitHub and Slack.

Update to a more recent version, they re-worked the nav to be one menu on mobile.

Re: Ask HN: What are you using for public documentation these days?

#56

I am frequently working on ways to document inline with the code using comments and then extract those comments during the build process to keep documentation up to date automatically. The comments are formatted as mark down so that they may be converted from code comments to stand alone mark down documents. I have also noticed that in VS Code a comment immediately preceding a type or interface declaration written in…

Are you talking about Typescript here? If so, could you give an example of how to make this happen? This sounds incredibly useful.

I think you and austincheney might be looking for [TypeDoc](https://typedoc.org/). See my comment here: https://news.ycombinator.com/item?id=29265856

Re: Ask HN: What are you using for public documentation these days?

#57
We use asciidoctor + jekyll at $CURJOB. It seems to work great, can be hosted for free or low cost. Lots of templating wins.

I do wish it supported running code snippets, but I think that can be done with some scripts and including things. (On the list, not done yet.)

Re: Ask HN: What are you using for public documentation these days?

#58

Earlier quoted context omitted.

Your docs even support dark mode! Did that come out of the box or did you add that?

It comes out of the box. We are now trying to figure out how to switch screenshots based on the light/dark mode. The screenshots taken from light mode of ToolJet looks odd in Docusaurus' dark mode.

You could build your own react image wrapper then use that component in the mdx and pass in two images, then display the appropriate one based on the current theme provider. Docusaurus makes using inline react components easy.

You could also write your own remark plugin, that does it for you, and would have the benefit of having more control over what happens on the github side if it was still standard markdown.

Re: Ask HN: What are you using for public documentation these days?

#59
post #6

I'm using mkdocs with the material plugins [1]. I'm running it mainly for a Blockchain Education site for my labs from my course, which seems to be fine [2]. I did a fair amount of customization though, so I am running all this as mkdocs plugins, not directly from the materials project. [1] https://squidfunk.github.io/mkdocs-material/ [2] https://ethereum-blockchain-developer.com

Oh wow this looks great! Simple conversion of markdown into an opinionated simple to use really nice looking doc site.! Cheers for this :)

+1000 for the "Material for MkDocs" project by squidfunk - we (Ritza.co) do documentation for various companies and we've strongly encouraged them to all switch to this since we found it. Fast, beautiful, simple.

The free version is really nice but also very happy to pay for the 'insiders' version via GitHub donations.

Post reply on HN