BookStack/resources/views
Dan Brown 9d149e4d36
Notifications: Linked watch functionality to UI
Got watch system working to an initial base state.
Moved some existing logic where it makes sense.
2023-08-02 13:14:00 +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 Notifications: Linked watch functionality to UI 2023-08-02 13:14:00 +01:00
chapters
comments Comments: Tweaked design to be more consistent and compact 2023-06-28 13:41:14 +01:00
common
entities Notifications: Linked watch functionality to UI 2023-08-02 13:14:00 +01:00
errors
exports
form Shelf permissions: reverted create removal 2023-07-12 22:04:05 +01:00
help
home
layouts
mfa
misc
pages Comments: Added read-only listing into page editor 2023-06-16 13:08:04 +01:00
search
settings Notifications: Added role receive-notifications permission 2023-07-25 17:59:04 +01:00
shelves Applied shelf book sort changes from testing 2023-02-17 16:18:24 +00:00
tags Played around with a new app structure 2023-05-17 17:56:55 +01:00
users Notifications: added user preference UI & logic 2023-07-25 17:08:40 +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