Landing sites
Landing sites
Landing sites are the public websites of your products: MaxSuite at maxsuite.si, and any other product on its own address. Each landing is its own code, built and deployed on its own. The words and pictures its code marks as editable are changed here. Changes stay a draft until you press Publish, and every publish is kept so an older version can be restored.
Only a platform admin can edit landing sites.
In the sidebar under Content → Landing sites. Needs: nothing else switched on.
Landing sites screen
The list shows every landing Max runs, with its name, main address, how many pages are live and how many have changes not yet published.
- New landing adds a landing for a product.
- Found in the dashboard's code lists landings whose code is already in the app but are not in the list yet. Add one in one go: its field list and first drafts from the sample its code ships come with it. Nothing is published.
- Shortcuts keeps landings Max does not run, such as another team's site or an old product page, as a name, a link and a note. Max does not read, serve or check these sites. Add shortcut, edit or remove one; only the record changes.
Open a landing to see four tabs.
Content
The landing's pages, each Live, Draft or Unpublished.
- Open a page. Its Words and pictures are the fields its code lets you change, each with its limit.
- Change the words, or add a picture (PNG, JPEG, WebP or GIF, up to 10 MB). Set the Menu title, Search title and Search description.
- Save. Nothing changes on the web.
- Use the preview to open the draft on the landing itself for ten minutes.
- Press Publish. A value that does not fit stops it, naming the field (Before this page can be published). Links to pages that are not live ask you to confirm (Publish with links that lead nowhere?).
Every published version of a page is listed with Restore, which copies it back into the draft. Unpublish makes the page answer "not found" until it is published again; the draft and every version stay. Values for fields the code no longer uses are kept under No longer used, never deleted, until you delete one for good.
Languages lets you offer the landing in Mandarin under /zh/ as well as English. A page not yet translated says Not translated yet. You can fill every empty translation from the translated sample its code ships in one go.
Contact form makes the form in Intake and connects the contact page to it, in one go.
Overview
About this landing: its name, status (Setup, Live or Paused), featured modules, the docs link, and where its code lives. Field list shows which list of editable fields is in use and where it came from, with Refresh to read it again from the landing. Deploys shows the app's latest deploys.
Addresses
A landing's addresses: a root domain, a subdomain or a separate domain. The first is the main one; the others redirect to it.
- Add an address. This changes nothing in DNS yet.
- The screen shows whether DNS points at the app's server and whether the app has the name, with the exact record each step needs.
- For a domain managed here, connect it: the record is published and the address is added to the app, which restarts to get a certificate. For a domain elsewhere, add the record yourself, then add it to the app once DNS answers.
- Refresh address asks public DNS and the app again: Connected, Points elsewhere or Not set up.
Settings
Where the landing runs (its Coolify application), its Keys, and Edit pages in. Deleting a landing deletes its pages, every version and its pictures, and cannot be undone.
Who can do what
| Permission | Label | Lets you |
|---|---|---|
landing:read | View landing sites, their pages and drafts | Open Landing sites and read every landing, page and draft. |
landing:write | Edit, publish and restore landing sites, and push their field lists | Edit drafts, publish, restore, manage addresses, languages and shortcuts. On top of this, editing needs a platform admin. |
See People, roles and permissions.
What happens on its own
| Job | When | What it does |
|---|---|---|
deploys | Every 5 minutes | When a landing's app has just finished deploying, reads its field list again. |
nightly | Every night at 03:40 | Reads every landing's field list again, and checks every address again. |
Live addresses of landings also show in Monitoring's list of things not yet watched.
What agents can do
An agent can read landings, fill and change drafts, and manage addresses. Pointing DNS at the app and adding an address to the app change live servers, so they need approval. See Agents and approvals.
Read only: landing.list, landing.found, landing.get, landing.fields, landing.pages, landing.page, landing.addresses, landing.checkAddress, landing.shortcuts
Set up a landing: landing.create, landing.addFromCode, landing.syncFields, landing.draftFromSample, landing.setLanguages, landing.languageFromSample
Edit and publish pages: landing.updatePage, landing.publish, landing.restore
Addresses: landing.addAddress; landing.connectAddress and landing.addToApp (need approval)
Shortcuts: landing.addShortcut, landing.updateShortcut, landing.removeShortcut
Over MCP the same tools are named landing__list, landing__publish and so on. See API keys and MCP access.