Most websites are far more complicated than the job requires. A small business site, a club website, or a personal project usually needs pages, images, navigation, maybe a contact form, and perhaps a few articles.
Yet we often build those sites with a database, a large theme, a collection of plugins, caching layers, and an administration system that has to work every single time somebody opens a page.
That is the problem Superlite CMS and Onlite.site are designed to solve. You use Superlite to create and manage the website, but publishing turns the content into ordinary static HTML pages. Onlite takes the same model one step further by removing the installation and hosting work, so you can start building without first setting up a server, installing a CMS, and configuring a hosting environment.
Three ways to use it
A small business needs a website
Most small businesses do not actually want a CMS. They want a website.
It needs to explain what the company does, show its services, provide contact information, and maybe include a contact form and a few articles. It should be easy to find through Google, and somebody at the company should be able to update a paragraph or add an image without calling an agency.
That is not a complicated set of requirements, but we often build a small business website as if it were enterprise software. It gets a database, a large theme, and a stack of plugins that all need updates and all need to keep working together. A few years later, nobody is quite sure which pieces are still necessary.
With Onlite, you can skip most of that. You create the site, write your pages, and publish them. If you later want your own domain, you can connect one without first learning how the web server or the CMS installation works.
Superlite also keeps the public website simple. Once a page has been published, the HTML already exists. The visitor does not have to wait for the CMS to start, query a database, and assemble the page again.
For a small business, the result matters more than the machinery behind it. The site is fast and there are fewer moving parts that can break.
You also do not have to install every possible feature from day one. Core SEO features are already there, while things such as contact forms, Google Analytics, and cookie consent can be added when you actually need them.
A personal project should stay simple
Another use case is the person who just wants to put something on the internet.
It could be a photography site, a local club, a band, a side project, a hobby, a collection of guides, or something completely different. You may have no interest in becoming a web developer, and you should not have to become one just to publish a few pages.
Today, getting started can require a surprising amount of work. First you choose a hosting company. Then maybe you buy a domain. Then you install a CMS, choose a theme, work out which extensions you need, and try to understand a long list of settings before the first real page even exists.
With Onlite, I want to reverse that order. Create the website first. Start writing. Upload an image. Publish.
Your site can start on an Onlite address. If the project turns into something you want to keep, you can add your own domain later.
That matters because it lowers the cost of simply trying something. You should not have to make decisions about hosting plans, server environments, and web technology before you even know whether the idea is worth pursuing.
Superlite is deliberately limited as well. The core does not try to contain every feature you might ever imagine needing. Extra functionality can be added as modules. For a personal project, that means a simple website has a chance to remain simple.
SEO specialists get more control
I belong to a third group with a different set of requirements.
For an SEO specialist, easy content editing is not enough. What happens technically when a page is delivered to a visitor or a search engine matters too.
When you publish a page, Superlite generates finished HTML. A normal page view therefore does not usually need a database query or a PHP process to build the content.
That does not mean every site automatically gets perfect Core Web Vitals. Images, CSS, fonts, and design still matter. The difference is that you are not starting with a large amount of CMS overhead that has to be optimized away.
Superlite also does not automatically add a pile of JavaScript and CSS to the public site. The theme decides which resources are needed. For an SEO specialist, that makes it easier to understand exactly what the page contains and what actually needs optimization.
SEO features sit close to the content itself. You can manage the page title, meta description, canonical URL, robots directives, Open Graph data, and the sitemap without installing a separate SEO package. There is also support for permanent redirects when URLs change.
We have also built tools for practical work on larger content sites. Image Optimizer can generate the image sizes a theme actually needs, while WordPress Importer can move content from an existing WordPress site.
If you work with a lot of content driven websites, that combination is interesting. The amount of content can grow without forcing the technical footprint to grow with it.
The CMS should not be able to take down the website
One of the most important ideas in Superlite is that the published website is separated from the administration system. You use the CMS to edit and publish content, but the finished page then exists as its own HTML file.
That means a problem in the administration area does not automatically have to affect the public site. If you cannot log in, or something in the CMS stops working, pages that have already been published can remain online and continue to be served normally.
I think that is an important principle. The more components that need to work every time somebody visits a page, the more opportunities there are for something to fail. If the visitor mainly needs to receive an existing HTML file, CSS, and images, the chain becomes much shorter.
You should only carry what you need
Superlite works without a SQL database and is designed for ordinary PHP hosting. Content, settings, media, themes, and modules are fundamentally stored as files, which also makes backup and recovery easier to understand.
Content is separated from presentation as well. You can change the theme without manually rebuilding the content, and images can be optimized for the sizes the active theme actually uses.
If you want full control, you can install Superlite on an ordinary hosting account. If you would rather avoid installation, server configuration, and technical operations, you can use Onlite.site.
If what you need is a website, you should not have to operate a small IT system just to keep it online.
Technical details for people who enjoy this stuff
- Static HTML on the public site
- Zero database queries for normal page views
- Zero PHP execution for normal page views
- No SQL database
- PHP 8.2 or newer
- No Node.js required on the production server
- No Composer required on the production server
- No SSH required
- Web based installation
- Block based editing with Editor.js
- Content and presentation stored separately
- Incremental builds
- Full rebuild available when needed
- Atomic publishing
- Existing public pages remain in place if rendering fails
- Public site operates independently from the CMS runtime
- The CMS core does not automatically add JavaScript or CSS to the public site
- The public site can operate without JavaScript
- Core SEO functionality
- Support for SEO title, meta description, canonical URL, robots directives, and Open Graph
- Automatic sitemap.xml
- Support for robots.txt
- Support for Schema.org
- Permanent redirects
- Permanent content IDs separate from URLs
- Modular architecture
- Hooks for extending the system without changing core files
- File based backups
- Export of the entire website or individual content
- Designed for ordinary shared PHP hosting
- Structured file based storage with JSON as master data
- Themes can be changed without rewriting content
- Normal publishing only rebuilds the parts of the site that have changed
- Generated HTML is not master data and can therefore be rebuilt
- Public templates decide which frontend resources they use
- Safer file writing through temporary files before existing files are replaced
- File locking to reduce problems during simultaneous writes
- Checks for unsafe file uploads
- PHP and other executable files are not accepted as media
- Image optimization and WebP support through a module
- Multiple theme specific image sizes
- Structured navigation
- Internal links can point to permanent content identities instead of relying only on the URL slug
- Separate module support for Articles
- Separate modules for contact forms, Google Analytics 4, Google Search Console, and Cookie Consent
- WordPress Importer for moving content from WordPress
- Markdown Import for fast content imports
- A small core with additional features added only when needed
