Sayara
Auto-parts marketplace for Kurdish-speaking users, rebuilt with a CMS
- Role
- Frontend Developer (Intern)
- Status
- Live
- Year
- 2025
- Duration
- 2 Months (September – November 2025)
- Stack
- Next.js
- Sanity CMS
- Tailwind CSS
- React
- Skills
- Frontend Architecture
- Headless CMS Integration
- Performance Optimization
- Version Control (Git)
- Links
- Live demo
Results
46 → 81
Lighthouse Performance
Problem
The original platform's landing page was completely hardcoded, making content updates difficult for the marketing team and resulting in a low Lighthouse performance score of 46.
What I built
- Architected a new file system and rebuilt the landing page from scratch using Next.js and Tailwind CSS.
- Integrated Sanity as a Headless CMS to allow the marketing team to dynamically update content without developer intervention.
- Documented Git history thoroughly to ensure clean handoffs and structured team collaboration.
Key decisions
Headless CMS over Supabase
Why
Chose a Headless CMS (Sanity) specifically because the immediate need was structured content management for marketing, not a relational database for user application state.
Trade-off
Sanity excels at marketing content but isn't meant for complex backend user authentication, which was perfectly acceptable given the scope of the landing page.
Technical notes
Significant Lighthouse Boost
By replacing the heavy legacy codebase with an optimized Next.js architecture leveraging static generation, the performance score jumped from 46 to 81.
What I would do next
This internship provided real-world experience in replacing hardcoded legacy systems with maintainable modern architecture, heavily utilizing a Headless CMS and improving rendering performance.
Need something like this?
Available for full-time frontend/full-stack engineering positions, contract roles, and impactful civic tech initiatives.