As a little Christmas-time treat we have BookStack v23.12 slipping in as the last
release of the year. This release focuses on providing a simple WYSIWYG editor
-for description inputs and default page templates within books, among some other additional gifts.
+for description inputs, along with adding default page templates within books,
+in addition to some other additional gifts.
* [Update instructions](/docs/admin/updates)
* [GitHub release page](https://github.com/BookStackApp/BookStack/releases/tag/v23.12)
**Upgrade Notices**
-TODO - Copy to updates page
-
- **Page Includes** - The way page include content is fetched & merged has changed significantly in this release,
- which may in some cases alter how included content appears on the page.
-- **Prior Security Release** - Prior version v23.10.3 was a security release. If you missed this before, further details about that [can be found here](/blog/bookstack-release-v23-10-3/).
+ which in some cases may alter how included content appears on the page.
+- **Prior Security Release** - Prior version v23.10.3 was a security release. If you missed this before, further details about that [can be found on the blog here](/blog/bookstack-release-v23-10-3/).
Video - TODO
<!-- {{<pt 4YtVndveEVE6GuuGPV3Yn1>}} -->
### WYSIWYG Editor for Descriptions
-In BookStack we have description fields for chapters, books and shelves which allow a little bit of explanation and context to be provided for those items.
+In BookStack we have description fields for chapters, books and shelves which allow a little bit of explanation & context to be provided for those items.
These have always been simple plaintext fields, but as of v23.12 you'll now see a simple WYSIWYG input box instead with a few formatting controls:
-TODO - Image of description field
+
Formatting options include, and are limited to: bold, italic, links, bullet lists and numbered lists.
The formatting is purposefully limited here to keep main content within pages, but allow a little formatting along with linking to relevant pages where required.
Since links can now be placed within descriptions, references to other items will now be tracked via the existing reference system:
-TODO - Image of page references, references by a shelf, chapter and book.
+
-For API users, new `description_html` fields now exist on responses and requests to interact with this field in a HTML-aware manner, otherwise the pre-existing `description` fields will continue to work as before.
+For API users, new `description_html` fields now exist on responses & requests to interact with this field in a HTML-aware manner, otherwise the pre-existing `description` fields will continue to work as before.
### Default Template For New Book Pages
-We've long since supported page [templates](/docs/user/page-templates/) within BookStack but to be used the user would have to access the relevant sidebar menu within the page editor, leading to them being easy to miss. Additionally, it would be a common desire to use a template for all pages created within a certain context.
+We've long since supported page [templates](/docs/user/page-templates/) within BookStack but to be used an editing user would have to access the relevant sidebar menu within the page editor, meaning they could be easy to miss or ignore. Additionally, it would be a common desire to use a template for all pages created within a certain context.
In this release, a new option for books allows you to set a default page template:
-TODO - Image of option
+
When set, this template page will be used as the default content for all new pages within that book, preventing the need to select the template within the editor each time you create something new. Note though, this is still permission controlled so the template will only be used if the page creator has view access to the template assigned.
### OIDC RP-Initiated Logout
OpenID-Connect authentication in BookStack allows for easy login via an external system, but so far it's lacked any kind of logout support.
-That changes in this release thanks for efforts by [@joancyho](https://github.com/BookStackApp/BookStack/pull/4467) to introduce OIDC RP-Initiated logout support.
+That changes in this release thanks to efforts by [@joancyho](https://github.com/BookStackApp/BookStack/pull/4467) to introduce OIDC RP-Initiated logout support.
This official [complementary part of the OIDC spec](https://openid.net/specs/openid-connect-rpinitiated-1_0.html) allows an application like BookStack to request logout of the external authentication system as part of the application's logout flow.
BookStack's support of this includes the use of autodiscovery to learn the logout endpoint.
It's likely you'll need to also configure logout/sign-out URIs on your OIDC authentication system for your BookStack application instance.
Our [OIDC documentation](/docs/admin/oidc-auth/#authentication-system-configuration) has been updated with details of these URIs.
+During testing I've validated this system to work with Okta, KeyCloak, Azure, Authentik and Auth0; so support for this part of the
+standard by authentication services seems pretty widespread.
+
### Page Context in Email Notifications
A couple of releases ago we added email notifications for certain page activities, and these notifications would include
page name alone since it could be a page name used multiple times, or lacking context without knowing where that page is located.
To help add that context, notifications will now reflect the page parent book, and chapter if within:
-TODO - Image of notification with page parent context including chapter
+
A big thanks to [@Man-in-Black](https://github.com/BookStackApp/BookStack/pull/4629) for contributing this functionality.
For this release, the design of buttons has been tweaked a little to better fit them into the current design, rounding the corners
a little more, tweaking the shadows upon hover and, most importantly, using the casing from the source translation text:
-TODO - Image of buttons
+
In most cases buttons will now appear as Title Case, although this can now change to suit different languages as needed as it's not forced
by design.
cases due to nested paragraphs and other oddities, which may cause unpredictable issues in how pages would display
with include tags.
-In this release, the engine for page include tags has been rebuilt to specifically be more content aware
+In this release, the engine for page include tags has been rebuilt to specifically be more content aware,
avoiding invalid structure where possible by smartly splitting existing blocks or moving included content to
appropriate locations if needed.
### Translations
-One again a big thanks to all the exceptionally eloquent experts in language who've contributed
+Before the year closes out we have one more new language made available in BookStack, and that is Finnish!
+A big thanks to the [Crowdin user ajnyga](https://crowdin.com/profile/ajnyga/activity) for all their efforts
+translating for Finnish up to the point where we can include it.
+
+Once again a big thanks to all the exceptionally eloquent experts in language who've contributed
translations since our last feature release:
-TODO
+- Eduard Ereza Martínez (Ereza) - *Catalan - 7160 words*
+- Antti-Jussi Nygård (ajnyga) - *Finnish - 6108 words*
+- Guttorm Hveem (guttormhveem) - *Norwegian Nynorsk; Norwegian Bokmal - 2718 words*
+- toras9000 - *Japanese - 1045 words*
+- Vitaliy (gviabcua) - *Ukrainian - 922 words*
+- poesty - *Chinese Simplified - 635 words*
+- Jabir Lang (amar.almrad) - *Arabic - 480 words*
+- Sascha (Man-in-Black) - *German Informal; German - 443 words*
+- pedromcsousa - *Portuguese - 372 words*
+- Jaroslav Koblizek (foretix) - *Czech; French - 365 words*
+- Felipe Cardoso (felipecardosoruff) - *Portuguese, Brazilian - 348 words*
+- SmokingCrop - *Dutch - 324 words*
+- sdhadi - *Persian - 284 words*
+- Indrek Haav (IndrekHaav) - *Estonian - 250 words*
+- Konstantin (kkovacheli) - *Ukrainian; Russian - 246 words*
+- Wiktor Adamczyk (adamczyk.wiktor) - *Polish - 184 words*
+- Maciej Lebiest (Szwendacz) - *Polish - 164 words*
+- Abdulmajeed Alshuaibi (4Majeed) - *Arabic - 114 words*
+- scureza - *Italian - 99 words*
+- m0uch0 - *Spanish - 99 words*
+- HyoungMin Lee (ddokkaebi) - *Korean - 67 words*
+- Dasferco - *Chinese Simplified - 64 words*
+- NotSmartZakk - *Czech - 62 words*
+- TheRazvy - *Romanian - 55 words*
+- Martins Pilsetnieks (pilsetnieks) - *Latvian - 49 words*
+- balmag - *Hungarian - 25 words*
+- Serkan Yardim (serkanzz) - *Turkish - 14 words*
+- LameeQS - *Latvian - 12 words*
+- Marcus Teräs (mteras) - *Finnish - 10 words*
+- Y (cnsr) - *Ukrainian - 7 words*
+- ZY ZV (vy0b0x) - *Chinese Simplified - 6 words*
+- diegobenitez - *Spanish - 4 words*
+- Sorin T. (trimbitassorin) - *Romanian - 3 words*
+- Marc Hagen (MarcHagen) - *Dutch - 1 words*
-- User - *Language - x words*
*\* Word counts are those tracked by Crowdin, indicating original EN words translated.*
### Next Steps
-Now we have a simpler WYSIWYG editor, as implemented for descriptions in this release, I'll probably be looking to carry this across to the comments system to provide that with simple WYSIWYG editing, although this will require some breaking changes to the currently supported markdown content of this input. Upon that, over the initial few weeks of this year I'd like to explore some of the new PHP-ecosystem technologies like roadrunner and/or FrankenPHP to understand their potential benefit to BookStack.
+Now we have a simpler WYSIWYG editor, as implemented for descriptions in this release, I'll probably be looking to carry this across to the comments system to provide that with simple WYSIWYG editing, although this will require some breaking changes to the currently supported markdown content of this input.
+
+Upon that, over the initial few weeks of this year I'd like to explore some of the new PHP-ecosystem technologies like roadrunner and/or FrankenPHP to understand their potential benefit to BookStack.
Over the next few days I'll be putting together a "BookStack in 2023" blogpost, like [done previous years](https://www.bookstackapp.com/blog/bookstack-in-2022/) to look back and assess the progress of the project over the last year.