Files show who owns the data
Section content stays with its section. Shared DATA is reserved for values that are truly shared.
A micro framework for developers who like control
Build multilingual pages the way you think: component, data, template.
BlendHTML keeps the stack small and visible: Twig templates, recursively merged JSON data, locales and reusable sections without a heavy framework layer.
- Structure
- File-based
- Locales
- et · en · ru
- Focus
- Fast HTML
Real value
A small framework that does not hide your code from you.
BlendHTML fits landing pages, documentation, campaign sites and simple web projects where speed and clear ownership matter more than a stack of abstractions.
Localization is part of the workflow
Each component has base data and locale files that the framework merges for the active language.
HTML reaches the browser fast
Twig rendering, Tailwind utilities and a small set of vendor assets produce pages without heavy client-side dependency.
Reuse remains straightforward
Adding a component is a readable template call, not a new architectural decision.
Workflow
Write less glue. See more of the project.
The BlendHTML workflow is deliberately direct: the page composes sections, the section renders a template and the data comes from the place that owns it.
01
Compose the page from sections
The index file stays a page map. It shows which blocks make up the experience.
02
Keep text in locale files
Languages are not an afterthought. Every supported language gets its own natural content.
03
Use vendor assets only when useful
Reveal, parallax and smooth scroll are added explicitly and only when they support the experience.
The result is a file tree developers already understand.
There is no guessing where a headline or CTA comes from. Open the section and its template and data are right there.
Try the framework
Open the demo, inspect the structure and build your first page the same day.
The value of BlendHTML is easiest to see in real pages: multilingual content, a clear component tree and a surface area small enough to understand quickly.
See how the page is assembled
The demo shows how sections, data and vendor components work together.
Bring the patterns into your project
The structure fits documentation, agency pages and AI-assisted campaign sites.
Publish without a heavy layer
The result is server-rendered HTML with only the helper assets you choose.