Live data from Hacker News

SaltStack's docs set the standard for software documentation

docs.saltstack.com

1–9 of 9 posts

Re: SaltStack's docs set the standard for software documentation

#4
No, no they don't.

Poor search (custom Google searches are substandard generally), hidden full index, table of contents that doesn't match the index page, no synposes on pages that need them (eg CLI reference), no indication of what came before or next for individual sections, hidden index link, etc.

However, that's all very critical. On the plus side, comprehensive documentation is far better than no documentation at all, or poor / lacking documentation. And when you do want to read long sections of text, it looks quite well written.

Re: SaltStack's docs set the standard for software documentation

#6
The getting started doesn't help to really start anything.

I had to use third party docs to start with salt and ansible. I don't like puppet and chef docs either. Maybe all of them expect some user knowledge (I'm a developer learning about configuration management).

Re: SaltStack's docs set the standard for software documentation

#7
The getting started doesn't help to really start anything.

I had to use third party docs to start with salt and ansible. I don't like puppet and chef docs either. Maybe all of them expect some user knowledge (I'm a developer learning about configuration management).

Re: SaltStack's docs set the standard for software documentation

#9
post #4

No, no they don't. Poor search (custom Google searches are substandard generally), hidden full index, table of contents that doesn't match the index page, no synposes on pages that need them (eg CLI reference), no indication of what came before or next for individual sections, hidden index link, etc. However, that's all very critical. On the plus side, comprehensive documentation is far better than no documentation a…

We have a Salt Docs Sprint coming up next week. Details here: http://www.saltstack.com/saltstack-events/salt-docs-sprint Please add this feedback as an issue on our GitHub tagged with ticket #12446, and please join the sprint and contribute if you can.