Within Reach
Claude Build Instruction
Platform: WordPress (Custom Theme + ACF Modular Architecture)
1. Platform Requirements
- WordPress (latest stable)
- Custom theme (no page builders)
- ACF Pro (Flexible Content-based architecture)
- The Events Calendar Pro
- SEO plugin compatible
- Clean, scalable, maintainable code
No Elementor. No Gutenberg block sprawl. No unnecessary plugins.
2. Content Types
2.1 Initiatives (Custom Post Type)
Register CPT:
post_type: initiative
slug: initiatives
has_archive: true
public: true
URL structure:
/initiatives/{slug}
Purpose:
Evergreen pillar pages representing key focus areas.
Do NOT relate to Events for now.
Each initiative uses modular ACF sections.
2.2 Stories (Custom Post Type)
Register CPT:
post_type: story
slug: stories
has_archive: true
public: true
URL structure:
/stories/{slug}
Stories are editorial only.
No categories.
No tags.
No author display.
Chronological archive.
2.3 Events
Use The Events Calendar Pro.
Do NOT register a custom Events CPT.
Use: tribe_events
Override templates for styling only.
Do not break plugin functionality.
No relationship to initiatives (for now).
3. Core Pages
Create standard WP pages for:
- Homepage
- CityServe
- O,NE
- Partners
- Join Form
- About
- State of the City
- Give
- Footer pages (Terms, Privacy, Web Accessibility, Signup)
All built using ACF Flexible Content.
4. ACF Architecture
Use Flexible Content on:
- Homepage
- All Initiative pages
- About
- CityServe
- O,NE
- State of the City
- Give
Create reusable section modules:
- Hero
- Content + CTA
- Video
- Stats
- Testimonials
- Stories Feed
- Events Feed
- Initiative Grid
- Form Embed
- CTA Block
Sections must be reusable across page types.
No hardcoded page layouts.
5. Stories Requirements
Archive (/stories):
- Grid layout
- Featured image
- Title
- Short description
- Date
- Pagination
Single Story:
- Hero
- Subtitle
- Optional video
- Body content
- Pull quote
- Share row
- Recent Stories module
- CTA section
Homepage Stories Module:
- ACF toggle: auto (latest) OR manual selection
6. Initiatives Requirements
Each Initiative:
- Modular layout
- Overview section
- Optional video
- Optional stats
- Optional testimonials
- Optional CTA blocks
Archive (/initiatives) should list initiatives in grid format.
7. Events Requirements
Use Events Calendar Pro:
- /events archive
- Month view + list view (native)
- Styled to match theme
- Single event template override
- Preserve schema + plugin features
8. Forms
Forms handled via forms plugin (likely Gravity Forms).
Required forms:
- Partner Join
- CityServe Volunteer
- Email Signup
Use Form Embed module for placement.
Ensure validation and clean markup.
9. Donations
Give page links externally to:
go.withinreach.com
No internal donation processing.
10. Navigation Structure
Primary Nav:
- What We Do (dropdown)
- Upcoming Events
- Partners
- Stories
- About
- Give
Keep hierarchy simple.
11. SEO & Performance
- Clean permalinks
- No duplicate CPTs
- No unnecessary queries
- Lazy load media
- Respect Events Calendar schema
- Keep theme lightweight
12. Priority Objectives
Design and build must prioritize:
- Story engagement
- Event registration
- Partner signups
- Donations
13. Non-Goals
Do NOT build:
- Member portal
- Dashboard
- Complex filtering systems
- Overengineered taxonomy structures
Keep architecture clean and scalable.