BookStack/resources/views
Dan Brown 0bc9ddd780
A11y: Updated other dropdown menus with correct tagging
Made some form improvements at the same time.
2025-08-07 16:37:18 +01:00
..
api-docs
attachments Attachments: Hid edit/delete controls where lacking permission 2024-12-11 20:38:30 +00:00
auth
books Lexical: Added new WYSIWYG to chapter/book/shelf descriptions 2025-06-26 11:00:17 +01:00
chapters Lexical: Added new WYSIWYG to chapter/book/shelf descriptions 2025-06-26 11:00:17 +01:00
comments Comments: Switched to lexical editor 2025-06-25 14:16:01 +01:00
common A11y: Updated other dropdown menus with correct tagging 2025-08-07 16:37:18 +01:00
entities A11y: Updated other dropdown menus with correct tagging 2025-08-07 16:37:18 +01:00
errors
exports ZIP Imports: Updated import form to show loading indicator 2024-11-22 21:36:42 +00:00
form Lexical: Added new WYSIWYG to chapter/book/shelf descriptions 2025-06-26 11:00:17 +01:00
help Lexical: Added about button/view 2024-12-17 22:40:28 +00:00
home
layouts A11y: Improved tagging of profile menu 2025-08-07 14:32:20 +01:00
mfa
misc Opensearch: Fixed XML declaration when php short tags enabled 2025-07-01 11:29:16 +01:00
pages A11y: Updated other dropdown menus with correct tagging 2025-08-07 16:37:18 +01:00
search
settings A11y: Updated other dropdown menus with correct tagging 2025-08-07 16:37:18 +01:00
shelves Lexical: Added new WYSIWYG to chapter/book/shelf descriptions 2025-06-26 11:00:17 +01:00
tags
users A11y: Updated other dropdown menus with correct tagging 2025-08-07 16:37:18 +01:00
vendor
readme.md

BookStack Views

All views within this folder are Laravel blade views.

Overriding

Views can be overridden on a per-file basis via the visual theme system. More information on this can be found within the dev/docs/visual-theme-system.md file within this project.

Convention

Views are broken down into rough domain areas. These aren't too strict although many of the folders here will often match up to a HTTP controller.

Within each folder views will be structured like so:

- folder/
    - page-a.blade.php
    - page-b.blade.php
    - parts/
        - partial-a.blade.php
        - partial-b.blade.php
    - subdomain/
        - subdomain-page-a.blade.php
        - subdomain-page-b.blade.php
        - parts/
            - subdomain-partial-a.blade.php
            - subdomain-partial-b.blade.php

If a folder contains no pages at all (For example: attachments, form) and only partials, then the partials can be within the top-level folder instead of pages to prevent unneeded nesting.

If a partial depends on another partial within the same directory, the naming of the child partials should be an extension of the parent. For example:

- tag-manager.blade.php
- tag-manager-list.blade.php
- tag-manager-input.blade.php