SDECB

Portal v2 Architecture

Goal: A static, modern portal that can browse/search KB content without requiring a backend.

Key idea

Portal v2 is a set of HTML pages under portal/v2/ that load pre-built JSON indexes from portal/v2/data/.

Those JSON files are generated from canonical sources in the repo (podcasts, interviews, website scrape export).

Files

UI

portal/v2/index.html — dashboard
portal/v2/knowledge_base.html — unified search UI
portal/v2/podcast_explorer.html — episode browser + detail view
portal/v2/governance.html — links into governance docs
portal/v2/training.html — links into training docs

Shared styles

portal/v2/styles/theme.css — tokens
portal/v2/styles/components.css — UI components
portal/v2/styles/utilities.css — layout helpers
portal/v2/styles/animations.css — minimal animations

Shared JS

portal/v2/components/nav.js — top navigation + language toggle
portal/v2/components/language_toggle.js — FR/EN toggle (localStorage)
portal/v2/components/search.js — simple client-side search/ranking
portal/v2/components/card.js — card renderer helper

Data

portal/v2/data/unified_index.json
portal/v2/data/podcasts_index.json
portal/v2/data/interviews_index.json
portal/v2/data/website_index.json

Data flow

flowchart TD
  podcasts[Podcasts corpus] --> ingestPod[ingest_podcast_kb.py]
  interviews[Interviews corpus] --> ingestInt[ingest_interviews_kb.py]
  websiteExport[Website export] --> ingestWeb[ingest_website_content.py]

  ingestPod --> kbPod[kb/podcasts/index.json]
  ingestInt --> kbInt[kb/interviews/index.json]
  ingestWeb --> kbWeb[kb/website/index.json]

  kbPod --> unified[build_unified_kb_index.py]
  kbInt --> unified
  kbWeb --> unified

  unified --> portalData[portal/v2/data/*.json]
  portalData --> portalUI[Portal v2 pages]

Why this approach

Keeps canonical content where it already lives
Avoids a backend until it’s clearly needed
Makes UI fast and portable
Makes future upgrades easy (server-side search, embeddings, auth)