Skip to content
A platform to create documentation/wiki content built with PHP & Laravel
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Tweaked bug report template to request hosting method Aug 12, 2018
app Merge branch 'fix/registraion-form-validation' of git://… Apr 21, 2019
bootstrap Fixed heavy init breakages made in last commit Nov 19, 2017
config Czech translation Mar 22, 2019
resources Updated TinyMCE to version 4.9.4 Apr 21, 2019
routes Add revision restore confirm and changed http method Apr 20, 2019
storage Added ability to secure images behind auth Jan 13, 2018
tests Merge branch 'fix/registraion-form-validation' of git://… Apr 21, 2019
themes Added view override support Dec 31, 2017
.browserslistrc Added browserlist, Tweaked md scrollToText ot use ES6 Jul 14, 2018
.env.example Commented APP_URL by default to prevent upgrade path issues Jan 6, 2019
.env.example.complete Issue #1306 - Unit Tests for LdapService Changes Mar 9, 2019
.gitattributes Initial commit Jul 12, 2015
.gitignore Refactored moment.js out of app Apr 1, 2018
.travis.yml Fixed heavy init breakages made in last commit Nov 19, 2017
LICENSE Updated readme, license and added code of conduct Mar 25, 2018
artisan Fixed heavy init breakages made in last commit Nov 19, 2017
composer.json Updated socialite to work around google+ API shutdown Jan 20, 2019
composer.lock Updated socialite to work around google+ API shutdown Jan 20, 2019
package-lock.json Cleaned up some existing tri-column views Mar 30, 2019
package.json Updated npm packages and migrated webpack css plugin Feb 3, 2019
phpunit.xml Updated readme with security info Mar 24, 2019
server.php Initial commit Jul 12, 2015


GitHub release license Build Status

A platform for storing and organising information and documentation. General information and documentation for BookStack can be found at

Project Definition

BookStack is an opinionated wiki system that provides a pleasant and simple out of the box experience. New users to an instance should find the experience intuitive and only basic word-processing skills should be required to get involved in creating content on BookStack. The platform should provide advanced power features to those that desire it but they should not interfere with the core simple user experience.

BookStack is not designed as an extensible platform to be used for purposes that differ to the statement above.

In regards to development philosophy, BookStack has a relaxed, open & positive approach. At the end of the day this is free software developed and maintained by people donating their own free time.

Road Map

Below is a high-level road map view for BookStack to provide a sense of direction of where the project is going. This can change at any point and does not reflect many features and improvements that will also be included as part of the journey along this road map. For more granular detail of what will be included in upcoming releases you can review the project milestones as defined in the "Release Process" section below.

  • Design Revamp (In Progress)
    • A more organised modern design to clean things up, make BookStack more efficient to use and increase mobile usability.
  • Platform REST API
    • A REST API covering, at minimum, control of core content models (Books, Chapters, Pages) for automation and platform extension.
  • Editor Alignment & Review
    • Review the page editors with goal of achieving increased interoperability & feature parity while also considering collaborative editing potential.
  • Permission System Review
    • Improvement in how permissions are applied and a review of the efficiency of the permission & roles system.
  • Installation & Deployment Process Revamp
    • Creation of a streamlined & secure process for users to deploy & update BookStack with reduced development requirements (No git or composer requirement).

Release Versioning & Process

BookStack releases are each assigned a version number, such as "v0.25.2", in the format v<phase>.<feature>.<patch>. A change only in the patch number indicates a fairly minor release that mainly contains fixes and therefore is very unlikely to cause breakages upon update. A change in the feature number indicates a release which will generally bring new features in addition to fixes and enhancements. These releases have a small chance of introducing breaking changes upon update so it's worth checking for any notes in the update guide. A change in the phase indicates a much large change in BookStack that will likely incur breakages requiring manual intervention.

Each BookStack release will have a milestone created with issues & pull requests assigned to it to define what will be in that release. Milestones are built up then worked through until complete at which point, after some testing and documentation updates, the release will be deployed.

For feature releases, and some patch releases, the release will be accompanied by a post on the BookStack blog which will provide additional detail on features, changes & updates otherwise the GitHub release page will show a list of changes. You can sign up to be alerted to new BookStack blogs posts (once per week maximum) at this link.

Development & Testing

All development on BookStack is currently done on the master branch. When it's time for a release the master branch is merged into release with built & minified CSS & JS then tagged at its version. Here are the current development requirements:

SASS is used to help the CSS development and the JavaScript is run through babel to allow for writing ES6 code. This is done using webpack. To run the build task you can use the following commands:

# Install NPM Dependencies
npm install

# Build assets for development
npm run build

# Build and minify assets for production
npm run production

# Build for dev (With sourcemaps) and watch for changes
npm run dev

BookStack has many integration tests that use Laravel's built-in testing capabilities which makes use of PHPUnit. To use you will need PHPUnit 6 installed and accessible via command line, Directly running the composer-installed version will not work. There is a mysql_testing database defined within the app config which is what is used by PHPUnit. This database is set with the following database name, user name and password defined as bookstack-test. You will have to create that database and credentials before testing.

The testing database will also need migrating and seeding beforehand. This can be done with the following commands:

php artisan migrate --database=mysql_testing
php artisan db:seed --class=DummyContentSeeder --database=mysql_testing

Once done you can run phpunit in the application root directory to run all tests.


All text strings can be found in the resources/lang folder where each language option has its own folder. To add a new language you should copy the en folder to an new folder (eg. fr for french) then go through and translate all text strings in those files, leaving the keys and file-names intact. If a language string is missing then the en translation will be used. To show the language option in the user preferences language drop-down you will need to add your language to the options found at the bottom of the resources/lang/en/settings.php file. A system-wide language can also be set in the .env file like so: APP_LANG=en.

You will also need to add the language to the locales array in the config/app.php file.

There is a script available which compares translation content to en files to see what items are missing or redundant. This can be ran like so from your BookStack install folder:

# Syntax
php resources/lang/check.php <lang>

# Examples
php resources/lang/check.php fr
php resources/lang/check.php pt_BR

Some strings have colon-prefixed variables in such as :userName. Leave these values as they are as they will be replaced at run-time.

Contributing & Maintenance

Feel free to create issues to request new features or to report bugs and problems. Just please follow the template given when creating the issue.

The project's code of conduct can be found here.

Code Standards

PHP code within BookStack is generally to PSR-2 standards. From the BookStack root folder you can run ./vendor/bin/phpcs to check code is formatted correctly and ./vendor/bin/phpcbf to auto-fix non-PSR-2 code.

Pull Requests

Pull requests are welcome. Unless a small tweak or language update, It may be best to open the pull request early or create an issue for your intended change to discuss how it will fit in to the project and plan out the merge.

Pull requests should be created from the master branch since they will be merged back into master once done. Please do not build from or request a merge into the release branch as this is only for publishing releases.

If you are looking to alter CSS or JavaScript content please edit the source files found in resources/assets. Any CSS or JS files within public are built from these source files and therefore should not be edited directly.

Website, Docs & Blog

The website which contains the project docs & Blog can be found in the BookStackApp/website repo.


Security information for administering a BookStack instance can be found on the documentation site here.

If you'd like to be notified of new potential security concerns you can sign-up to the BookStack security mailing list.

If you would like to report a security concern in a more confidential manner than via a GitHub issue, You can directly email the lead maintainer ssddanbrown. You will need to login to be able to see the email address on the GitHub profile page. Alternatively you can send a DM via twitter to @ssddanbrown.


The BookStack source is provided under the MIT License.


The great people that have worked to build and improve BookStack can be seen here.

These are the great open-source projects used to help build BookStack:

You can’t perform that action at this time.