BookStack/resources/views
2023-10-19 16:37:55 +01:00
..
api-docs API Docs: Allowed multi-paragraph descriptions 2023-06-20 23:44:39 +01:00
attachments Allowed attachment drag via main text link 2023-05-22 20:23:19 +01:00
auth
books Print Styles: Fixed header/footer content showing 2023-10-03 14:59:35 +01:00
chapters Guest control: Cleaned methods involved in fetching/handling 2023-09-16 13:18:35 +01:00
comments Comments: Tweaked design to be more consistent and compact 2023-06-28 13:41:14 +01:00
common Header: Simplified, split and re-orgranised view file(s) 2023-09-24 10:29:51 +01:00
entities My Acount: Updated old preference url reference for watches 2023-10-19 16:37:55 +01:00
errors Guest control: Cleaned methods involved in fetching/handling 2023-09-16 13:18:35 +01:00
exports
form Shelf permissions: reverted create removal 2023-07-12 22:04:05 +01:00
help
home Homepage: Made much nicer at ipad-like widths 2023-10-07 12:38:54 +01:00
layouts My Account: Cleaned-up/reorganised user header dropdown 2023-10-18 17:57:14 +01:00
mfa
misc
pages Editors: Adjusted new design for mobile and dark mode 2023-10-14 17:10:29 +01:00
search Guest control: Cleaned methods involved in fetching/handling 2023-09-16 13:18:35 +01:00
settings Users: Built out auth page for my-account section 2023-10-17 17:38:07 +01:00
shelves Print Styles: Fixed header/footer content showing 2023-10-03 14:59:35 +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