Thanks for sharing my project! I started building BookStack just over 9 years ago to suit a need at work, and have been improving & maintaining it since. I left full time employment three years ago and have been focusing on BookStack since, with my living costs now covered via project donations, sponsorships & support services, and the growth of these continue as shown in my blogpost here: https://www.bookstackapp.com/blog/9-years-of-bookstack/#fina....

The platform has been designed for ease-of-use, with mixed-technical-skill workplace use in mind. The design and content structure is (purposefully) quite opinionated though so does not suit all use-cases, but for many it works quite well.

Technically it's built as quite a technically simple PHP/Laravel/MySQL stack with custom JavaScript sprinkled in where needed. The default WYSIWYG editor is TinyMCE based, although due to TinyMCE license changes I'm currently building a lexical-fork-based new editor.

If you'd like to understand the project more, a project FAQ can be found on our site here: https://www.bookstackapp.com/about/project-faq/

[0]

We use it at work and its ok. Missing permalinks and the permission concept does not fit our usecase.

Good to see simple wiki / confluence alternatives. But confluence is here to stay, with all it's rich features.

I switched jobs and thus move away from confluence to ADO wiki and life is never endingly painful for internal knowledge management!

Either there are 100s of word docx or there's confluence that can be easily queried, with various other capabilities using it's plugins for draw.io and mermaid.js.

Markdown for large tables is just silly and hard to maintain. AsciiDoc is great, but a bit too much for docs that are shared with product teams.