What it includes
The February 2026 changelog has the full details.
A Studio project type
Studio has a collection browser, a schema-driven entry editor, a code editor, a visual editor with live preview and a media browser.
AI content assistant
The built-in assistant can create and edit content entries, write to files, manage media and insert edge function islands. The conversation stays open as you move between Studio pages.
Branch-based review
Editors make changes on a branch and submit them for review. Approving a pull request merges it into the main branch and starts a deployment.
AI migration from a website
When you create a Studio project, choose Import from Website and enter a URL. An AI agent analyses the site and classifies its content types. After you approve the results, the tool crawls the site. AI agents then generate an Astro template based on the original design and map the content into structured collections.
Schemas and languages
The schema manager lets you view, create, edit and delete collection fields from the dashboard without editing code. In Studio settings, you can also turn on multi-locale content. The entry and visual editors then have a locale switcher.
Deployments and Quant Builder
The Deployments page lists the GitHub Actions workflow runs for the current branch. It has a log viewer for each job, a Deploy button, and re-run and cancel controls. Quant Builder mode publishes from the browser instead.
Who it is for
Content editors
Edit entries in a form or in the visual editor with live preview, then submit your branch to the team for review.
Site developers
Keep your Astro site in GitHub, and edit code, schemas and edge functions in the browser when you need to.
Agencies moving sites
Convert a client's existing website into a Studio project with the AI migration tool, then let editors work in it.
What it is
Quant Studio is a browser-based content management interface for Astro static sites, and a new project type in the Quant dashboard. Your content is stored in your GitHub repository, and you publish your changes to the CDN without leaving the dashboard.
Editors use forms, a visual editor and an AI assistant. Developers keep the Astro code in GitHub and can also edit it in the browser.
To try Studio without GitHub, open the sandbox at https://dashboard.quantcdn.io/studio/demo. It does not keep your changes after your browser session ends.
How it works
A content change moves from an editor to the live site in these steps:
- An editor creates a branch and opens an entry. The form comes from the collection’s schema, and the visual editor shows a live preview.
- The editor can ask the AI assistant to create or change entries.
- The editor submits the branch for review. Reviewers see a diff preview in the review queue and comment on individual diff lines.
- A reviewer approves the pull request. Studio merges it into the main branch and starts a deployment.
- The Deployments page lists the GitHub Actions workflow runs for the current branch, with a log viewer for each job.
Quant Builder mode builds and publishes pages in the browser, without a GitHub Actions workflow. Turn it on in Studio settings. Save & Publish then pushes the page you are editing to the CDN immediately. Build & Publish on the Deployments page rebuilds and publishes the full site.
Studio also has pages for edge functions, site search and forms. On the Functions page, saving a function deploys it. A <quant-island> tag in an entry shows the HTML that an edge function returns.
Get started
Try the demo
Open the Studio demo. It needs no GitHub connection.
Create a Studio project
Import a GitHub repository, or choose Import from Website to convert a site.
Edit on a branch
Create a branch, then change entries in the entry editor or visual editor.
Submit for review
Submit your branch. Reviewers comment on diff lines in the review queue.
Approve to publish
Approving a pull request merges it and starts a deployment of the site.
Related: Explore Quant Studio · Documentation · February 2026 changelog
Ready to try it on Quant?
Use Quant Studio on your own project, or talk to our team first.