Books and chapters
A logical structure: department → process → steps. A new employee finds the answer alone.
Collaboration 07.3 — Knowledge base
Procedures, instructions and knowledge in one place — structured as books, chapters and pages. Not Word files in a folder, but a searchable base.
BookStack / capabilities
A simple WYSIWYG editor, role-based permissions, full-text search and LDAP/SSO — I deploy it and train the team.
A logical structure: department → process → steps. A new employee finds the answer alone.
WYSIWYG, images, tables and code blocks — without technical knowledge.
Who reads, who writes and who approves — at book level, not just system level.
Search works inside page content, not just titles — an answer in 5 seconds.
One user for every service — the same account, password and groups.
Every change is kept — who changed what and when is always visible.
process
What processes exist and how they split into books — taxonomy first, content second.
BookStack via Docker, its database, HTTPS and backups.
Moving and organising existing Word/PDF documents — nothing old is lost.
I teach the team to write so others can find it — that is half the success.
cases
Access, procedures and contacts in one book — nobody has to explain everything again.
How support works, what the stages are and who approves — one source for everyone.
Integration
BookStack does not replace Nextcloud — it fills in what a file store cannot do.
faq
BookStack is more structured: book/chapter/page and a simple editor. A wiki is freer and more networked — the choice depends on purpose.
Yes — a Docker container with 1–2 GB RAM is enough. Very light for a small team.
All directions
If the answer is “in people’s heads” — it is time to build a base.
Let’s talkContact
Contact me by phone or WhatsApp. Critical incidents are covered 24/7; other requests are handled within the agreed support schedule.
24/7 on critical incidents — Response mode
If I miss your call, I will get back to you.