The Services Page specification folder is the primary source of truth for this initiative.
Requirements, decisions, implementation references, and task tracking should remain centralized and easily discoverable.
Contributors should consult:
- specification.md
- decisions.md
- references.md
- tasks.md
before beginning implementation work.
GitHub Issues and Pull Requests should reference these documents whenever applicable.
All Services Page development will occur within the services-dev branch.
The Services Page represents a large initiative involving multiple contributors.
Using a dedicated branch allows the team to:
- Reduce merge conflicts.
- Test functionality independently.
- Continue maintaining the production site through
main. - Deploy Services Page work to a dedicated Netlify staging environment.
Remove custom intake form fields from the Hero section.
Calendly already collects the required information.
Maintaining both a custom form and Calendly introduces duplicate data entry and unnecessary friction.
Replace the form with a CTA that opens Calendly.
Do not implement the Testimonials section during the initial release.
The organization does not currently have enough completed client projects to support testimonials.
The section may be implemented after sufficient client feedback and case studies have been collected.
Pricing will be one of the final sections implemented.
The team requires additional time to conduct pricing research and validate assumptions before publishing pricing information.
The goal is to establish pricing that is:
- Affordable for small businesses.
- Competitive within the market.
- Sustainable for project delivery.
- Aligned with Web Dev Path's educational mission.
Pricing cards may be built after pricing research is completed and approved.
The Services Page will be developed using a lightweight Specification-Driven Development approach.
The team wants to:
- Improve onboarding.
- Reduce ambiguity.
- Improve collaboration.
- Improve AI-assisted development workflows.
- Create experience with specification-based delivery practices.
The following documents act as the source of truth:
- specification.md
- decisions.md
- tasks.md
GitHub Issues and Pull Requests should reference these documents whenever applicable.
Services Page development will be validated through a dedicated Netlify staging environment connected to services-dev.
This allows the team to:
- Test independently of production.
- Validate functionality before merging.
- Review large features incrementally.
Production remains connected to main.
Services staging remains connected to services-dev.