admin/39948-vm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated documentation

Browse Source
This commit is contained in:
Dmitri 2026-03-27 07:36:05 +04:00
parent 961241ecc7
commit b9ca9bbc10
2 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -148,6 +148,11 @@ Pages have an `environment` field (`dev`, `stage`, `production`) that determines
| `audio_player` | Audio player |
| `popup` | Modal popup |
**Element Defaults:** Each element type has configurable default settings that follow a three-tier hierarchy:
- **Global** (`element_type_defaults`) - Platform-wide defaults (auto-seeded)
- **Project** (`project_element_defaults`) - Per-project overrides (auto-snapshotted on project creation)
- **Instance** (`tour_pages.ui_schema_json`) - Page-specific element values
## API Overview
Base URL: `http://localhost:8080/api`

14
frontend/README.md
View File

@ -233,6 +233,20 @@ The tour builder supports these UI elements:
| `audio_player` | Audio player |
| `popup` | Popup/modal |
### Element Defaults Hierarchy
Element types follow a three-tier defaults system:
1. **Global** (`element_type_defaults`) - Platform-wide default settings (11 predefined types)
2. **Project** (`project_element_defaults`) - Project-specific overrides (auto-snapshotted on project creation)
3. **Instance** (`tour_pages.ui_schema_json`) - Page-specific element instances with custom settings
The constructor fetches project defaults via `/api/project-element-defaults?projectId=xxx` and merges them when creating new elements. Existing element values in `ui_schema_json` take precedence over defaults.
**Key files:**
- `types/constructor.ts` - `normalizeElementDefault()`, `buildElementDefaultsMap()` utilities
- `pages/constructor.tsx` - Loads project defaults, creates elements with merged settings
## Content Environments
Tour pages have a three-tier environment model: