My site

# Specifications — OntoWave Bootstrap Interface **Language**: English (translation) — [Version française](interface.fr.md) **Status**: Living document — all implementations must conform — versioned by git --- ## 1. Founding Principle > **The HTML page is near-empty. The library creates all the DOM.** A correct OntoWave page contains only: ```html My site ``` The library creates the entire interface. **The user defines no DOM in HTML.** --- ## 2. Configuration Injection OntoWave **never fetches an external configuration file**. Configuration must be injected by the host page. Two APIs are available: ### Option A — `window.ontoWaveConfig` (recommended) The simplest API. Declare the configuration object directly in the page, before the library ` ``` The library reads `window.ontoWaveConfig` and automatically converts it to `window.__ONTOWAVE_BUNDLE__['/config.json']`. ### Option B — `window.__ONTOWAVE_BUNDLE__` (low-level API) Advanced API for pages/tools that need to inject multiple files (config, nav, sitemap, search-index) in a single operation: ```html ``` ### Behavior without configuration If neither API is defined, OntoWave starts in **minimal monolingual mode**: - Default config: `{ roots: [{ base: '/', root: '/' }] }` - Loads the home page: `#/index.md` - No network request to find a configuration --- ## 3. Automatic Bootstrap On load, `bootstrapDom()` applies this algorithm: ``` 1. Read configuration (§2 — injection only, never fetch) 2. If document.getElementById('app') exists → COMPLETE STOP (no DOM, no style, no menu — integration mode) 3. Otherwise → create full DOM: a. Inject