AI and MCP Page Reordering — Move, Sort, and Reorder Site Structure
Quasar can reorder pages in the editor. POST /api/v1/sites/{siteId}/reorder and aveiro_reorder_pages let agents and CI scripts reorganize folders without opening the dashboard.
Translation Jobs: Live Progress, Cost Estimates, and Cleaner Pickers
In short
Ask Quasar to reorder a collection, move a page between folders, or switch sort mode. The same operations are available over REST and MCP for docs sync and agent workflows.
What we shipped
Content automation could already create and update draft pages. Reorganizing the file tree — nav order, moving pages between collections, sort modes — still meant opening the Pages panel or dragging rows by hand.This release closes that gap in three places:
Quasar in the editor
Quasar now has tools to reorder pages inside a folder, move a page into another collection, and set a folder's sort mode (manual, alphabetical, recent, published). Ask in plain language:
"Put /guides/quickstart.mdx first in the Guides collection."
"Move /draft.mdx into /blog at the top."
"Sort /updates by most recently published."
Changes apply through the same review flow as other AI edits.
REST API
POST /api/v1/sites/{siteId}/reorder accepts three operations:
reorder — pass a folder path and the complete ordered list of page paths inside it
move — move one page into a folder, optionally at a 0-based position
sort — set manual, name-asc, name-desc, recent, or published on a folder (or site root)
Requires content:write — the same default scope as create and update.
MCP tool
, , and wrap the same route — one MCP tool per . Pair them with when an agent needs to discover paths before reorganizing.
aveiro_reorder_pages
aveiro_move_page
aveiro_set_folder_sort
operation
aveiro_list_pages
Editor drag-and-drop polish
The Pages tree drag-and-drop got easier to use for manual reordering and nesting — wider drop targets and clearer insertion lines when you prefer the mouse over chat.
Why we built it this way
Docs sites, help centers, and blogs all depend on tree order for sidebar nav and collection cards. CI pipelines that sync MDX from git often create pages in arbitrary order; agents drafting new sections need a way to slot them without a human rearranging the tree afterward.
One endpoint with three operations keeps the mental model small: reorder siblings, move across folders, or change how a folder sorts itself.
Try it
In the editor: open Quasar and ask to reorder a collection you are working on.
Over REST:
GET /api/v1/sites/{siteId}/pages — list paths
POST /api/v1/sites/{siteId}/reorder with operation: "reorder" and the full order array
In Cursor: call the matching tool (aveiro_reorder_pages, aveiro_move_page, or aveiro_set_folder_sort) with the fields for that operation.
