Manchester |26-ITP-May| SamreenAmjad |Sprint 1 | Form-Controls

[serveyano]

Learners, PR Template

Self checklist

I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
My changes meet the requirements of the task
I have tested my changes
My changes follow the style guide

Changelist

This PR creates a T-shirt order form using semantic HTML. It collects the user’s name, email, colour, and size.

[netlify]

✅ Deploy Preview for cyf-onboarding-module ready!

Name	Link
🔨 Latest commit	c44123d
🔍 Latest deploy log	https://app.netlify.com/projects/cyf-onboarding-module/deploys/6a1ca2fbf8aca0000839fe20
😎 Deploy Preview	https://deploy-preview-1336--cyf-onboarding-module.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	2 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 86 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

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

[Luro91]

How can you get all lighthouse scores to 100?

[serveyano]

Changes made

[Luro91]

How can you achieve a lighthouse score of 100 for SEO as well?

A note on commit messages. It's hard to know for me what happens in a commit if the message is not descriptive. A commit should describe what changed in the code. It's also good practice to split commits into logical blocks (for example for each task or each review comment). This makes it easier to understand and additionally the commits could also be undone more easily if needed.
I like this article about commit messages: https://chris.beams.io/git-commit