SVELTIA / CMS

Website editing without the extra steps.

For an everyday text change, all you need is a browser and an account approved by your administrator.

Open the editor
  1. Open the editor

    Go to /admin. The site redirects you to the sign-in provider selected for this project: Google or Microsoft.

  2. Sign in with an approved account

    After verification, Sveltia opens with its collections ready. There is no GitHub repository to choose or access token to paste.

  3. Edit and save your content

    Choose a page or language, update its fields and press Save. A successful save means your change is stored in Git.

  4. Wait for the new version

    The server builds the site automatically. A successful build publishes the new output in one step. The previous version stays available while it runs.

For editors

Edit text and images in Sveltia. If someone else changed the same file, saving reports a conflict and keeps your draft available to resolve it.

For developers and administrators

Pushing to content triggers publishing. Pushing code to main waits for an explicit deployment through /ops. Only approved operators can deploy code.

Before you start

Do I need a GitHub account?

No. The server uses a GitHub App to access one preconfigured repository.

Are Google and Microsoft enabled together?

No. Each project selects one provider during setup. Only explicitly approved accounts can use the editor.

Is a change visible immediately after Save?

Save confirms storage. Publication follows a successful build. A failed build leaves the working website in place.

What happens if I edit again during a build?

The newer request stops the older build and its subprocesses. Only the current result may be published.