Resources

Preparing a static build for deploy

Most static-site generators write their output to a conventional folder — Empire Pages looks for dist/, build/, public/ or out/ automatically, falling back to the first folder it finds containing an index.html. Run your framework's normal build command (e.g. npm run build) before uploading a zip, or point Empire Pages at a repo whose build output is already committed.

Connecting an EmpireGit repo

Empire Pages only clones repositories under our own EmpireGit orgs (empire-apps, eas-oss, empire-games, iskra) — enter the path as org/repo in the dashboard's deploy form, along with the branch to deploy (defaults to main).

Related products

Empire Pages is part of the Empire dev-infra line, alongside EmpireGit (source hosting) and EliteSSO (the sign-in system every Empire product shares).