Updating SDD docs to include new Service page issues

[mariana-caldas]

Web Dev Path

Have you updated the CHANGELOG.md file? If not, please do it.

Yes.

What is this change?

This PR continues the adoption of our Specification-Driven Development (SDD) workflow for the Services Page.

Instead of duplicating implementation details across the repository, the SDD documents define the product requirements, decisions, and supporting references, while GitHub Issues become the execution layer for individual implementation tasks.

This PR includes:

• Updated tasks.md to reference GitHub Issues instead of maintaining duplicated implementation checklists.
• Updated references.md with the latest design documentation and supporting resources.
• Added the first implementation issue for the Services Page:
  • Create Services page Hero section #308 – Create Services page Hero section
• Updated the CHANGELOG.md.

The remaining Services Page sections will follow the same approach as new implementation issues are created.

---

Were there any complications while making this change?

No technical complications.

This PR intentionally simplifies the relationship between the SDD documentation and GitHub Issues to avoid maintaining the same implementation details in multiple places.

The workflow may evolve as the team gains experience using it, and small improvements can be incorporated based on contributor feedback.

---

How to use this workflow

For every Services Page implementation task:

1. Review the SDD documentation:
   • specification.md
   • decisions.md
   • references.md
2. Open the corresponding GitHub Issue linked from tasks.md.
3. Use the issue as the implementation guide.
4. Reference the issue in your Pull Request.
5. Update the issue status when appropriate.

The SDD documents remain the source of truth for requirements, decisions, and supporting references, while GitHub Issues manage implementation work and technical discussion.

---

How to test

No application functionality was modified.

Review the documentation changes to verify that:

• tasks.md correctly references the implementation issue.
• references.md includes the latest supporting documentation.
• Issue Create Services page Hero section #308 references the appropriate SDD documents.
• The workflow is clear and easy to follow for future contributors.

---

When should this be merged?

After confirming that the proposed Specification-Driven Development workflow supports future Services Page implementation and that the updated documentation accurately reflects the intended development process.

[netlify]

✅ Deploy Preview for services-dev-webdevpath ready!

Name	Link
🔨 Latest commit	bc22fbc
🔍 Latest deploy log	https://app.netlify.com/projects/services-dev-webdevpath/deploys/6a5bebfa967cb7000869a121
😎 Deploy Preview	https://deploy-preview-309--services-dev-webdevpath.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mariana-caldas]

Hi team! As soon as you approve this approach, I'll add the other issues to our task.md file and to this PR. The goal is to merge this PR with all our issues for the project added to our dashboard -> Web Dev Path platform - Development team

That means that if we decide to add more issues or change anything in terms of our SDD architecture after merging this PR, our PM's (or myself) will open a new one so that we keep our specs as the project source of truth, which means where you are finding all the info you and your AI models need to code.

Over to you, @cherylli and @dami-boy ;)

[cherylli]

thanks. Looks good!

[oluwatobiss]

LGTM. Thanks.

[Satoshi-Sh]

Looks good to me too.