BookStack/resources/views
Dan Brown 7751022c66
Updated migration to carry across more colors, updated export
Updated export to use link color for link.
Export will now copy primary color to link color options for stable
upgrades.
2023-01-28 17:49:48 +00:00
..
api-docs Updated a batch of JS components 2022-11-15 11:24:31 +00:00
attachments Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
auth Updated email confirmation flow so confirmation is done via POST 2022-11-12 15:11:59 +00:00
books Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
chapters Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
comments
common Update JS to show live changes and set light color values 2023-01-28 17:11:15 +00:00
entities Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
errors
exports Updated migration to carry across more colors, updated export 2023-01-28 17:49:48 +00:00
form Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
help
home Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
layouts Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
mfa Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
misc
pages Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
search Added new endpoint for search suggestions 2022-11-21 10:35:53 +00:00
settings Update JS to show live changes and set light color values 2023-01-28 17:11:15 +00:00
shelves Rolled out use of seperate link color style 2023-01-28 16:06:11 +00:00
tags
users Updated a whole load more js components 2022-11-15 16:04:46 +00: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