A lightweight vanilla HTML, CSS and JavaScript framework used by Electronic Artefacts for fast prototyping, public showcases and small production surfaces.
Electronic Artefacts Lightweight Template is a small front-end framework for composing static, content-led websites with HTML, CSS and browser JavaScript.
activepublishedv1.0.0
REPÈRES
Definition, sources and useful limits.
Start here for the practical frame: what the page covers, what it leaves aside and which references support it.
Principles
Framework commitments
Keep the canonical page readable as static HTML.
Use CSS and small browser scripts to enrich the interface without hiding the content model.
Prefer reusable partials, generated pages and progressive enhancement over a heavy runtime.
Keep public showcases inspectable, portable and easy to archive.
Limitations
Known constraints
It is not a general-purpose application framework.
It is intended for static surfaces, editorial systems, prototypes and compact public interfaces.
Larger products may still need a dedicated runtime, API layer or application framework.
Topics
Tags and disciplines
HTMLCSSJavaScriptStatic SiteProgressive EnhancementFront-end FrameworkWeb DevelopmentDesign TechnologyCreative TechnologyKnowledge Systems
Role
Electronic Artefacts Lightweight Template is the small front-end framework used by the studio to assemble fast, inspectable web surfaces. It favours static HTML, reusable partials, bundled CSS and focused browser JavaScript rather than a heavy client-side application shell.
Use on this site
This public Electronic Artefacts website is composed in part with the framework. The canonical content comes from typed records and generated HTML, while the framework layer shapes navigation, layout, interface behaviours, search surfaces, language switching and progressive enhancements.
The point is not to present the framework as a separate commercial platform. It is the lightweight composition layer behind parts of the site itself: a practical system for making editorial, research and showcase pages feel coherent without turning every page into a full web application.
Principles
Static pages should remain readable before JavaScript runs.
Interface enhancements should support navigation, search, sharing and orientation without replacing the document.
The CSS system should carry the visual identity without requiring a design-system dependency.
Public pages should remain easy to crawl, archive and cite.
Boundaries
The framework is deliberately small. It does not replace VASTE, Forge or any larger Electronic Artefacts runtime. It also does not claim to be the right foundation for every product. Its role is narrower: compose lightweight public surfaces where HTML, CSS and JavaScript are enough.