This site on Everlock

This public website is itself hosted by an Everlock instance.

That matters because the site is not only talking about Everlock. It is also one example of what Everlock is currently able to do.

What that means in practice

the content lives in a normal git-backed site repository
Everlock serves that repository through backend-site-http
the public pages, search index, feed, and generated routes come from the site backend itself
local assets and templates are part of the same repository instead of being deployed through a separate pipeline

Why the project does this

Hosting the public site on Everlock makes the project easier to evaluate.

it keeps the documentation close to the product behavior
it gives contributors a concrete repository layout to inspect
it demonstrates the Markdown site backend on a real public-facing site
it keeps the project site legible as infrastructure, not just as a brochure

The important distinction

There are two separate layers involved:

Everlock system configuration:
- which site exists
- which vhost serves it
- whether it is public or authenticated
site repository content:
- Markdown pages
- templates
- assets
- navigation
- taxonomies

So when we say “this site is hosted on Everlock”, we mean:

Everlock owns the serving and routing
the site content is stored and published as a repository
the site backend renders the public output directly from that content

What it does not mean

It does not mean this site is a separate static export uploaded somewhere else after a build step.

It also does not mean the public website is a special-case demo outside the product. The intent is the opposite: keep the project site close enough to the real backend behavior that it remains useful as a reference.

If you want the mechanics

Getting started for the first-run path
Configuration reference for the broader configuration model
Docs for backend and frontend explanations