How-to guides
Task-oriented guides for a specific result: a feature, an integration, an operation on a live site.
With AI
Get results from the built-in assistant and connected agents: prompting, skills, MCP, content generation.
Connect an agent over MCPGive your own AI agent access to a Quilium site, with your account, your permissions, and no token to copy around. Prompting well for QuiliumGive an AI agent what it needs to build a Quilium site correctly, and phrase the request so it does not have to guess. What you can ask an agentShort jobs that take one prompt and no guide, with what to check afterwards. Use the integrated AI agentWork with the assistant that ships inside the CMS, know what it can do, which model tiers you have, and how credits are counted.
Build something complete
Assemble a whole feature end to end: a blog, an events agenda, a contact form, a multilingual site.
Build a blogModel articles as a collection, list them, give each one its own URL, let visitors filter and search, and know what goes live the moment you save. Build an agendaStore dated events in a collection and split them into upcoming and past, in chronological order, without writing a line of date logic in the template. A rich, flexible article bodyLet editors build a rich body out of typed blocks, paragraph, quote, image, text-with-image, using a single choice field. Build a complete contact formBuild a form that validates server-side, saves each submission into a collection, redirects to a thank-you page, and, when you need them, accepts a file, a captcha and an email notification. Let AI generate your contentGive an agent one page that shows every block your site already has, and it composes new pages out of them instead of inventing a structure. Let AI write the HTMLA block whose HTML an agent writes lifts the ceiling that content-types impose — and hands the maintenance of that page to whoever can read markup. Powerful, and not for every team.
Master one aspect
Go deep on one part of the platform: templates, partials, media, navigation, SEO.
Build a template (Liquid)Write the Liquid files that turn a page-type and its content blocks into rendered HTML, from the root layout down to a single element. Reuse blocks (partials)Factor repeated markup into partials, pass parameters explicitly, and dispatch a page's content blocks with a single include. Run a multilingual siteDeclare locales, translate content and interface strings, and make every link in your templates land on the right language. Manage media and imagesUpload once, let Quilium produce the sizes, render them with the right dimensions and a real alt text. Handle SEO and metasGive every page a real title and description, keep the pages that should stay out of the index out of it, and get detail pages right. Build navigation and menusRender menus from the site tree instead of hardcoding them, nest pages, hide what should not appear, and reorder without touching Liquid. Manage site-wide contentPut the address, the social links and the footer text in one editable place, and read them from any template. Consume an external feedRead a remote JSON endpoint at render time with an `api` field, key it on the item the page is showing, and handle the day it stops answering — which is the part that actually needs designing. Set up redirectionsKeep old URLs alive after a rename or a migration, without losing what search engines already know.
Operate
Run a Quilium site day to day: publish, redirect, troubleshoot, connect an external feed.
Publish and go liveGet templates and content from your machine to a live domain, and know which action moves what. Drive the site with MCP toolsRun real operations through the MCP server, in the right order, with the right wrappers, without turning fifty items into fifty round-trips. TroubleshootingThe failures that waste an afternoon, what actually causes them, and the check that tells them apart.