BookStack/resources/views
Tushar Nain 6a5361d853
Fixed : Comment notification settings are visible even if comments are disabled
Added a UX condition to display comment notification settings, only if the user has enabled the comment notifications.
2023-09-16 14:00:08 +05:30
..
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 Views: Rolled out ID to similar recent activity lists 2023-09-11 18:50:39 +01:00
chapters Notifications: Fixed issues causing failing tests 2023-08-17 14:59:28 +01:00
comments Comments: Tweaked design to be more consistent and compact 2023-06-28 13:41:14 +01:00
common Drawio: Added unsaved restore prompt and logic 2023-08-23 14:16:20 +01:00
entities Simplified and aligned handling of mixed entity endpoints 2023-09-10 15:19:23 +01:00
errors
exports
form Shelf permissions: reverted create removal 2023-07-12 22:04:05 +01:00
help
home Views: Rolled out ID to similar recent activity lists 2023-09-11 18:50:39 +01:00
layouts Theme: Added handling for functions.php file load error 2023-09-12 12:34:02 +01:00
mfa
misc
pages Drawio: Added unsaved restore prompt and logic 2023-08-23 14:16:20 +01:00
search
settings Notifications: User watch list and differnt page watch options 2023-08-14 13:11:18 +01:00
shelves Views: Rolled out ID to similar recent activity lists 2023-09-11 18:50:39 +01:00
tags
users Fixed : Comment notification settings are visible even if comments are disabled 2023-09-16 14:00:08 +05:30
vendor Notifications: Aligned how user language is used 2023-09-02 15:11:42 +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