Website

This standard governs the public website content maintained through the content management system: pages, banners, the photo gallery, navigation, reusable content blocks, search metadata, promotions, and shop products. It is used by Content Editors, who prepare and publish website content; by the Store Manager, who approves promotions and product changes; and by the Web Administrator, who owns publishing rights and the audit log. The website is assembled from database records, and each part of the site reads from one specific store. Editing the wrong store is the most common cause of "the change did not appear," and this standard states which store each part reads.

Roles and duties

• Content Editor: prepares pages, gallery photos, content blocks, and search metadata; previews every change before publishing.
• Store Manager: approves promotions and shop product changes and confirms each promotion in a test checkout before it is announced.
• Web Administrator: grants and removes publishing rights, reviews the audit log, and resolves publishing failures.

How publishing works

All website changes are made through the CMS Management screens in the admin console. Every action writes its record and an audit log entry with the operator, the time, and the resulting state. The public site displays stored default content on first load and then refreshes as changes are published; a published change may take a few minutes to appear everywhere. That delay is the normal refresh cycle, not a failure. If a change has not appeared after a few minutes, the operator shall follow CMS Troubleshooting.

Only seven public content resources are readable by anonymous visitors: services, service items, testimonials, frequently asked questions, policies, gallery, and add-ons. All other content requires an administrator session to read, and all changes require an administrator session. This restriction is a security control and shall not be worked around.

Pages

General pages are held as page records carrying a web address name, title, page type, body content, laid-out content blocks, excerpt, featured image, publication state, and an optional scheduled publication time. Every save creates a revision record with a version number and the operator's change note. Change notes shall describe the change in terms a reader six months later can act on: "Updated holiday hours for Thanksgiving week," not "updates." To remove a page from the site without deleting it, withdraw it from publication; the content and its revision history survive.

Banners

Banners are records with a type (hero, promo bar, popup, inline, footer, or alert), a placement (home, all pages, services, booking, portal, or custom), an active switch, a sort order, and a start and end time. A banner displays only when it is active, the current time falls inside its window, and its placement matches the page. Every banner shall carry an end date; a banner with no end date remains until someone remembers it, and an out-of-season promotion left on the site damages customer trust.

Gallery

The public gallery reads one photo store only: each photo carries an image, alternative text, a category (GROOMING, BATH & SPA, TRANSFORMATIONS), a display order, and a visible switch. Photos placed in any other gallery store do not appear on the site, and operators shall not use those stores. Captions shall state what the photo shows and which service it represents. The Content Editor shall add recent work regularly; a gallery whose newest photo is a year old tells visitors the business is idle.

Navigation

Navigation is maintained as menu records for the primary, footer, mobile, utility, and portal menus. Each entry requires a label and either a web address or a linked page, a parent entry where it sits in a dropdown, and an explicit sort order. Labels shall be words a customer understands ("Book Grooming," not internal module names). Dropdowns are one level deep. An entry shall never link to a page that is not live.

Reusable content blocks

Reusable blocks hold text that appears in many places: the phone number, the address block, the holiday-hours notice, the tagline: each under a content key, with a text or structured value, grouped for findability. The locale on every block shall be en-US; a block created under any other locale value is never read by the site. Branding values: the primary colour and the logo: are maintained as settings on the same screens. The point of the block store is single-source editing: before typing repeated text into a page, the Content Editor shall check whether it belongs in a block, because the same phone number typed into five pages is a future inconsistency.

Search metadata

Per-page search metadata is maintained for each page and as a site default: meta title, meta description, the preferred page address, and social-sharing title, description, and image. The meta description is the snippet shown in search results and is the highest-value field. Titles shall be kept under 60 characters and descriptions under 160 characters, or search engines truncate them. The content system controls per-page metadata only; crawl policy is maintained in the site's own sitemap and robots configuration, outside the console.

Promotions and shop products

Promotions are built in the Promo Builder: name, a unique uppercase code, type (percentage off, amount off, or free add-on), value, what it applies to, eligibility (new, existing, or all customers), start and end dates, maximum total uses, maximum uses per customer, whether it may be combined with other offers, and the placements where it is published. A discount with no end date and no usage cap is a liability, not a promotion, and shall not be published. After creating a promotion, the Store Manager shall test it in a real checkout before it is announced. Promotional offers to customers are governed by the Promotional Offers Terms.

Shop products maintained through the console carry a name, category, display price, payment price identifier, badge, image, alternative text, description, order, and visible switch. Entering the payment price identifier is what enables checkout for that product. Deleting a product through the console also retires its payment counterpart; the console record governs, and deletion completes in the console even if the payment update fails.

Services and pricing content is governed by Services and Pricing; payment method settings are governed by Payments and Gateway.

Controls

Publishing rights are limited to the Content Editor, Store Manager, and Web Administrator roles. Every console action is audit-logged. The Web Administrator shall review the audit log whenever content changes without explanation, and shall treat the log: not recollection: as the record of who changed what.

Records

This standard produces page records and their revision history, banner, gallery, navigation, block, and metadata records, promotion and product records, and the audit log entries for each action. Revision history is retained permanently; it is the evidence of what the site said on any given day.

Escalation

Publishing failures that CMS Troubleshooting does not resolve go to support@aapawz.com. Content that raises a legal question: a claim the Company may not be able to substantiate, or wording that conflicts with a governing policy: goes to legal@aapawz.com before it is published.

Review cadence

The Web Administrator reviews banners, promotions, and the gallery monthly for expired or stale content, and reviews publishing rights quarterly.