← DocumentationFirst steps
After signing in at /admin/, check general settings, the public URL, time zone, languages, and error display. A public website should not show PHP errors to visitors. Build the page tree next, then install only the modules the project actually needs.
Site structure
The Site Structure screen is a page tree. Each page has a parent, order, publication state, HTML template, and content for each language. Moving a page may change its URL when nested addresses are enabled. Check internal links and redirects after such changes.
Modules and templates
Enable features under Modules → Install Modules. Many module types support several instances, each with its own name, settings, content, and template. A file template controls presentation; an instance holds the actual content. Edit content in the instance instead of copying it into several templates.
Page templates live in the selected design directory. Module templates are isolated within the relevant module. Make a backup before editing template code.
Security and daily workflow
Give users only the permissions they need. Review the activity log and active sessions, and enable two-factor authentication for administrators. Before publishing, inspect every active language, headings, links, images, and the mobile layout. Create backups regularly and test that they can be restored.
Editing page labels
Below a page's main settings, the control panel lists the labels found in its selected HTML template and their bindings. Text has two modes. The visual editor is suited to formatted text, lists, links, and images. HTML code preserves the markup of a prepared design block, including containers and CSS classes, without visual-editor conversion. The server still checks the markup: structural elements such as section, article, header, footer, main, nav, and aside are allowed, while script elements, forms, and executable code are removed.
A context button next to a configured label opens the visual or HTML editor for text, or the exact module instance editor when a module is selected. It updates as the binding changes and is hidden for inherited or disabled labels. Templates and bindings are inherited from the parent page until the child sets its own values.
In multilingual forms, the active language tab is visually prominent. The fields below belong only to that language. Switching tabs does not save the form; press the main Save button after completing the languages.
Managing modules and templates
Modules are grouped by type. Each instance has a readable name, technical details, status, and editor; one type can have several configurations. Installing a module enables it in the CMS. Remove its instances before uninstalling it; module data can be kept or removed during uninstall. The Site Modules sidebar lists installed, enabled modules. A regular module without an instance links to instance creation; a singleton opens its shared settings.
The Templates section separates site design files from module files. Module templates are strictly grouped by type: a menu template will not appear in the gallery editor. Open files in the editor or create a new template in the appropriate module directory.
Roles, audit log, and settings
Roles have distinct permissions for overview, structure, modules, templates, settings, file manager, users, and the activity log. The administrator role has all permissions, and at least one active administrator must remain. For administrative POST actions, the audit log records the action, user, status, IP, User-Agent, request ID, and time. Mutating actions require authentication, the appropriate permission, and a CSRF token.
General settings include the site name, email, description, URL, time zone, interface language, error display, maintenance mode, design and content directories, 404 and maintenance pages, and MySQL parameters. A design can only be selected from design and textual content from content. The MySQL password is held separately in storage/private/secrets.json.
Each language has a code, name, status, URL prefix, and flag image. The default language has no prefix; others may use /en/ or /pl/. A Position field controls order in the language menu and editor tabs without changing codes or saved translations. Nested versus short URL mode and the .html suffix are site-wide SEO settings.
The file manager is confined to design, content, and uploads. It can create folders and text files, upload, edit, rename, and move items to the trash. System directories and server-side extensions are protected. The ? button opens help for the current screen; its text lives in admin/help/<language>. For portable archives, see the backup guide.