DEV Community

loading...

Discussion on: Where do you keep non-code documentation, such as architecture explanation or research?

Collapse
juanita profile image
Juanita Soranno

I really like GitBooks. (see: gitbook.com) It reminds me of an old school SOP when they lived in three-ring binders and had handwritten content pages in the front.

Not sure what 'hosted on premises' means, so there's that :D

Collapse
jess profile image
Jess Lee (she/her)

Do you use GitBooks throughout the entire org -- i.e. sales/marketing docs or strictly for technical documentation?

Collapse
juanita profile image
Juanita Soranno

For everything!

Collapse
lennartb profile image
Lennart Author

It means that it should be hosted locally somewhere in our local network. So no cloud services or something, we don't want to put that kind of data on other people's servers.

Collapse
irvinlim profile image
Irvin Lim

All GitBooks are essentially just Git repositories, which can be self-hosted. If your organization requires it to be hosted on premises I suppose you have a self-hosted Git service like GitLab.

In that case, GitLab Pages plays well with GitBook using GitLab CI. Otherwise, you can set up some CI/CD pipeline that automatically builds your books for you.