Content Studio — your website, inside your business system

Publish your website from the same system that runs your business: markdown pages, SEO metadata, sitemap, robots.txt and llms.txt generated on every request.

A luminous sheet dissolving into scattered nodes

Your website is where customers meet your business. It is strange that it usually lives in a completely different system from the business itself.

Content Studio is a headless CMS inside AxisIQ: you write pages here, and they are served publicly — with the search-engine and AI-crawler plumbing generated for you rather than configured by you.

The page you are reading right now is published from it.

Writing

A clean, Medium-style editor: select text and a formatting bar appears; press the + in the margin to insert a heading, list, quote, code block, divider or image; drag an image straight in from your desktop. There is no HTML to learn and no theme to fight.

Underneath, everything is stored as Markdown — which means your content stays portable, diff-able and readable by machines, and never becomes a pile of nested <div>s that only one editor can open.

If you would rather write raw Markdown, one toggle switches the same document to a source view. If you want a first draft, the AI drafting panel writes one from a prompt and you edit it down.

Publishing

Content has two states: what you are working on, and what the world sees. Publishing takes a frozen snapshot — so you can edit a live page all week without a single half-finished sentence leaking. The document list marks anything that has been edited since it was last published, so nothing sits forgotten.

Publishing can also wait for a time you choose: schedule a page to go live at midnight for a sale, or to come off the site when the offer ends. It goes live with whatever the page says at that moment, published as the person who scheduled it.

A page's path is its URL and its folder structure at once. Publish at guides/getting-started and it is live at that address, in the Guides section, in the navigation, and in the sitemap. There is nothing else to configure.

Found by search engines and by AI

This is the part most CMSs leave to a plugin. AxisIQ generates all of it on every request from whatever is currently published, so a publish is live immediately and nothing needs rebuilding:

  • sitemap.xml — every published, indexable page with its last-modified date.
  • robots.txt — pointing crawlers at that sitemap.
  • llms.txt — the emerging standard for telling AI models what a site contains: your pages, grouped by section, each with a description.
  • llms-full.txt — the entire site as one clean Markdown document, so a model can read your whole story in one fetch.

Every page is also available as plain server-rendered HTML, with the meta description, Open Graph tags and structured data filled in. That matters more than it sounds: most AI crawlers and every link-preview bot run no JavaScript at all, so a client-rendered site is invisible to them. Your site can serve that version to those readers and keep its own design for everyone else. This site does exactly that.

Each page carries its own SEO block — meta title and description, keywords, canonical URL, social preview image, and a noindex switch for anything you want live but unlisted.

Works with any front end

Content Studio is headless: it holds and serves your content, and your site decides how it looks. Your site reads published pages from a small public API, and it works the same way from any stack:

  • Server-rendered frameworks such as Next.js, Nuxt, SvelteKit, Astro and Remix fetch a page on each request, so a publish is live within a minute and needs no deploy.
  • Static site generators such as Astro, Eleventy and Hugo fetch at build time.
  • WordPress, PHP, Django, Rails or any other backend fetches over plain HTTPS. Each page arrives as markdown and as ready, sanitized HTML, so no markdown library is needed.
  • Plain HTML pages and single-page apps fetch from the browser on any domain.
  • Mobile apps read the same endpoints and render the markdown natively.

Images come back as absolute URLs, so they load wherever the page is shown.

Getting started

  1. Open Content Studio and create a content space for your site, with its address as the Site URL.
  2. Write a page, choose its path (that is its URL), and publish it.
  3. In Team & Permissions → Roles, create a role from the Public visitors template so that published pages are readable by anyone.
  4. Point your site at the delivery URLs listed in the space's settings, and forward sitemap.xml, robots.txt and llms.txt from your domain.

Publishing a website from Content Studio walks through it step by step. Connecting Content Studio to your website or app has copy-paste code for each stack, and the delivery API reference lists every field.

Images

Images upload from the editor into a dedicated space and are served publicly with proper caching. You do not need a separate media host or a CDN account to put a photo on a page.

Who it is for

If you run a marketing site, a documentation set, a product catalogue's supporting pages or a company blog, this replaces a separate CMS subscription and the integration work that comes with it — while keeping publishing inside the same permission model as the rest of your business. Only the people you allow can write, and only the people you allow can publish.

See how permissions are scoped per content space, how to connect your site, or read about the platform as a whole.