Monday, October 19, 2026 · Web Development · StayWithJay
Work session: Approximately 10:00 AM–4:00 PM Eastern, with partner-related work beginning around 7:00–8:00 AM amid other activities. Work continued beyond 4 PM. These are user-reported estimates, not a verified time log.
Session outcome
Partner registration and intake are working. The registration email is being received. The visual Partner Hub design has been established, and WordPress, ACF and Otter Blocks integrations were tested. The production-ready, visually editable dynamic Partner Hub remains unfinished.
What worked
- Partner user registration successfully creates WordPress accounts and captures registration data.
- Registration notification email is received; visual/email refinements remain possible.
- Identified and verified ACF field references and the Otter dynamic-content markup for logged-in user names, profile pictures and profile fields.
- Confirmed WPVibe can read WordPress user data and ACF definitions, create/edit pages and publish native Gutenberg blocks.
- Created and published an Otter Tabs test with Home and Profile tabs, plus a Promotions post-type grid.
- Established the desired Partner Hub visual direction from the actual StayWithJay screenshot: white cards, light pink accents, rounded tab navigation and clear tiles. No unrelated stock imagery should be used.
Pages and references
- Partner Hub — Full Design (page #19469): accepted visual direction but not editable in the desired way.
- Partner Hub — Native Blocks (page #19472): editable foundation with some dynamic bindings.
- Partner Hub Native Blocks V2 (page #19476): published but not operational end-to-end.
- Partner Hub Tabs Test (page #19482): published Otter tabs and Promotions query experiment.
Agreed architecture
The Partner Hub is a junction of editable WordPress/Otter building blocks, not a custom application. Home shows overview tiles; Find Work queries open Honest Gig opportunities using WordPress post types and taxonomies; My Jobs queries jobs claimed by the logged-in partner; Profile reads WordPress user and ACF values; Learn links to relevant rules, procedures and safety material. Availability windows should be captured by a form or other stored record rather than rendered as an elaborate interactive landing-page interface.
Rules, regulations and qualification
An adjacent form or job-specific process should capture acknowledgment of rules, regulations, safety and procedures. Cleaning is the initial focus. Requirements may vary by service, property, task and partner: a maintenance worker may have different prerequisites than a cleaner. Some additional requirements may be communicated or requested by email, text or in person. Requirements and acknowledgment evidence must be recorded in an appropriate system; an email, text or conversation alone should not automatically be treated as completed verification.
Outstanding work
- Finish the clean, editable Partner Hub using native Otter/Gutenberg blocks matching the supplied design.
- Connect dynamic queries for open Honest Gig opportunities and the logged-in partner’s claimed jobs.
- Verify profile name, photo, services and contact information render for the logged-in partner.
- Create a restricted WPForms profile-update form exposing only approved fields; avoid sending partners into wp-admin.
- Review and restrict partner-role backend capabilities.
- Improve the registration page’s light visual design while retaining the working registration and login forms.
- Refine registration notification email presentation.
- Create a rules/regulations and job-qualification acknowledgment form, starting with cleaning and allowing service/property-specific requirements and additional email, text or in-person requests.
Assessment
Today’s substantial morning-and-afternoon effort delivered a functioning partner-registration foundation, confirmed email receipt, validated key WordPress/ACF/Otter capabilities and clarified the correct content-dashboard architecture. The main remaining gap is connecting the accepted visual design with real, permission-scoped dynamic content. No guest communications were sent as part of this session record.