SDD Services dev -> Main

CHANGELOG.md

@@ -232,6 +232,9 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ### Added
 
+- Introduced SDD structure for Services Page
+- Updated SDD docs to include new Service page issues
+
 ### Fixed
 
 ### Changed

specs/services-page/decisions.md

@@ -0,0 +1,148 @@
+# Services Page Decisions
+
+## Source of Truth
+
+### Decision
+
+The Services Page specification folder is the primary source of truth for this initiative.
+
+### Reason
+
+Requirements, decisions, implementation references, and task tracking should remain centralized and easily discoverable.
+
+### Implementation
+
+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.
+
+## Branch Strategy
+
+### Decision
+
+All Services Page development will occur within the `services-dev` branch.
+
+### Reason
+
+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.
+
+---
+
+## Hero Section Form
+
+### Decision
+
+Remove custom intake form fields from the Hero section.
+
+### Reason
+
+Calendly already collects the required information.
+
+Maintaining both a custom form and Calendly introduces duplicate data entry and unnecessary friction.
+
+### Implementation
+
+Replace the form with a CTA that opens Calendly.
+
+---
+
+## Testimonials Section
+
+### Decision
+
+Do not implement the Testimonials section during the initial release.
+
+### Reason
+
+The organization does not currently have enough completed client projects to support testimonials.
+
+### Future State
+
+The section may be implemented after sufficient client feedback and case studies have been collected.
+
+---
+
+## Pricing Strategy
+
+### Decision
+
+Pricing will be one of the final sections implemented.
+
+### Reason
+
+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.
+
+### Implementation
+
+Pricing cards may be built after pricing research is completed and approved.
+
+---
+
+## Specification-Driven Development
+
+### Decision
+
+The Services Page will be developed using a lightweight Specification-Driven Development approach.
+
+### Reason
+
+The team wants to:
+
+- Improve onboarding.
+- Reduce ambiguity.
+- Improve collaboration.
+- Improve AI-assisted development workflows.
+- Create experience with specification-based delivery practices.
+
+### Implementation
+
+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.
+
+---
+
+## Netlify Environment Strategy
+
+### Decision
+
+Services Page development will be validated through a dedicated Netlify staging environment connected to `services-dev`.
+
+### Reason
+
+This allows the team to:
+
+- Test independently of production.
+- Validate functionality before merging.
+- Review large features incrementally.
+
+### Implementation
+
+Production remains connected to `main`.
+
+Services staging remains connected to `services-dev`.

specs/services-page/references.md

@@ -0,0 +1,132 @@
+# Services Page References
+
+## Design
+
+### Approved Mockups
+
+[Figma](https://www.figma.com/design/Fp0lLB5OWZLJseTs2svGbg/Web-Dev-Path_design?node-id=4813-12781&t=nFCiwC8KAHXakSmE-0)
+[Figma Prototypes: animations and behaviours](https://www.figma.com/proto/Fp0lLB5OWZLJseTs2svGbg/Web-Dev-Path_design?node-id=5354-12767&viewport=11375%2C-3827%2C0.23&t=fUPGkKi107ruYZK8-0&scaling=contain&content-scaling=fixed&starting-point-node-id=5354%3A12839&show-proto-sidebar=1)
+
+
+### Google Docs
+
+[Components' Study, Content, and Architecture](https://docs.google.com/document/d/15evnvS0T8jMhE_mlp1IyIOEhWWKH7eaDwoKVWrLG9PM/edit?usp=sharing)
+[Design System Doc](https://docs.google.com/document/d/16SaPlRJmAB6GCPcW4uo09owKVvkD0sgKm-BZzh0avEc/edit?usp=drive_link)
+
+
+### Design Notes
+
+- Testimonials section is deferred.
+- Hero form has been replaced by a Calendly CTA.
+- Mobile and desktop layouts should follow the approved Figma mockups.
+- Pricing values are pending research and team review.
+
+---
+
+## Environments
+
+### Production
+
+https://www.webdevpath.co
+
+Purpose:
+
+Current production website.
+
+### Services Development Staging
+
+[NETLIFY_STAGING](https://services-dev-webdevpath.netlify.app/)
+
+Purpose:
+
+Dedicated environment for Services Page development and testing coming from 
+the branch `services-dev`
+
+### Main Staging
+
+---
+
+## Integrations
+
+### Calendly
+
+[CALENDLY](https://calendly.com/marianacaldas/30-min)
+
+Purpose:
+
+Primary lead capture and discovery call booking flow.
+
+Notes:
+
+- Do not implement duplicate intake forms.
+- Calendly should remain the primary scheduling mechanism.
+
+---
+
+## GitHub
+
+### Repository
+
+https://github.com/Web-Dev-Path/web-dev-path
+
+### Services Page Specification
+
+/specs/services-page/specification.md
+
+### Services Page Decisions
+
+/specs/services-page/decisions.md
+
+### Services Page Tasks
+
+/specs/services-page/tasks.md
+
+### Services Page References
+
+/specs/services-page/references.md
+
+---
+
+## Related Issues
+
+Add Services Page GitHub Issues here as they are created.
+
+Example:
+
+- Hero Section
+- What We Offer Section
+- How It Works Section
+- Pricing Research
+- Pricing Section
+- Technology Stack Section
+
+---
+
+## Pricing Research
+
+Purpose:
+
+Provide supporting information for future pricing decisions.
+
+Future Resources:
+
+- Competitor research
+- Freelancer pricing research
+- Agency pricing research
+- Non-profit pricing considerations
+- Recommended pricing proposal
+
+---
+
+## Future Resources
+
+Reserved for:
+
+- Case studies
+- Client testimonials
+- Discovery call analytics
+- Conversion metrics
+- Additional design iterations
+- Service package documentation
+
+