Your first site
From an empty install to a site handed over to its owner. The commands run from the site's document root, web/, as the site's user.
1. Install without demo content
Install as in Installation and skip setup demo: a client's site starts empty. It already has a home page, sign-in, registration, password recovery and the admin.
2. Make pages from templates
Sign in at /login/ and open «Управление структурой» (Structure management) at /admin/structure/.
- The home page: select it, press «Редактировать» (Edit) and choose «Лендинг» (Landing) in «Содержимое страницы» (Page content). Its sections: first screen, services, reviews, call to action and contacts.
- A service: press «Добавить» (Add) under the home page and choose «Услуга» (Service): first screen, the page's own text, prices, questions and answers, call to action.
- Contacts: add a page with «Контакты» (Contacts): the page's text and a contacts section.
- Other pages can be «Текстовая страница» (Text page), «Список подразделов» (Subsection list) or «Карта сайта» (Site map).
A template of your own is one command:
php index.php setup page --name=about --title="О компании" --sections=hero,services,reviews,cta
It writes site/modules/main/templates/content/about.content.xml and the template's name for the list (--title in Russian, --title-ua in Ukrainian), loads the name into the database and runs setup linker, so the template appears in «Содержимое страницы» at once. See Page templates and sections.
3. Write the section texts
The owner turns on «Режим редактирования» (Edit mode) on the admin toolbar and writes on the page itself. An empty section is not shown on the site; in edit mode it shows a sample text to replace. A picture goes in with the editor's image button; a picture in the first screen becomes its background.
There are no contact forms and no attachments: contacts are links, and a gallery is pictures in the text.
4. Show the owner what they have
- Broken links. «Битые ссылки» (Broken links) at
/admin/links/lists links to missing or switched-off pages and to missing files;php index.php setup checklinksdoes the same in the console and exits with code 1 if it finds any. On the site a broken link shows as plain text, and an administrator sees it marked. - Help. The ? in the top right corner of an admin window explains that screen.
- Text history. In edit mode «История» (History) shows the last 20 versions of a text in this language and brings one back.
- A language in preparation. In the language editor, untick «Открыт посетителям» (Open to visitors): visitors get 404 for that language until it is ready. The default language can't be closed.
- The owner's manual.
php index.php setup manual --out=/home/me/manual.mdwrites a short guide for the owner with the site's addresses filled in; hand it over with the access. Keep the file out ofweb/.
5. Your colours and font
Colours, the font, the corner radius and the page width are variables in one file, site/modules/main/stylesheets/theme.css: the light scheme on :root, the dark one under @media (prefers-color-scheme: dark). Change the values and keep the names. Then rebuild the stylesheet:
bash ../private/energine/tools/get-tailwind.sh # once per machine: downloads the Tailwind CSS binary
php index.php setup css
Keep the contrast of text and buttons at 4.5:1 or more in both schemes. See Theme.
6. Check
php index.php setup check
It prints OK, WARN and FAIL lines, exits with code 1 if anything failed and changes nothing.
- FAIL: debug mode on, no site address, a static
web/robots.txt, demo users, a switched-on page without a name in an open language, broken links, untranslated interface strings, no GD. - WARN: a language in preparation, a page without text, NOINDEX on an ordinary page, no SMTP server, the template's sender address left as it is.
The repository's browser audits check contrast in both schemes, widths from 320 px and pages without JavaScript errors; they need Node, Playwright and Chrome — see tests/README.md in the repository.
7. Move to hosting
Your theme, templates and interface strings are in the repository's site/, and the built stylesheet is in git as well: the hosting needs neither Tailwind nor Node, but it needs your copy of the repository, not a fresh clone of Energine Simple.
- Put your copy into
private/energineon the hosting: commit your changes and clone your own repository, or copy the folder withoutconfigs/system.config.*.php,tests/local.phpandtools/tailwindcss. - Follow Installation from step 2 into an empty database: the installer writes the hosting's configuration and an administrator.
- Load a dump of your working database over it — the tables are the same; the administrators and passwords now come from your working copy. The site's address lives only in the configuration, never in the database.
- Copy
web/uploads/; its files must belong to the site's user. - Run
php index.php setup linker.