A mini-site built for the mobile screen
Add content, buttons, images, forms and contacts in a visual editor. Set the theme, the short address and publishing without coding a page yourself.
- 9 languages for translation
- Publish at /p/slug or on your own domain
- SEO and PWA settings in the model
Add block
- Link button
- Messengers
- Photos and gallery
- Text
- Menu and prices
- Contacts and map
Loft Studio
Photo and video studio in the city centre
Features
Editing, publishing and growing a single page
A mini-site keeps its blocks, theme, SEO fields and publishing settings as one object.
Mobile preview
Check the order of the blocks and their content in the editor canvas before you publish the page.
Page theme
Keep the visual settings apart from the content and refresh the design without rebuilding the blocks.
SEO fields
A mini-site has its own SEO configuration; fill it with a real title and description before publishing.
Forms
Accept form data through the public endpoint of the mini-site and record the submission as an event.
Language versions
Enable a set of locales and run the translation of the content through the built-in process.
Versions
Save and review the versions of a mini-site, and restore a selected one when you need to.
Address and domain
Use the page slug or a verified custom domain within your plan.
Details
What a mini-site stores and publishes
A mini-site is a structured set of blocks with a theme, SEO settings, an address and a publishing state. That is what makes the page editable through the interface instead of the source HTML.
Blocks instead of a rigid template
Every block has a type, a configuration and a visibility flag. The editor arranges them into a sequence you can change without rewriting the whole page. That makes a mini-site convenient for frequently updated information and short mobile flows.
Not every block type is meant for every mode. Restaurant and specialized modules may be available only in the matching section, so this page does not promise an identical catalog across all plans and editors.
Publishing, versions and languages
A page can stay a draft, be published or be moved to the archive. The backend also keeps a list of versions and can restore a selected state, which helps separate work in progress from the public version.
For several languages, the set of locales and the translation result are stored. Automatic translation always needs proofreading: names, prices, contacts and legal text cannot be treated as confirmed just because the service generated them.
SEO and a custom address
A mini-site has SEO fields, but having them does not optimize the page by itself. You still need a unique title, a description, real content and a public URL you can verify.
Custom-domain availability comes from the current pricing catalog. A domain goes through separate verification.
What a mini-site can do
- Publish at /p/slug or on your own domain
- 9 languages for translation
- Block and theme editor
- Draft, published and archived states
- SEO and PWA settings in the model
- Forms and submission events
- Versions and language settings
- Forms and leads without built-in CRM automation
Workflow
From draft to published page
First assemble the content and check the mobile composition, then set the address, and only after that publish.
- 1
Create the page
Set a name and a slug, choose a starting structure or begin with an empty set of blocks.
- 2
Assemble the blocks
Add content, change the order and configure every block in the editor.
- 3
Set the theme and SEO
Check the colors, the typography, the title, the description and the page settings before it goes public.
- 4
Publish and measure
Move the page from draft to published and watch the events within your plan.
Scenarios
One mobile page for one specific job
A mini-site helps when a full multi-page project is overkill but a single external link is no longer enough.
Comparison
A single link or a mini-site
Choose a plain link if all you need is a redirect. A mini-site is for your own content and several actions.
| Parameter | Short link | Mini-site |
|---|---|---|
| Your own content | ||
| Several buttons and blocks | ||
| Form on the page | ||
| Theme and visual composition | ||
| Fast change of destination | Through the page content | |
| Best fit | Redirect | Mobile landing page |
- Your own content
- Short link
- Mini-site
- Several buttons and blocks
- Short link
- Mini-site
- Form on the page
- Short link
- Mini-site
- Theme and visual composition
- Short link
- Mini-site
- Fast change of destination
- Short link
- Mini-site
- Through the page content
- Best fit
- Short link
- Redirect
- Mini-site
- Mobile landing page
FAQ
Frequently asked questions
Can a page be published later?
Yes. A mini-site has draft, published and archived states. You can save the structure and the theme before publishing and then change the state in the dashboard.
How do forms on a mini-site work?
The public page sends the form data into the mini-site, and the submission is recorded as an event. There are no ready-made connectors for CRM, Telegram or spreadsheets in the current version.
Are several languages and PWA settings supported?
A mini-site supports language versions, translation, PWA settings, a theme and SEO fields. Before you launch each locale, check the translation, the links and the page metadata.