Waiting on Client
Spanish Translation — Track B (Custom AI Workflow)
Property: main-site + solano-site (cross-property) Date: May 6, 2026 Status: Pitched in Eric's May 4 reply, parked pending Anders' decision
What's Done
- Two-route reply sent to Anders (May 4): simple GTranslate toggle vs. custom AI-assisted page-by-page workflow with reviewer sign-off.
- Anders chose simple route for now (May 5): "make the translate toggle larger and more obvious. I'll get back to you on the more intensive one soon."
- Discovery on both sites complete. Track A (prominent toggle on both sites) is moving in parallel under Todoist project "California Forever — Spanish Translation."
What's Needed from Client
Anders to come back with one of: - Greenlight to scope hours + monthly cadence for the AI workflow - Confirmation of a bilingual NorCal-familiar reviewer (gating dependency) - Or a "stick with the simple toggle for now" if he decides Track B isn't worth the lift
Resume Path
- When Anders re-engages, build hours quote and CMS strategy decision doc (Polylang Pro vs. TranslatePress vs. WPML vs. shadow ACF) before any build.
- Glossary template ready for joint working session.
- Reference:
main-site/Retainer/2026-05-06-spanish-translation-scope.md
Blog Reverse-Chrono List Layout — Mike Design Review
Property: main-site
Date: May 6, 2026
Status: Parked on branch fix/blog-list-layout, waiting on Mike
What's Done
- New row-based list layout on home.php (image left, title + excerpt + date)
- Reverse chronological reading order, no big/small card mix
- Image fallbacks (bg-sky / bg-sand) preserved for thumbless posts
- Filter pills, pagination, archive link untouched
- Verified at desktop 1280, mobile 375, plus /blog/?type=all
- Branch pushed to origin, no PR
What's Needed from Client / Internal
Mike to weigh in on design direction: - Image width (256px) - Aspect ratio (3:2 / pb-[66%]) - Gap between image and text - Whether fallback rows should look distinct from image rows
Resume Path
- Checkout
fix/blog-list-layout - Adjust per Mike's feedback
- Rebuild Tailwind, screenshot, post for review
- Open PR when approved
Files Changed (PR not yet opened)
home.php— new list layoutcss/tailwind-output.css— recompiled
Blog Archive — Older Posts to Add
Property: main-site Date: Apr 27, 2026 Status: Live, waiting on Jan for next batch
What's Done
- 9 trashed posts (Aug 2023 → Dec 2024) restored and tagged
archive. - New
/category/archive/page live at https://californiaforever.com/category/archive/ - National, Local, and All views: reverse chronological, archive category filtered out.
- Persistent "For archive of older blogposts, please click here" link on every blog filter view.
- Editorial workflow documented: tag a post
archivein WP admin → it leaves the main feed and appears on the archive page.
What's Needed from Client
Jan said in Apr 27 Basecamp thread: "there will be more posts we used to have online that we'll want to add."
He needs to send over the next batch of older content (titles, copy, images, dates) for us to add as new posts under the archive category. Investigation showed ~38 historical posts that Wayback Machine captured but are no longer in the database — Eric offered to dig those out (~1 hr to find/list/recover) if Jan wants, pending Jan's confirmation that the billable hours are OK.
Files Changed (PR #15, merged)
home.php— query order, archive exclusion, persistent linkcategory-archive.php— new templatecss/tailwind-output.css— rebuilt
Slack Pledge Approval - Interactivity Setup
Property: main-site Date: Jan 14, 2026 Status: Waiting on client response
What's Done
- Dual-webhook integration implemented in
inc/integrations/slack-pledge-approval.php - Client's Slack credentials configured (webhook URL + signing secret)
- G&M monitoring webhook retained (notifications without buttons)
- Documentation updated
What's Needed from Client
Client needs to enable Interactivity in their Slack app:
- Go to https://api.slack.com/apps
- Select the Pledge Approvals app
- Click Interactivity & Shortcuts
- Toggle Interactivity to ON
- Enter Request URL:
https://californiaforever.com/wp-json/cf/v1/slack/pledge-action - Save Changes
Next Steps (Once Client Confirms)
- Deploy code to production
- Test end-to-end: submit test pledge → verify notification in both Slack channels → click Approve in CF Slack → verify status updates
Files Changed
inc/integrations/slack-pledge-approval.phpdocs/slack-pledge-approval/README.mddocs/slack-pledge-approval/SETUP-GUIDE.mddocs/slack-pledge-approval/OVERVIEW.md