Install
Updating the admin
WordPress has built-in core/plugin/theme updates. Flexweg CMS doesn't — you build the new admin yourself (or download a release), upload the new to Flexweg, and the new code is live.
Plan limits and monitoring
Both Flexweg and Firebase have plan limits. Stay under them or pay; either way, monitor them so you don't get surprised mid-publish.
Renaming the admin folder
By default the admin SPA is deployed to on Flexweg. You can rename that folder to anything you want — for example a random-looking string like — to make it harder for crawlers and casual scanners to
Installation overview
There are two paths to a working Flexweg CMS, depending on whether you're a developer who wants to build the admin yourself, or a user who's been given a pre-built to drop on Flexweg.
Firebase project setup
Flexweg CMS uses Firebase for two things:
Deploying to Flexweg
Once you have a folder (either built locally with or downloaded from a release), deploying to Flexweg means uploading two folders to two specific locations on your Flexweg site.
Firestore security rules
Firestore rules are the only thing protecting your CMS data. Without them, anyone on the internet could read and modify your posts, settings, even create user records and grant themselves admin. The
Local development
This page is for developers who want to run the admin locally with hot module reload, write plugins or themes against live admin code, or contribute to the CMS itself.
Flexweg account setup
Flexweg is the static hosting service that holds both your public site (visitors browse this) and your admin SPA (you log in here). The CMS interacts with Flexweg through its Files API — every
First-run setup form
When you visit for the first time after uploading , the admin detects there's no Firebase configuration baked in (because ships as a null stub for the no-build path) and renders an in-admin setup
Troubleshooting
The most common problems and how to fix them. Skim the section that matches your symptom.