Steven Broschart
DE·EN
Contact
Halite CMS

Static HTML CMS for sustainable websites.

Halite is my static HTML CMS for fast, secure and resource-efficient websites. Existing sites are migrated regardless of their original platform - whether WordPress, Typo3, Drupal, Joomla or a hand-maintained HTML setup.

Halite first mirrors the existing domain into a local staging environment. There, content can be analyzed, cleaned up and edited directly in the browser before the final version crystallizes into pure HTML on approval. Dynamic functions can be introduced selectively where they make sense - the bulk of the site sits as pre-rendered files that a web server delivers directly, without further processing.

Performance

Maximum performance.

Static delivery is technically the fastest possible approach on the web - with immediate benefits for SEO and user experience. Halite does not produce cached rendering, but real, final HTML on disk.

Pure HTML

No database query, no PHP execution, no cache layer and no cache-invalidation headaches.

TTFB under 50 ms

Time to First Byte typically below 50 ms - compared to 200 to 600 ms on classic dynamic CMS installations with database and template rendering.

Consistent delivery

No cold/warm-cache disparities - the first visitor does not pay the rendering cost for everyone else.

Core Web Vitals

Achieved without additional optimization - with direct impact on ranking and UX.

Even one extra second of load time can noticeably reduce conversion rates. Static HTML prevents this delay structurally, instead of merely papering over it with caching.

Security

Robust against attacks.

A look at typical server log files makes one thing clear: automated bots constantly scan for known vulnerabilities - XML-RPC endpoints, unpatched plugins, exposed admin paths or SQL injection vectors.

Especially in the WordPress ecosystem, most security issues do not originate in the core system but in plugins. Halite fundamentally reduces this attack surface:

No database in the hot path

No SQL injection vectors on the delivered page, no compromised database backups.

No PHP execution per request

Classic code-execution flaws in the PHP stack run into empty space.

No plugin chains

No cascading dependencies and no unpatched third-party components in live operation.

No dynamic page generation

What is not there cannot be exploited.

DoS attacks also lose much of their impact, because a request essentially amounts to a simple file fetch - no collapsing connection pools, no expensive render processes in the background. At a time of increasing attacks on publicly reachable infrastructure, this is less a comfort feature than basic operational hygiene.

Staging

Staging with data inventory.

Halite is not just a CMS but a complete staging system. Every migrated site is first analyzed, edited and approved in an isolated environment before content goes live.

At the center of this stands a systematic data inventory:

Orphaned images

Media files that are not used in the final site are automatically identified.

Duplicate pages

Duplicate or content-identical pages are surfaced and can be consolidated.

Same content under multiple URLs

Canonical conflicts and duplicate-content risks are resolved before go-live.

Outdated documents

Legacy material and documents that have lost their relevance are flagged for review.

This makes it possible to decide deliberately before publication what stays - and what can be removed. Many sites reduce their data volume significantly this way, without losing substance.

Operations

Lightweight in operation.

Halite works without a resource-hungry database infrastructure. Administration is based on an embedded SQLite file - no separate MySQL or PostgreSQL service, no connection pool and no complex backup regime.

As a result, the system runs on virtually any PHP-capable web hosting with its standard tools and uses significantly fewer resources in operation. This lowers both hosting costs and energy consumption.

Live editor

Targeted dynamics.

Content is edited directly in the browser inside the staging environment - click, type, save. Drafts and published versions remain cleanly separated.

The existing HTML documents can also be edited directly at any time - in the live editor or in the source. Halite works with plain HTML on disk, not with proprietary data structures. Content remains independently usable and is not tied to the system.

Where dynamic functionality genuinely makes sense - forms, search or individual interactive components - it can be added selectively, without having to deliver the entire site dynamically. The static architecture is preserved, while necessary interactivity is added precisely where it belongs.

Privacy

GDPR-compliant tracking without cookie banner.

Through the integration with Spectronq - also developed in-house - every Halite site comes with a full analytics engine without third parties, cookies or IP storage.

Sessions exist exclusively in the browser's sessionStorage and disappear automatically when the tab is closed. All data stays on your own server:

No third countries

No transfer of personal data to third countries or external providers.

No consent required

Since no processing of personal data in the sense of the GDPR takes place, no consent requirement applies.

No cookie banner

A smooth user experience without intrusive consent layers - and full legal clarity.

Detailed session journeys, goals, vanity URLs and optional AI-supported analyses are nevertheless available.

Migration & consulting

Considering a move to a static CMS?
Let's talk.