Genesis
Genesis is a CMS and static site generator written in PHP and JavaScript, with no framework and no npm dependency. It exports semantic HTML, readable by search engines and AI agents alike; this site is one of its outputs. Genny lives in the editor. She knows the whole site, block by block, keeps the rules and facts I give her, and holds the list of what remains to be done. She writes, translates, generates images, changes the layout, handles SEO and syntax. Genesis is her medium: I describe what I want, she builds it. I review, I post.
Technical sheet
Problem
The web is no longer read only by humans. Augmented search engines and AI agents analyze pages in depth: structure, semantics, load times, HTML clarity. Yet most CMSs and site builders produce heavy pages, saturated with scripts and dependencies. They answer marketing checkboxes more than a logic a machine can read. As soon as you add interactive content, a 3D scene, or a demo, the performance of the whole page degrades. And when AI is present, it is often reduced to a “generate” button. It writes into a void, without understanding the site, its context, or what already exists.
Response
Genesis brings the site structure, sections, blocks, design, and SEO into one visual interface, with live preview. The export produces static, semantic HTML pages enriched with Schema.org, metadata, the sitemap, feeds, and llms.txt. Content is available in French and English through model-based translation with review. WebGL 3D scenes are integrated in iframes without breaking performance. A single three.js engine is shared by all scenes. Each scene goes silent when it leaves the screen, rendering runs through a worker off the main thread, and loading is orchestrated.
The AI agent is built into the editor, not added as a simple text generator. It knows the whole page block by block, keeps an overview of the site, and helps maintain its consistency. It does not create a site structure in place of the CMS: it helps lay out pages from existing modules. It can suggest, improve, or take on a task, with validation before writing. It works with harnesses like Claude Code or Codex, which increase its working capacity. With Codex, it can also produce visuals. Before each write, the previous text is kept in a log, and nothing is published without validation.
The AI agent is built into the editor, not added as a simple text generator. It knows the whole page block by block, keeps an overview of the site, and helps maintain its consistency. It does not create a site structure in place of the CMS: it helps lay out pages from existing modules. It can suggest, improve, or take on a task, with validation before writing. It works with harnesses like Claude Code or Codex, which increase its working capacity. With Codex, it can also produce visuals. Before each write, the previous text is kept in a log, and nothing is published without validation.
Features
Genesis is not like any other tool.
It generates static websites with the flexibility of a dynamic CMS, integrating features designed to combine performance, full control, and simple use.
Some exist elsewhere. Others are unique.
Here is what it can do.
It generates static websites with the flexibility of a dynamic CMS, integrating features designed to combine performance, full control, and simple use.
Some exist elsewhere. Others are unique.
Here is what it can do.
Page performance
The table alongside this text shows the measurements page by page. Each result depends on the URL, date, device and test conditions.
Visual site editor
Responsive web design
Integrated SEO
Adjustable layout
Corrected HTML headings
Evolution
Genesis already lets me build the sites I want, with the level of control I need. But for me, it is only a starting point. I want it to become a truly assisted system, able to anticipate part of the work instead of only executing my choices. Connected to Homeostasis, Genesis should be able to generate pages from semantic models, propose structures adapted to the context, select the right media, then let me adjust the details. The goal is not to delegate the decision. It is to use machine intelligence to prepare the ground, without losing control of the result.
There are also very concrete points to improve. I want to see the impact of the styles I apply immediately: shadows, border radii, typographic variations, hover states, directly in the panels. I want expandable setting groups, a text editor that renders content live, and visual placeholders that make blocks easy to distinguish at a glance. A tool at this level must be powerful, but also pleasant to handle. No hacks. No guessing. A clear relationship between each setting and what appears on screen.
The preview needs to become more fluid, with several screen sizes available in one gesture, and blocks delivered by default with relevant icons or images, so the rendering stays clean even when the content is not final yet. Longer term, I want to add a house-made slideshow engine, very light and highly optimized, multiple headers and footers, dynamic menus, and an integrated generator for the legal notice, Terms of Use, and cookie banners. Everything that wastes time without adding creative value.
Genesis is designed as a living system. In time, I want it to become an autonomous ecosystem, able to recognize recurring needs, propose suitable configurations, and prepare the ideal structure before I even ask for it explicitly. Because at its core, Genesis is not only a tool. It is a way of working. Less friction, more control, and one constant obsession: that the technical layer gets out of the way, so all the space is left for what we truly want to show.
There are also very concrete points to improve. I want to see the impact of the styles I apply immediately: shadows, border radii, typographic variations, hover states, directly in the panels. I want expandable setting groups, a text editor that renders content live, and visual placeholders that make blocks easy to distinguish at a glance. A tool at this level must be powerful, but also pleasant to handle. No hacks. No guessing. A clear relationship between each setting and what appears on screen.
The preview needs to become more fluid, with several screen sizes available in one gesture, and blocks delivered by default with relevant icons or images, so the rendering stays clean even when the content is not final yet. Longer term, I want to add a house-made slideshow engine, very light and highly optimized, multiple headers and footers, dynamic menus, and an integrated generator for the legal notice, Terms of Use, and cookie banners. Everything that wastes time without adding creative value.
Genesis is designed as a living system. In time, I want it to become an autonomous ecosystem, able to recognize recurring needs, propose suitable configurations, and prepare the ideal structure before I even ask for it explicitly. Because at its core, Genesis is not only a tool. It is a way of working. Less friction, more control, and one constant obsession: that the technical layer gets out of the way, so all the space is left for what we truly want to show.
Owan
0/2000