two/web/components.yml
GnomeZworc b479493ac1
web: start: multiple pages
Signed-off-by: GnomeZworc <nicolas.boufidjeline@g3e.fr>
2026-06-01 21:40:26 +02:00

57 lines
1.8 KiB
YAML

# Component manifest — source of truth for the web UI.
#
# Edit this file, then run ./build.sh to:
# - download every remote component into components/<name>/
# - generate components.json (the runtime load list) in declared order
#
# Load order matters: service components (login-gate, api-client) must come
# before the components that consume them.
# Local components shipped inside this repo. Not downloaded — listed here only
# so build.sh can place them in the generated load order.
local_components:
- login-gate
- api-client
- side-nav
- logout-button
- side-panel
- date-display
# Remote components fetched from git at build time.
# Each is its own repo; its root must contain <name>.js and manifest.json.
#
# - name: vpc-panel # → components/vpc-panel/
# repo: https://git.g3e.fr/team-reseau/vpc-panel
# ref: v1.2.0 # tag, branch or commit (default: main)
components: []
# Pages — each page is a self-contained directory (JS + CSS + manifest.json).
# Same model as components: local pages ship in this repo, remote pages are
# downloaded from git at build time. build.sh reads each manifest.json to
# generate navigation.json and pages.json.
#
# Page manifest.json must contain: tag, route, label, icon.
# Page JS must: customElements.define('<tag>', ...) and use display:contents.
local_pages:
- dashboard
- vpcs
- subnets
- vms
# Remote pages fetched from git — same mechanism as components.
#
# - name: vpcs
# repo: https://git.g3e.fr/team-reseau/page-vpcs
# ref: v1.0.0
remote_pages: []
# Menu — order and visibility in the side-nav.
# List routes in desired display order.
# A page not listed here is accessible via /#/route but hidden from the nav.
menu:
- dashboard
- vpcs
- subnets
- vms