BookStack/resources/views
Dan Brown 56d07f1909
Users API: Fixed sending invite when using form requests
- Cast send_invite value in cases where it might not have been a boolean,
  which occurs on non-JSON requests.
- Added test to cover.
- Updated API docs to mention and shown boolean usage.
2023-12-13 15:13:54 +00:00
..
api-docs Users API: Fixed sending invite when using form requests 2023-12-13 15:13:54 +00:00
attachments
auth
books Default templates: Fixed syntax for php8.0, added test 2023-12-12 15:59:12 +00:00
chapters
comments
common URL Handling: Removed referrer-based redirect handling 2023-12-10 12:37:21 +00:00
entities Default templates: Added page picker and working forms 2023-12-11 15:58:27 +00:00
errors
exports
form Default templates: Cleaned up ux, added case for added endpoint 2023-12-12 15:38:09 +00:00
help
home Styles: Aligned empty state alignment & consistency 2023-10-23 11:53:19 +01:00
layouts Auth: Refactored OIDC RP-logout PR code, Extracted logout 2023-12-06 13:49:53 +00:00
mfa
misc
pages Default templates: Cleaned up ux, added case for added endpoint 2023-12-12 15:38:09 +00:00
search
settings Default templates: Added page picker and working forms 2023-12-11 15:58:27 +00:00
shelves Styles: Aligned empty state alignment & consistency 2023-10-23 11:53:19 +01:00
tags
users My Account: Updated and started adding to tests 2023-10-19 14:18:42 +01:00
vendor Locales: More use of locale objects, Addressed failing tests 2023-09-17 16:20:21 +01:00
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