Beta Release v0.20.0
Dan Brown posted on the 11th of February 2018
Here we have the first release of 2018 and it’s a chunky one! Not only do we have draw.io integration but thanks to a range of contributors we have extra languages and authentication options. Additionally, In this release we are testing options for theming as well as authenticated image access.
Often when creating documentation there are some things that are much better explained as drawings rather than text hence why drawing support had been requested a few times for BookStack. Creating our own solution is a bit too much work for a project like BookStack to take on but in this release I’m pleased to introduce Draw.io integration as a solution for creating drawings.
Previously you could create a drawing on draw.io then export it as an image to then upload into BookStack but this user flow is clunky and slow. Now there’s a drawing button in both the WYSIWYG and Markdown editors that will load in draw.io and create drawings without leaving BookStack.
When you save the drawing it will be uploaded to BookStack. You can then continue editing the image by double-clicking the drawing from the page editor.
There are a couple of things to note with the current implementation. Updating a drawing will overwrite the file in BookStack instantly. Even if you don’t save the page the drawing will be updated. In addition, There is no current way to delete drawings. In the near future we plan to implement some level of ‘drawing manager’ which will allow drawing versioning and deletion control. If you expect a high level of drawings to be created and you’re low on disk space you may want to disable draw.io support for now.
The Draw.io integration can be disabled from your
.env file by setting
Chinese and Swedish Language Support
For anyone wishing to help with adding or updating translations, Details of doing so can be found in the project readme. The readme details the use of a helper script to speed up the process of finding missing or unused translations.
GitLab and Twitch Authentication Options
Book Grid Enhancements
The last BookStack release included the new grid view for the books page. Since then, Thanks to @Abijeet, Switching between the grid and list view has been made more intuitive and now only requires clicking the appropriate link situated on the left of the header bar. The old user-profile option for this has been removed accordingly. In addition, The book grid will now properly align to provide a cleaner grid format:
Authenticated Image Access
Previously images could not be secured behind authentication like page content itself due to performance concerns. With this release authenticated image access is being trialled. This prevents image access to anyone not logged in if your instance is not publicly accessible. On larger instances and on pages with many images there could still be performance concerns so use this feature with caution.
Groundwork for Theming
Some initial work for support custom views and themes has been added. BookStack is built on Laravel and therefore uses blade template files for rendering page content. This new system allows you to selectively override any blade view file that BookStack uses without altering any original BookStack code.
Note that this feature is very early-on in its implementation and using it in a production environment is not advised at this time.
After updating, You’ll find a
themes folder in the top-folder-level of your BookStack install. Within this folder you can create a folder, ‘my-custom-theme’ for example, to house your view overrides. Within your
.env file you can then set
APP_THEME=my-custom-theme. When loading a view BookStack will then look in your specified theme folder before then defaulting to the stock BookStack views. The view will need to match the name and folder structure as those within the
In a future release I plan to go over the views and considerably clean them up to make things more consistent, modular and easier to override. This cleanup will cause breakages to existing themes so create themes with caution for now.
Full List of Changes
- Added Draw.io integration. (#632, #66, #619)
- Added language - Swedish. Thanks to @marcusforsberg. (#679)
- Added language - Simplified Chinese(zh-CN). Thanks to @yuezhihan. (#696)
- Added GitLab authentication. Thanks to @jozefbalun. (#691, #476, #349)
- Added Twitch authentication. Thanks to @moutonnoireu. (#684, #680)
- Added ability to secure images behind authentication. (#665)
- Added button to allow quick switching between grid and list book views. Thanks to @Abijeet. (#635, #613)
- Added utility command to delete all users from the system. Thanks to @Abijeet. (#621, #579)
- Added utility command to add an admin user. (#609)
- Added ‘.env’ option to set default books view. (#675)
- Updated book sort operation to check permission of all involved entities before sorting. Thanks to @Abijeet. (#651)
- Updated books ‘Grid’ view so it now uses CSS grid so books align in height. (#701)
- Standardised PHP code to follow PSR-2. (#649)
- Corrected the example configuration for okta auth. Thanks to @lommes. (#692)
- Fixed long code block lines going off the page on PDF exports. (#676)
- Fixed long text pushing out the view width on mobile devices when viewing books and chapters. (#669)
- Fixed bug causing markdown editor preview to collapse. (#658)
- Fixed bug causing page to refresh when clicking search in the image manager. (#697)
- Fixed styling issue preventing code editor save button from showing on smaller-screen devices. (#650)
- Fixed error thrown when user accesses an attachment without permission. (#681)
- Fixed font-size difference between list types in comments. Thanks to @Abijeet. (#644, #643)
- Fixed content includes to not break code structure if targeting a table or list. (#640)
As mentioned in the article above a ‘Drawing Manager’, similar to the ‘Image Manager’, would be a good addition. Maybe also some kind of ‘Image/Drawing Cleanup’ functionality would be good at this stage to find unused drawings and images on larger instances.
For other features please ensure you add a ‘Thumbs-up’ reaction on the parent post of any GitHub issue for desired features as it’s a really helpful way to identify the most requested features.
Header Image Credits: Sergey Zolkin