maineaa-updates/maineaa.json

{
  "name": "Maine AA Area 28",
  "slug": "maineaa",
  "version": "0.17.0",
  "download_url": "https://gitea.mulligan.casa/aa/maineaa-updates/raw/branch/main/maineaa/maineaa-0.17.0.zip",
  "homepage": "https://gitea.mulligan.casa/aa/maineaa",
  "requires": "6.7",
  "tested": "6.9",
  "requires_php": "8.1",
  "last_updated": "2026-09-24 01:34:16",
  "screenshot_url": "https://gitea.mulligan.casa/aa/maineaa-updates/raw/branch/main/maineaa/screenshot.png",
  "author": "Mike Mulligan",
  "author_homepage": "https://gitea.mulligan.casa/mmulligan",
  "tags": [
    "generatepress",
    "child theme",
    "maine aa area 28"
  ],
  "sections": {
    "description": "<p>Custom GeneratePress child theme for Maine AA Area 28.</p>\n<p>The full changelog lives in CHANGELOG.md at the repo root; the<br />\nmanifest-updater plugin picks it up from there automatically and<br />\ndisplays it in the WordPress admin's \"View details\" modal.</p>",
    "changelog": "<p>All notable changes to the Maine AA Area 28 theme are recorded here.<br />\nThe format is based on <a href=\"https://keepachangelog.com/en/1.1.0/\">Keep a Changelog</a>.</p>\n<h2>[0.17.0] — 2026-09-23</h2>\n<p>The Committees listing becomes a normal page you can edit, with a security fix and tighter email handling.<br />\n- The Standing Committees listing is now a regular WordPress page built with blocks. Editors can change its banner, heading and surrounding text in the block editor. The committee grid and meeting schedule are locked in place so they can't be removed by accident; administrators can unlock them. Existing menu links move to the new page automatically, and the old \"Page Settings\" screen under Committees is gone.<br />\n- A new \"Site pages\" section under Appearance → Customize records which page is the Contact page, the Getting Involved page, the Events page and each listing page. Links across the site follow these settings.<br />\n- New blocks: Page Hero (the banner at the top of listing pages) and Committee Schedule. The committee grid, district directory, documents, officers and committee schedule blocks can show an optional section heading. A \"Committees page\" pattern under \"Site pages\" builds the page from scratch.<br />\n- Security fix: a flaw in how the theme rewrote link attributes could let someone with a content account add script to a page. It is fixed, and updating is strongly recommended.<br />\n- Email addresses typed into page content now route through the contact form in more places: custom-field text, menus, embedded frames, links with several recipients, and addresses followed by punctuation. Administrators can turn this off, or list addresses to show as typed, under Appearance → Maine AA Setup. One example is a treasurer address used for PayPal donations.<br />\n- Smaller fixes: pages keep exactly one main heading in more situations, the meeting schedule no longer widens the page on phones, and old <code>?post_type=</code> links to the committee list go to the new page.<br />\n- The theme now requires WordPress 6.7 or newer.</p>\n<h2>[0.16.0] — 2026-09-23</h2>\n<p>Simpler Boomerang dating and a more polished News and Documents presentation.<br />\n- Boomerang issues are now ordered by their WordPress publication date, and the archive can be filtered by year. When adding a back issue, set its publish date to when it was issued.<br />\n- The manual \"This is the current issue\" switch is gone; the newest issue by date leads the list.<br />\n- The News index and single news posts share a card-style presentation, and the Documents archive carries a short description.</p>\n<h2>[0.15.0] — 2026-09-20</h2>\n<p>A clearer regional events calendar with useful listings and practical event pages.<br />\n- Event listings now use a chronological agenda with prominent date blocks, times, locations, categories, short descriptions and direct detail links.<br />\n- Maine Area 28, district and nearby-Area events can be filtered separately. New Hampshire Area 43 and New Brunswick/PEI Area 81 are recognized and clearly labeled; unknown Areas remain outside the regional feed.<br />\n- Event pages now present the description alongside a compact date, time, venue, host and calendar-download panel. The unrelated default comment form is gone.<br />\n- Local event times now display as entered in Events Manager, including clear start/end wording for multi-day events.</p>\n<h2>[0.14.0] — 2026-09-20</h2>\n<p>Safer public links and identity handling, Area-scoped events, stronger colour guarantees, and a broad accessibility and maintenance pass.<br />\n- Links in editor-authored content now follow the site's public policy automatically: off-site links receive safe relationship attributes, while email links and visible email addresses route through the contact form.<br />\n- Event listings now include untagged and Area 28 events while excluding events tagged only for another Area. The same boundary applies to the main Events page and district listings.<br />\n- Colour pins, hero photos and admin focus states now retain readable contrast across custom palettes. Body copy wraps more naturally, anchored content clears the floating navigation, and tab content remains available without JavaScript.<br />\n- Public author discovery is closed across archives, feeds, sitemaps and oEmbed output. Profile screens show editors the site's \"First L.\" display-name convention without forcing it.<br />\n- Announcement visibility and ARIA state now agree in standard, no-JavaScript and reduced-motion views.<br />\n- Small data and editor fixes cover block counts, district sorting, document queries, flat document categories, checkbox previews, Elementor cache timing, Customizer saves and unused committee-image controls. Translation loading and the source template are now included.<br />\n- Secure Custom Fields continues to load version-controlled field definitions everywhere, but may write local JSON only in explicitly local or development environments.</p>\n<h2>[0.13.0] — 2026-09-20</h2>\n<p>More accessible news and newsletter paths, working block-width controls, and native footer navigation.<br />\n- News titles with a configured source now link directly to that source from the News index and the post page. External destinations carry a visible arrow and an accessible new-tab notice; posts without a source keep their normal permalink.<br />\n- Boomerang issues can now include an optional readable HTML version. Those issues open as web pages with the PDF offered as a download; existing PDF-only issues continue to open the file directly.<br />\n- Wide and full-width controls now work on the Committee Grid, District Directory, Area Documents, Document List and CTA Hero blocks. Custom CSS classes entered in the block editor also reach the rendered page.<br />\n- Footer links now use a standard WordPress menu under Appearance → Menus. Existing footer links migrate automatically, in order, while their old option rows remain available as recovery data. Contact roles, social links, the hotline and the meeting-finder destination remain on the Footer options page.</p>\n<h2>[0.12.0] — 2026-09-20</h2>\n<p>Safer site setup, provider-neutral online meetings and contribution content, and clearer contact guidance.<br />\n- Administrators can now review and rerun the theme's site setup under Appearance → Maine AA Setup or with <code>wp maineaa setup</code>. Setup repairs missing defaults, retries failed work, and notices when a required plugin becomes available, while preserving deliberate role changes and later Elementor edits.<br />\n- Announcements now have their own permissions. Administrators, Editors and Chairs can manage the full announcement lifecycle; Content Editors can work on their own announcements without publishing authority; Authors and Contributors do not gain announcement access.<br />\n- Committee and district online-meeting fields now support Zoom, Microsoft Teams, Google Meet and other services. Existing invitation links are preserved. A valid Zoom meeting ID can create a join link when no link was supplied, while the passcode remains visible separately for entry. Private meeting credentials remain hidden from both pages and the public data feed.<br />\n- Seventh Tradition content is no longer tied to PayPal. Editors can enter linked contribution instructions, an optional QR image and mailing addresses. Existing contribution data migrates automatically without replacing later edits.<br />\n- The managed contact form now recovers when Contact Form 7 is installed after the theme or reactivated, without creating duplicate forms. Concurrent setup requests fail safely and retry later.<br />\n- The login screen uses the site's normal logo when no separate login logo is configured.<br />\n- Editor guidance now says exactly what the site does: supplied phone numbers may be published, while email addresses route through the contact form. Private meetings use the same wording throughout the editor and public pages.</p>\n<h2>[0.11.0] — 2026-09-16</h2>\n<p>Security hardening, a header menu that stays on one line, and two fixes that keep the site's styling stable.<br />\n- Security: the site no longer answers XML-RPC, an old remote-publishing interface that nothing here uses but that is a favourite target for automated password guessing. It also no longer discloses user accounts to anonymous visitors: author-archive probes are sent to the home page, and the public users feed is closed to logged-out requests. The theme and plugin file editors built into the dashboard are switched off. Normal editing in wp-admin is unchanged.<br />\n- The header menu now stays on one line. Any items that do not fit fold into a \"•••\" dropdown at the end of the bar, which appears only when something actually overflows. To turn it off: Customize → Maine AA — Advanced → Header → \"Keep the menu on one line\".<br />\n- The current and hovered menu items are now marked with a coloured underline rather than a filled grey box, so the label stays readable at every colour setting. High-contrast and forced-colour modes fall back to a plain underline.<br />\n- Fixed: on a fresh activation, GeneratePress could mistake the theme's own setup for an old installation and write pre-3.0 defaults over the site. That showed up as grey menu boxes, a legacy header layout and a missing header search icon. The theme now registers itself correctly and paints the menu colours from the site palette.<br />\n- Fixed: stylesheet changes now reach returning visitors' browsers as soon as they ship, instead of waiting for the next version bump. Previously a cached copy could persist on phones after an update.<br />\n- The changelog moved out of readme.txt into CHANGELOG.md, which is the file the updater's \"View details\" panel displays.</p>\n<h2>[0.10.2] — 2026-07-26</h2>\n<p>Stability fixes, a full assembly archive, and a cleaner hero for visitors whose browser or OS is set to high-contrast mode.<br />\n- Fixed two crash bugs: any request to /news/ or /documents/ with a malformed URL parameter (e.g. <code>?news[]=1</code>) would return a 500 error. Both pages now handle the input gracefully.<br />\n- Announcements no longer leak through the site's data feed before their show-from date or after their show-until date. On-page display was already correct; the feed now matches.<br />\n- The Districts index now shows the Area 28 districts map at the top of the page, with the district cards below.<br />\n- The district card now groups servants by role (all DCMs together, all Alt DCMs together, etc.) and shows the meeting location and format rather than the district number chip (the \"District N\" heading already carries the number).<br />\n- The Assemblies index now shows every assembly on a single page. Previously the list was capped at ten posts, which could push the sole upcoming assembly (and its featured \"Next Assembly\" card) out of view when past assemblies were back-filled.<br />\n- Higher-contrast browsers and OS settings (macOS/iOS/Android \"Increase contrast\", Windows High Contrast, Firefox contrast preferences) now get a cleaner hero: the design's subtle opacity dimming is removed and hero photo backgrounds (Home, Documents, hero-image variants) swap to the guaranteed brand gradient. Default experience is unchanged; the site respects the browser/OS signal automatically, no in-page toggle.<br />\n- The A− / A / A+ text-size stepper in the primary menu is now off by default. Modern browsers and phones/tablets provide native page zoom and system font scaling that reach every site; the in-header control took real estate most visitors did not use. To bring it back: Customize → Maine AA — Advanced → Accessibility → \"Show text-size stepper\".<br />\n- Defense-in-depth escaping on document library body content.</p>\n<h2>[0.10.1] — 2026-07-26</h2>\n<p>Contact form UX polish — the routing form is easier to reach and easier to read on both mobile and desktop.<br />\n- On mobile, the committee detail page shows the committee's own tabs first; the long list of \"Other committees\" is a collapsed disclosure below, so you don't have to scroll past it to see who chairs this one. Desktop is unchanged (the list stays visible on the left, as always).<br />\n- On mobile, the officers roster on /contact/ shows three tappable group headings (\"Elected Officers\", \"Committee Chairs\", \"Non-voting Positions\") — each collapsed by default so the contact form is on the first screen. Tap a heading to reveal the roster; desktop is unchanged.<br />\n- Every \"contact this chair / DCM / officer / assembly coordinator\" link now scrolls straight to the form (via a #send-message anchor) instead of dropping you at the top of /contact/.<br />\n- Contact links pasted into the footer's Contact column now pre-select the right recipient in the form's dropdown when the address matches an officer, chair, or DCM on file — so a footer link to the Area Chair opens the form with \"Chair\" already selected. Unknown addresses still fall back to the form with the dropdown blank; no address is ever exposed.<br />\n- The dropdown option labels now include the seat holder's name (e.g. \"Website — Chair — Marissa May C.\", \"Delegate — Willy K.\") when a name is on file, so you can pick the right person by name rather than by role alone. The confirmation banner on assembly deep-links reads the same way.</p>\n<h2>[0.10.0] — 2026-07-26</h2>\n<p>Servant anonymity: emails are no longer on the site or in its data feed; a new role-mapped contact form on /contact/ routes members to the right chair, DCM, officer, or assembly coordinator without ever showing the address.<br />\n- Every rendered servant email is gone from every page and from the site's data feed. Committee, district, officers-roster and assembly pages show role and name; where a contact avenue makes sense, the name is a link that opens the new contact form pre-configured to reach that seat. The addresses stay in the admin so the form can deliver, but they never appear in a page, a link, or the site's data feed.<br />\n- The new form on /contact/ carries a \"who would you like to reach?\" dropdown built live from the current officer, committee and district data — a chair change or a new committee shows up automatically, with no editing.<br />\n- Assembly coordinators are reachable through a per-contact link on the assembly page — the coordinator's name links into the form in \"Contacting {name}\" mode, so a member can write to the right person without their address ever being published.<br />\n- Free-form \"mailto:\" links pasted into the footer's Contact column are automatically rerouted to /contact/ so no address ships in the page source. The crisis hotline (1-800-737-6237) is unchanged.<br />\n- The one personal phone number the content model carried — the assembly coordinator phone — has been removed entirely: from the editor form, from the page, and from the stored data. Institutional phones (crisis hotline, venue phones, other-org public numbers) are unchanged.<br />\n- Contact Form 7 is now a required plugin (like Secure Custom Fields). If it is missing, an admin notice explains what to install; the officers roster on /contact/ still renders, only the form is absent.</p>\n<h2>[0.9.1] — 2026-07-24</h2>\n<ul>\n<li>If the site is ever running the wrong custom-fields plugin — WP Engine's free \"Advanced Custom Fields,\" which leaves out the repeaters and options pages this theme's content is built on — or none at all, the dashboard now shows a clear notice explaining that Secure Custom Fields is required, with a link to install it, instead of committees, districts and rosters silently failing to appear.</li>\n</ul>\n<h2>[0.9.0] — 2026-07-24</h2>\n<p>Print-friendly pages, closed-meeting privacy, a scannable document library, and editor dashboard help.<br />\n- Every page now prints cleanly. When you print (Ctrl+P), the menus, floating buttons and other on-screen chrome drop away, colours flatten to black-on-white, collapsed sections and tabs open so nothing is hidden, web links show their address, and a \"Printed [date] — check the site for the latest version\" line is added at the foot. Made for the rosters, schedules and packets handed out at assemblies and district meetings.<br />\n- Closed meetings no longer publish their join details. When a committee or district meeting is marked \"closed,\" its Zoom link, meeting ID and passcode are hidden everywhere — on every page and in the site's data feed — and replaced with a \"contact the chair for access\" note.<br />\n- The Documents library now opens as a set of clearly labelled categories you expand, with a row of category filters across the top, so you can jump straight to the one you need instead of scrolling one long open list. A document can also record the earlier one it replaces.<br />\n- District pages now carry a \"Service resources\" panel linking the guidelines, assemblies, and the For-GSRs / For-DCMs pages, so a DCM landing on their own district has the service documents one click away.<br />\n- A committee's Files can now link a document straight from the library rather than re-typing its web address, so the link keeps working when the document is updated.<br />\n- Two new dashboard helpers for the volunteers who edit the site: a \"Before You Publish\" checklist (anonymity and accessibility reminders, each linked to the relevant guidance) and a \"Writing Style\" reference card; committee chairs see a tidy dashboard with only what they need.<br />\n- Cards keep a clear outline even at the flattest \"elevation\" setting, so groupings never visually collapse.</p>\n<h2>[0.8.0] — 2026-07-23</h2>\n<p>A \"page not found\" page that helps, plus site-wide search.<br />\n- Mistyped or out-of-date links now land on a friendly \"page not found\" page that offers a search box, the main sections to browse, and — when the web address makes it clear — a direct suggestion of the page you were probably after (for example a link to /contact-us/ points you to Contact). When the address is too broad to guess from, it simply fills the search box with those words so you can press Search.<br />\n- A search magnifier in the site header, and a matching search results page that finds committees, districts, documents, newsletters, and assemblies, with the option to narrow results to one type.<br />\n- The \"Find a Meeting\" pill now uses the correct brand colour and is properly legible; the header search link is aligned with the text-size controls beside it.<br />\n- Announcement-band text is now guaranteed readable on whatever band colour is chosen.</p>\n<h2>[0.7.0] — 2026-07-22</h2>\n<p>Visual polish wave + a floating Find-a-Meeting pill.<br />\n- Larger hero pathway pills on small screens.<br />\n- A minimal floating navbar that appears on scroll (mobile), with the hamburger opening the menu as an on-screen overlay.<br />\n- The A-/A/A+ text-size control moved off the mobile header into the slide-out menu.<br />\n- A persistent help bar (mobile bottom bar / desktop pill) showing the AA hotline, driven by the existing footer setting.<br />\n- A new floating \"Find a Meeting\" pill linking the Meeting Guide app and the Maine meeting list; adds one owner-editable \"Find a Meeting URL\" setting in the Footer options.<br />\n- Body/editorial link underlines, an H6 minimum size so no heading matches body text, and brand-hue-aware shadows.<br />\n- Accessibility and mobile-breakpoint refinements throughout.</p>\n<h2>[0.6.1] — 2026-07-21</h2>\n<ul>\n<li>No-DCM district pages now show a short \"this service seat is open\" page with a get-involved link, instead of returning a \"page not found\" error.</li>\n</ul>\n<h2>[0.6.0] — 2026-07-20</h2>\n<ul>\n<li>A cleaner, friendlier wp-admin for the volunteers who edit the site: the editing experience now matches the site's look — warm colours, the site fonts, plainer wording, and far less clutter.</li>\n<li>Committee chairs get a simplified dashboard — a welcome with quick shortcuts to the pages they manage, plus a site-stats panel (unique visitors, sessions, a 30-day trend, and top pages).</li>\n<li>A branded login screen and site header carrying the Area 28 mark.</li>\n<li>Calmer editing screens: fields grouped by space instead of boxes, related fields placed side by side, short fields sized to fit, plain-language labels, and \"(optional)\" markers instead of required asterisks.</li>\n<li>New \"Chair\" and \"Content Editor\" roles with least-privilege defaults, and a trimmed admin menu so non-technical volunteers see only what they need.</li>\n</ul>\n<h2>[0.5.0] — 2026-07-19</h2>\n<ul>\n<li>The \"Submit an Event\" form now matches the rest of the site — brand colours, fonts, and buttons throughout, including the date-range calendar and the time pickers, with a tidier two-column layout.</li>\n<li>Two new page-building blocks any editor can drop into a page: a gradient hero banner (eyebrow, heading, text, and an optional button or background photo), and a resource list of bordered link rows where each row can carry several links (for example \"Read\" and \"PDF Download\").</li>\n<li>New Digital Newcomer Packet and New to AA pages, built from those blocks, gathering the AA newcomer resources in one place.</li>\n<li>A page that opens with a hero banner no longer shows a duplicate page title above it.</li>\n</ul>\n<h2>[0.4.3] — 2026-07-18</h2>\n<ul>\n<li>The homepage hero can now hold more than one banner photo. Add several and the site can rotate through them on each visit, or leave rotation off to always show the first.</li>\n<li>Give any hero photo a season — a start and end date — so it only appears during part of the year (for example a winter photo from December through February); the dates wrap across the new year automatically.</li>\n<li>Choose which part of each hero photo stays in view — top, middle, or bottom — when it is cropped to the banner.</li>\n<li>Fully optional and non-destructive: a single existing hero photo keeps working unchanged, and with nothing set the homepage looks exactly as before.</li>\n</ul>\n<h2>[0.4.2] — 2026-07-18</h2>\n<ul>\n<li>Added a theme preview image — the card shown under Appearance → Themes. No change to the public site.</li>\n</ul>\n<h2>[0.4.1] — 2026-07-18</h2>\n<ul>\n<li>New \"Page Settings\" screen for each index page — Committees, Districts, Boomerang, Documents, Assemblies, and the Events page — so editors can add a custom heading, a subtitle, and rich intro text above or below the list.</li>\n<li>Add an optional header photo to any of those pages; a built-in overlay keeps the title readable over any image, and you choose which part of the photo stays in view.</li>\n<li>An \"Edit This Page\" button appears in the toolbar while viewing one of these pages, linking straight to its settings.</li>\n<li>Fully optional and non-destructive: every index page looks exactly as before until you fill something in.</li>\n</ul>\n<h2>[0.4.0] — 2026-07-17</h2>\n<ul>\n<li>New colour system: pick a brand colour, an accent, and a neutral \"paper\" colour — surfaces, borders, and buttons all derive from them, with WCAG-AA contrast still guaranteed automatically.</li>\n<li>A Brand tint dial washes the whole page toward the brand colour, or leave it at zero for a clean neutral; an optional \"Match neutral to brand\" gives surfaces a subtle brand tint.</li>\n<li>Hero and call-to-action panels now use a richer on-brand gradient instead of a flat fill.</li>\n<li>New Corners dial (sharp to round) and a Preset picker — Area 28, Harbor, Pine, Slate, and Dusk — that sets a whole look in one click, with room to fine-tune from there.</li>\n<li>Retired the separate neutral-temperature dial; choosing a warmer or cooler neutral colour now does the same job.</li>\n</ul>\n<h2>[0.3.0] — 2026-07-17</h2>\n<ul>\n<li>Structured content: Standing Committees, Districts, Assemblies, Documents, and the Boomerang newsletter are now their own content types with dedicated fields and templates, instead of hand-typed pages.</li>\n<li>Committee pages are a tabbed detail (Info / Meeting / Files / Get Involved) with a persistent facts header. \"Zoom\" is relabeled to a platform-agnostic \"Meeting / Join\" ahead of the move to Teams.</li>\n<li>Getting Involved lists the committees with open positions and links straight to each committee's Get Involved tab; open positions are editable per committee.</li>\n<li>News gains an All / Area / GSO category filter, and Events gains an All / Area / District filter over one branded list.</li>\n<li>Assemblies feature the next assembly on top, with upcoming and past listed in date order.</li>\n<li>Homepage pathway buttons now smooth-scroll to their section, and each section can carry a \"Read more\" link to a full page.</li>\n<li>Added a rich site footer, a scheduled announcement band, and a two-line wordmark.</li>\n<li>Data-heavy content types use the classic editor so their fields are easy to see and edit.</li>\n<li>Mobile polish: aligned list cards, tidier text-size controls, and consistent spacing.</li>\n</ul>\n<h2>[0.2.0] — 2026-07-16</h2>\n<ul>\n<li>Colors now flow through GeneratePress's own Global Colors and the block palette, so blocks and Elementor pages inherit the site palette automatically.</li>\n<li>Light mode only — the dark mode and manual dark toggle have been removed.</li>\n<li>New design-knob system: pick a brand color and an accent color, then fine-tune with surface-depth, text-contrast, neutral-temperature, elevation (flat to lifted), density (compact to airy), accent-vividness, and text-temperature dials — all with live preview.</li>\n<li>Self-hosted fonts (Manrope and Syne) delivered through GeneratePress Typography, with nothing hot-linked to third parties.</li>\n<li>Accessibility and fidelity fixes: responsive headings, WCAG-AA contrast, clear keyboard focus, and teal buttons.</li>\n</ul>\n<h2>[0.1.0] — 2026-07-15</h2>\n<ul>\n<li>First release: selectable design-token system with brand, accent, and neutral-warmth choices; contrast is checked for WCAG-AA safety, generated when you save, and cached.</li>\n<li>Automatic light and dark mode following your device preference, plus a manual dark toggle; per-visitor A-, A, and A+ text-size control; no flash of the wrong theme on load.</li>\n<li>Self-hosted fonts (Manrope, Syne, Source Sans 3, Libre Baskerville) with nothing hot-linked to third parties.</li>\n<li>GeneratePress styled on-brand through the token system, with Customizer controls and live preview.</li>\n<li>Accessibility foundations: skip link, semantic landmarks, and ARIA on tabs and controls.</li>\n</ul>"
  }
}