Page presentation is formed from the content Concept via semantic components

The structure of a public page does not have to be hardcoded into the database schema with dozens of separate presentation fields.

A practical approach, already proven in other projects: the main content and page composition are stored in a single content field, and special allowed tags control UI components — hero sections, facts, sections, cards, sidebars, and other blocks.

Why this is needed

• AI can manage not only text, but also page composition;
• a new content type does not immediately require expanding the table with dozens of fields;
• the entire document is easier to translate and adapt as a whole;
• page structure can evolve alongside the content;
• data is structured in the DB only when genuinely required for behavior, querying, permissions, or relations.

At the same time, the type field remains a lightweight mechanism for grouping Concepts. For example, project:default denotes a project Concept and allows fan-out queries like project:% without creating a separate Project entity just for public content.

This approach is part of the fi1osof.ru architecture and relies on the principle of Concept as the primary addressable unit of knowledge.