BookStack/resources/views
Dan Brown 3625f12abe
Added extendable/scalable formatter for webhook data
Creates a new organsied formatting system for webhook data, with
interfaces for extending with custom model formatting rules.
Allows easy usage & extension of the default bookstack formatting
behaviour when customizing webhook events via theme system, and keeps
default data customizations organised.

This also makes the following webhook data changes:
- owned_by/created_by/updated_by user details are loaded for events with
  Entity details. (POTENTIALLY BREAKING CHANGE).
- current_revision details are loaded for page update/create events.

Added testing to cover added model formatting rules.

For #3279 and #3218
2022-03-26 16:53:02 +00:00
..
api-docs
attachments
auth
books
chapters
comments
common Aligned some editor events, Changed wysiwyg custom styles loading 2022-02-08 01:01:37 +00:00
entities
errors Added help/about box to wysiwyg editor 2022-02-07 23:19:04 +00:00
form
help Added ctrl+shift+k shortcut to WYSIWYG 2022-02-28 13:34:32 +00:00
home
layouts Updated CSP with frame-src rules 2022-03-07 14:27:41 +00:00
mfa
misc
pages Updated tinymce link query to break caches 2022-02-27 16:03:18 +00:00
search
settings Added extendable/scalable formatter for webhook data 2022-03-26 16:53:02 +00:00
shelves
tags
users Added user-update API endpoint 2022-02-03 16:52:28 +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