Documentation edition: 9 September 2026

Content and directory maintenance

Add or correct a regional club

Search the directory first, including alternate spellings. Use the installed add/edit tool and its existing access controls. Confirm the kennel name, country/state, website/contact, run details and history with the club where possible. Save, reload the listing and verify links. If a field displays question marks, stop and check encoding before saving the damaged display back to the database.

Do not use a direct SQL insert copied from an old example: required fields, IDs and validation may have changed. The latest add-club implementation was not supplied for this documentation release. Use its installed form or obtain its current source before extending it.

Add a license plate

In the supplied gallery, entries live in the $plates array in /plates/index.php.

  1. Back up the current file and retain the original photo privately.
  2. Choose a simple unique filename, such as plate106.jpg, and upload it into /plates/. Match filename capitalization exactly.
  3. Copy one existing array entry and update its image, hasher, kennel and notes values. Escape apostrophes correctly in PHP string literals; do not remove array commas.
  4. Preserve the current page's image-alt implementation. Describe identifying visible text and the relevant hasher/kennel without inventing details.
  5. Validate PHP syntax, upload the changed file, search for the new entry and test enlargement.

The delivered gallery had 105 entries; that was a source snapshot, not a current live count. Some kennel/notes strings contain trusted HTML links. Do not insert unreviewed submitted HTML into these fields.

Install the plate lightbox

Upload plates-lightbox.js into /plates/, then add the following before </head> in the current gallery page:

<script src="/plates/plates-lightbox.js?v=1" defer></script>

The script works with the supplied .hm-legacy-card layout, .plate-card/.plate-item layouts and plate* image filenames under /plates/. It keeps existing image links as a fallback. Differently named photos should be within a supported card. Increment the version query when replacing the script so browsers request the update.

Add or restore songbook scans

Keep the existing /songbook/ PDF and JPG assets; changed-files packages omit them. Numbered scan filenames follow magic_page06.jpg; the four cover slugs are outerfrontcover, innerfrontcover, innerrearcover, outerrearcover. The delivered viewer recognizes pages 01–92 and those covers.

Restore an original missing scan under its expected name rather than renumbering later pages. A new page outside the current range needs the viewer whitelist and overview updated together. Test original-size links, previous/next, cover transitions and the complete PDF. OCR/searchable lyrics would be a separate feature.

Edit About or the homepage

Use the latest server file. Preserve shared header/footer includes and the founder's original text unless intentionally editing it. The About update added a timeline and an expandable historical account; dated statements in that account should not be presented as current operational facts. Test links and phone layout after changes.

Update navigation

The main site header lives at /2025header.php. Where section navigation lives at /where/awhere_menustrip.php. Keep global resources in the main header and account/report controls in the Where menu.

Kennel Leaderboards belongs after Where Hared under Rankings & reports:

<li><a href="awhere_kennel_leaderboard.php" class="where-menu__link<?= $activeClass('awhere_kennel_leaderboard.php') ?>">Kennel Leaderboards</a></li>

Retain the existing login/logout logic, active-class callback and horizontal mobile scroll. The page must actually include the menu strip; editing the menu file alone cannot add it to a page that never loads it.

Record a content change

Keep a date, affected paths or record IDs, short reason, backup location and verification result. Use a private maintenance record for personal information. Do not include credentials in release notes.

Maintain continent classifications

Adding a country to the reference list is separate from assigning its real continent. Preserve existing IDs because users' selections are positional. Use Country Continents in Site Administration after a new country is added. Keep the old area label for checklist organization and choose one real continent for milestones. Do not rename or reorder reference IDs to fix map aliases.

Choose a documented site convention for transcontinental entries. A single country checkbox cannot identify which part of a country a hasher visited. Record the reason for unusual assignments in your private maintenance notes.

Update help content

The new-user guide is the introductory walkthrough; the site user guide gives more detail. The site description supplies reusable introductory wording. Update the relevant Markdown file and regenerate HTML together. If presenting these guides publicly, use only visitor-facing documents; the admin viewer requires login, but static HTML files beside it are not automatically protected.