Skip to content
Sign in

What WBengine gives a site

A WBengine site keeps its pages, boxes, menu and articles in a database and serves them in several languages. Editors and AI assistants work through a keyed API, and the framework takes care of the cache, the statistics and the signals for search engines.

Pages and boxes live in the database

A page is a row, and the boxes it shows (a navigation, an article, a list, your own PHP class with a template) are rows too. You add a page, move a box to another section or hide a page without deploying code. A page can be strict and answer only its own address, or dynamic: the box behind it then receives the rest of the address as parameters and decides itself what is valid. See Boxes.

Languages are built in

Every page, menu entry and article can be translated. A language has its own address prefix (/cs/), the layout gets the links to the other languages, and the search engine signals follow: hreflang, a canonical link and a sitemap that lists each language of a page. See Languages.

It is managed from outside, safely

The API lets the central Admin and your own tools manage content with keys that carry only the permissions you chose, can be limited to certain addresses and leave a change log of who changed what. An article can be hidden and shown again. For an editor who is not technical there is an MCP server: an AI assistant plans the address and the search fields, checks that the page is complete and publishes only when asked. See REST API and Central administration.

Fast without extra work

Anonymous pages are served from a full page cache that keeps a copy per language and device, templates are compiled to PHP, and the framework has no runtime dependencies to load. See Caching.

Numbers without tracking people

The native statistics count page views, article views and box appearances per day and per language, and never identify a visitor. They are read through the API, in the Admin and in a ready report. See Logging and audit.

What it asks of you

PHP 8.3 or newer, MySQL or MariaDB, and a Composer install. The rest of this site is the documentation: start with Getting started.