About the app

The layout

Once a list is open, the app is one screen wherever you opened it from, headed Organize Child Pages with the space’s name beside it. It has three parts, left to right:

• The page tree — the whole space, pages and folders only, with the space’s name at the top. Click any item to show its child pages in the list. While you drag, it is also somewhere to drop pages.
• The list — the child pages of one parent, in the order Confluence’s page tree shows them. Above it, a breadcrumb says where you are and a hint line says what you can do. Its header holds a checkbox that selects every page, the page count and Sort all; once you tick pages, Move to… and a × that clears the selection appear beside it.
• The Unsaved changes panel — there only when it has something to say: the changes waiting to be saved, what the app is busy with (a save in progress, or a short check such as Reading dates…), or a message headed Saved, Not saved or Note. The rest of the time the list takes the full width.

Hide page tree sits at the top right. In the ••• dialog a Close button sits beside it; on the Apps page, ← Choose another space sits above the title.

In a narrower window the Unsaved changes panel moves above the list, and narrower still the page tree moves above both.

The words this guide uses

Hide page tree

Hide page tree at the top right folds the page tree away and gives the list more room; the button then reads Show page tree. The app remembers your choice in this browser, so the tree stays hidden the next time you open it here.

Hiding the tree takes away a place to drop pages and a quick way to open any parent in the space. You can still open child pages from the list and go back up with the breadcrumb, drop pages on the middle of a page in the list to put them inside it, or use Move to… to reach any parent in any space.

Keyboard and screen readers

The list, the Sort menu and the questions the app asks all work without a mouse. Dropping pages inside another page, or onto the page tree, needs a pointer; Move to… does the same job from the keyboard.

• When you can move pages, every row has a grip you can reach with Tab. The dotted grip at the start of a row shows when you hover the row, tick it, or tab to it. On a grip, Space picks the page up, the arrow keys move it, Space drops it and Esc cancels. Ticked pages move together.
• A keyboard drag reorders within the list. Dropping pages into another page, or onto the page tree, takes a pointer; from the keyboard, select the pages and use Move to….
• Drags are announced. A screen reader hears Picked up and the page or the number of pages, the page it is over, and then Dropped. Save changes to apply., Dropped outside the list. Nothing moved. or Move cancelled.
• Every control names its page. A row’s checkbox is Select plus the page’s title; its grip names the page and its position (“position 3 of 12”), or, on a row ticked with others, says the other ticked pages move with it; and the × on a move in Unsaved changes says how many pages it cancels and where they were going. The header checkbox is Select all, shown part-ticked when only some pages are.
• The Sort menu behaves like a menu. Opening it puts focus on the first order; ↑ and ↓ move through the orders and the option checkboxes and wrap round. Esc closes it and puts focus back on the button, and so does choosing an order.
• Marks carry spoken labels. ▲3 is labelled “moves up 3” and ▼2 “moves down 2”.
• Progress and results are announced. The panel that shows a save running, and the one that reports how it went, are live regions, so a screen reader hears the progress and the outcome. An error in Unsaved changes is announced as an alert.
• Leave without saving? starts on the safe answer. It opens with focus on Stay, so a stray Enter keeps your changes.
• The page tree is announced as a tree. Each item says whether it is open, the parent on screen is marked as selected, and the arrow beside each item is a button named Open or Close plus the item’s title.
• Keyboard focus is always visible, and when your system asks for reduced motion, the app’s animations and transitions are switched off.

Light and dark

There is no theme setting, because the app has no theme of its own. It switches on Confluence’s theme inside its frame and takes every colour from Atlassian’s design tokens, so it follows Confluence into light or dark mode.

What the app remembers

One thing: whether the page tree is shown. That is kept in your own browser, on your own machine. Another browser or computer starts with the tree showing, and so does a browser that blocks site storage; clearing your browser data clears it.

Everything else lasts only while the app is open:

• Your unsaved changes. They come with you from parent to parent, but closing the dialog, choosing another space, or reloading, leaving or closing the page drops them — see Leaving with unsaved changes.
• Ticked pages. The selection also clears whenever you open another parent.
• The Sort options. Sort numbers by value starts ticked and Include every level below starts unticked, every time.
• Where you were. The app opens where you opened it: on a page’s child pages, on the space’s top level, or on the list of spaces. The page tree opens with only its top level showing.

Nothing is kept anywhere else. The app has no database and no storage of its own, and keeps no record of what you moved. Specs & security has the detail.

Leaving with unsaved changes

Moving around inside the app never costs you anything: open a page, click the breadcrumb or the page tree, and your unsaved changes come along. Leaving the app is different.

• Close in the ••• dialog, or ← Choose another space on the Apps page, asks first when you have unsaved changes: Leave without saving? Your unsaved changes will be lost. Focus starts on Stay; Leave without saving drops the changes and goes.
• Close is switched off while the app is busy — during a save, and while it checks pages before a move, reads dates for a sort, or looks for free titles.
• Reloading or closing the tab with unsaved changes, or while a save is running, makes the app ask your browser to warn you first. Browsers don’t always show that warning for an app running inside Confluence, so don’t count on it.