4c7d6420ee
As per PR #5800 * DB: Planned out new entity table format via migrations * DB: Created entity migration logic Made some other tweaks/fixes while testing. * DB: Added change of entity relation columns to suit new entities table * DB: Got most view queries working for new structure * Entities: Started logic change to new structure Updated base entity class, and worked through BaseRepo. Need to go through other repos next. Removed a couple of redundant interfaces as part of this since we can move the logic onto the shared ContainerData model as needed. * Entities: Been through repos to update for new format * Entities: Updated repos to act on refreshed clones Changes to core entity models are now done on clones to ensure clean state before save, and those clones are returned back if changes are needed after that action. * Entities: Updated model classes & relations for changes * Entities: Changed from *Data to a common "contents" system Added smart loading from builder instances which should hydrate with "contents()" loaded via join, while keeping the core model original. * Entities: Moved entity description/covers to own non-model classes Added back some interfaces. * Entities: Removed use of contents system for data access * Entities: Got most queries back to working order * Entities: Reverted back to data from contents, fixed various issues * Entities: Started addressing issues from tests * Entities: Addressed further tests/issues * Entities: Been through tests to get all passing in dev Fixed issues and needed test changes along the way. * Entities: Addressed phpstan errors * Entities: Reviewed TODO notes * Entities: Ensured book/shelf relation data removed on destroy * Entities: Been through API responses & adjusted field visibility * Entities: Added type index to massively improve query speed
BookStack
A platform for storing and organising information and documentation. Details for BookStack can be found on the official website at https://www.bookstackapp.com/.
- Installation Instructions
- Documentation
- Demo Instance
- Screenshots
- BookStack Blog
- Issue List
- Discord Chat
- Support Options
📚 Project Definition
BookStack is an opinionated documentation platform 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 regard to development philosophy, BookStack has a relaxed, open & positive approach. We aim to slowly yet continuously evolve the platform while providing a stable & easy upgrade path.
You can read more about the project and its origins in our FAQ here.
🌟 Project Sponsors
Shown below are our bronze, silver and gold project sponsors. Big thanks to these companies for supporting the project. Note: The listed services are not tested, vetted nor supported by the official BookStack project in any manner.
Project donation details - GitHub Sponsors Page - Ko-fi Page
Gold Sponsor
|
|
Bronze Sponsors
|
|
|
|
|
|
|
|
|
|
🛠️ Development & Testing
Please see our development docs for full details regarding work on the BookStack source code.
If you're just looking to customize or extend your own BookStack instance, take a look at our Hacking BookStack documentation page for details on various options to achieve this without altering the BookStack source code.
Details about BookStack's versioning scheme and the general release process can be found here.
🌎 Translations
Translations for text within BookStack are managed through the BookStack project on Crowdin. Some strings have colon-prefixed variables such as :userName. Leave these values as they are as they will be replaced at run-time.
Please use Crowdin to contribute translations instead of opening a pull request. The translations within the working codebase can be out-of-date, and merging via code can cause conflicts & sync issues. If for some reason you can't use Crowdin feel free to open an issue to discuss alternative options.
If you'd like a new language to be added to Crowdin, for you to be able to provide translations for, please open a new issue here.
Please note, translations in BookStack are provided to the "Crowdin Global Translation Memory" which helps BookStack and other projects with finding translations. If you are not happy with contributing to this then providing translations to BookStack, even manually via GitHub, is not advised.
🎁 Contributing, Issues & Pull Requests
Feel free to create issues to request new features or to report bugs & problems. Just please follow the template given when creating the issue.
Pull requests are welcome but, unless it's a small tweak, it may be best to open the pull request early or create an issue for your intended change to discuss how it will fit into the project and plan out the merge. Just because a feature request exists, or is tagged, does not mean that feature would be accepted into the core project.
Pull requests should be created from the development branch since they will be merged back into development 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/. Any CSS or JS files within public are built from these source files and therefore should not be edited directly.
The project's code of conduct can be found here.
🔒 Security
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, details of doing so can be found here.
♿ Accessibility
We want BookStack to remain accessible to as many people as possible. We aim for at least WCAG 2.1 Level A standards where possible although we do not strictly test this upon each release. If you come across any accessibility issues please feel free to open an issue.
🖥️ Website, Docs & Blog
The website which contains the project docs & blog can be found in the BookStackApp/website repo.
⚖️ License
The BookStack source is provided under the MIT License.
The libraries used by, and included with, BookStack are provided under their own licenses and copyright. The licenses for many of our core dependencies can be found in the attribution list below but this is not an exhaustive list of all projects used within BookStack.
👪 Attribution
The great people that have worked to build and improve BookStack can be seen here. The wonderful people that have provided translations, either through GitHub or via Crowdin can be seen here.
Below are the great open-source projects used to help build BookStack. Note: This is not an exhaustive list of all libraries and projects that would be used in an active BookStack instance.
- Laravel - MIT
- TinyMCE - MIT
- Lexical - MIT
- CodeMirror - MIT
- Sortable - MIT
- Google Material Icons - Apache-2.0
- markdown-it and markdown-it-task-lists - MIT and ISC
- Dompdf - LGPL v2.1
- KnpLabs/snappy - MIT
- WKHTMLtoPDF - LGPL v3.0
- diagrams.net - Embedded Version Terms / Source Project - Apache-2.0
- SAML PHP Toolkit - MIT
- League/CommonMark - BSD-3-Clause
- League/Flysystem - MIT
- League/html-to-markdown - MIT
- League/oauth2-client - MIT
- pragmarx/google2fa - MIT
- Bacon/BaconQrCode - BSD-2-Clause
- phpseclib - MIT
- Clockwork - MIT
- PHPStan & Larastan - MIT and MIT
- PHP_CodeSniffer - BSD 3-Clause
- JakeArchibald/IDB-Keyval - Apache-2.0
For a detailed breakdown of the JavaScript & PHP projects imported & used via NPM & composer package managers, along with their licenses, please see the dev/licensing/js-library-licenses.txt and dev/licensing/php-library-licenses.txt files.