A CMS built for maximum control
AICMS gives designers and developers an editable, multilingual website without surrendering the frontend architecture, source code or publishing process.
Designed around the project — not a theme
AICMS is for teams that want a precisely designed website and a clear editing experience. The developer decides what is structural, the designer keeps control of the interface, and editors receive only the fields and modules they actually need.
It is a compact, project-specific CMS: PHP and Smarty on the public side, deliberate content models in the panel, and no theme builder standing between the design and the code.
Your frontend stays yours
Edit Smarty/HTML templates, CSS and JavaScript with lightweight syntax highlighting. The CMS exposes content without replacing the project’s own component structure or visual system.
Modules match the real design
Define single or repeatable modules, typed fields and personal, shared or inherited scope. Pages can use content sections, cards, pricing plans, galleries and project-specific structures.
Publishing stays deliberate
Work with drafts, preview and saved versions. The assistant prepares proposals rather than publishing on its own, so a person reviews the result before it reaches the live site.
How AICMS works
The workflow separates implementation decisions from everyday content work while keeping both in one understandable system.
- Model the pageThe developer creates or selects a Smarty template and defines the editable modules.
- Build the interfaceThe designer and developer keep full control of markup, CSS, JavaScript and responsive behavior.
- Fill the contentAn editor adds text, media, SEO data, translations and repeatable items without touching source files.
- Review and publishThe team previews the draft, checks changes and publishes only the approved version.
What you can manage
The panel is intentionally broad enough for real projects, but organized around focused tools rather than one overloaded page builder.
Pages and content
- Create, edit, order and hide pages
- Manage independent EN, PL, NO and LT versions
- Edit titles, slugs, excerpts, SEO metadata and notes
- Use draft, preview, publish and version history
Design and structure
- Edit Smarty/HTML templates, CSS and JavaScript
- Define modules, typed fields and repeaters
- Use personal, global and inherited content
- Control navigation and reusable page segments
Media and operations
- Upload images and PDFs with localized alt text
- Generate responsive WebP image variants
- Manage forms, messages and recipients
- Review audit history and scheduled cleanup
Clear roles for different responsibilities
Access is separated by capability, so daily editing does not require access to code or system configuration.
Superadmin
Full control of users, templates, CSS/JS assets, modules, media profiles, form definitions and all publishing tools.
Admin and editor
Manage pages, translations, media and incoming messages; use the assistant, review drafts and publish content.
Viewer
Read-only access to the panel and audit information — useful for oversight without editing rights.
Command Assistant and optional Advanced AI
Choose the page, language, area, action and block, then describe the change in natural language. The built-in assistant produces a structured proposal; optional Advanced AI can expand the interpretation when a provider is configured. If it is unavailable, the local assistant remains the safe fallback.
Form generator with practical protection
Create project-specific forms and fields, set a recipient address per form and handle submissions like the built-in contact and booking forms. Honeypot protection and a random addition challenge with a result no greater than 10 are available without an external CAPTCHA service.
Media prepared for the frontend
The media library stores localized alt text and creates purpose-specific WebP variants for hero, card, mobile, thumbnail and preview use. Media stays related to the pages that use it, while retention rules and cleanup tasks keep operational data under control.
One concrete example
Suppose a studio is launching a new service page. A developer selects the page template and adds a repeatable “service cards” module. The designer finishes the responsive layout. The editor then creates the EN and PL content, selects prepared images, writes metadata and asks the assistant for a shorter lead.
Result: the page remains a hand-crafted frontend, but future updates happen through clear fields, reusable segments and an approval-based publishing flow.
Who AICMS is for
A strong fit
- Designers protecting a distinctive visual system
- Developers who want readable files and explicit data models
- Studios building tailored sites for long-term clients
- Teams that need languages, roles and controlled publishing
Especially useful when
- A generic theme would constrain the design
- Editors should not touch layout code
- Reusable content needs project-specific fields
- AI should assist without taking over publication
Probably not for
- One-click theme marketplaces
- Unrestricted drag-and-drop page composition
- Projects that value plugin quantity over a focused codebase
- Teams that do not need implementation control
See the system from the inside
Open the demonstration panel to inspect the page editor, modules, media library, form generator, roles and assistant. The public demo protects system-critical actions, but shows how the complete workflow is organized.