BookStack/resources/views
Dan Brown 45ce7a7126
URL Handling: Removed referrer-based redirect handling
Swapped back handling to instead be pre-determined instead of being
based upon session/referrer which would cause inconsistent results when
referrer data was not available (redirect to app-loaded images/files).

To support, this adds a mechansism to provide a URL through request
data.

Also cleaned up some imports in code while making changes.
Closes #4656.
2023-12-10 12:37:21 +00:00
..
api-docs
attachments
auth
books Styles: Aligned empty state alignment & consistency 2023-10-23 11:53:19 +01:00
chapters
comments
common URL Handling: Removed referrer-based redirect handling 2023-12-10 12:37:21 +00:00
entities URL Handling: Removed referrer-based redirect handling 2023-12-10 12:37:21 +00:00
errors
exports
form
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
search
settings Dropdowns: Fixed bad direction logic, added dynmaic height 2023-11-07 15:07:11 +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
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