Shared Shell & Tool Directory
Framework-agnostic design tokens, brand shell, bilingual content templates, registry validation and static assembly for 20 independent tool sites.Local directory index
Operations
- This site provides the shared directory and public resources.
Real examples and limits
P00 ships only shared specifications and a static directory: no tool engines and no substitution for another project’s acceptance. All 20 registry sites are planned this round, so the directory produces no accessible links. Search matches a local in-browser index and never logs the search text. Each site must copy the shared CSS/analytics adapter into its own artifact; there is no runtime CDN dependency.
FAQ
Does P00 provide a shared React component library?
No. The shell is namespaced CSS (.al-shell / .al-*), a framework-free header-footer.html structure and zero-dependency ESM helpers; React/Vue/Svelte/Preact/Astro all work. site-shell/adapters/README.md contains minimal Vue 3 and Svelte 5 adapters.
Why are the directory tools not linked?
All 20 sites are planned this round. scripts/validate-registry.mjs hard-rejects a planned site carrying url/href/link/plannedOrigin, so no dead entries appear. Only a live site with a real check record may link to https://<id>.ailounge.top.
Are analytics and ads enabled by default?
Neither. window.ALAnalytics is a no-op without configuration/consent or when its script fails, and never blocks a tool; events and fields are whitelisted. Ad slots are off by default, content pages only, never in the isolated work area.
Does subpath deployment require code changes?
No business code change, but a rebuild is required: npm run build:basepath emits /sandbox/directory/ prefixed output with every link generated by createUrlHelper in site-shell/url.ts. An Nginx rewrite alone cannot hide hardcoded asset paths.