WP Manifestindependent plugin directory
manifest / editor / wp-child-page-tools

Child Page Tools

Tools to manage navigation and 'progress' across a set of sibling WordPress pages.

by RAV · github.com/hughc/wp-child-page-tools

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/hughc/wp-child-page-tools/archive/refs/heads/master.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/hughc/wp-child-page-tools ↗

WordPress Child Page tools

overview

A WordPress plugin exposing 3 Gutenberg blocks

  • Next / Previous sibling page links
  • Progress indicator block ( x/y to monitor position amongst siblings)
  • parent page title block

All calculations of the current page (for progress) and next / prev pages are based on finding an array of 'sibling' pages (ie those sharing a common parent), sorted by menu order, and determining the next / prev page to link to. This means you can use a plugin like Simple Page Ordering to arrange pages in a menu order, and then use that order to navigate between then

Sibling resolution rules

  • If the current page has a parent, siblings = all child pages of that parent (parent page itself is excluded).
  • If the current page is top-level (no parent), siblings = all other top-level pages.
  • Siblings are sorted by menu_order ASC, then ID ASC as tiebreaker.
  • If the current page is first or last in the sequence, the corresponding block hides (renders nothing).

Next prev block

UI options are

  • Direction: (next / previous)
  • Text
  • Icon

Progress block

Progress is displayed as an x / y string with a configurable text template using {current} and {total} tokens. Default template: {current} / {total}.

This plugin was written by Qwen3.6-plus under my iterative prompting, testing and debugging (although the initial implementations were all quite good).