The operational problem
The agency needed its public website to show the creative work itself, organize several service paths, and support ongoing search and content operations.
A responsive, video-led public company website that makes real client work, services, case studies, and content visible.
Why this system exists
Real footage and client examples are more credible than abstract agency claims. The site treats media as the product while the content system supports discoverability and maintenance.
Ayub is listed publicly as Website Developer. Creative production and campaign outcomes belong to the wider Que Media team.
How the work moves
- Organize proof
- Build responsive media surfaces
- Publish services and cases
- Run audits
- Validate routes and metadata
- Deploy and monitor
What shaped the solution
Creative production and campaign outcomes belong to the wider Que Media team.
Agency performance metrics are not attributed to Ayub without separate evidence.
What I owned
Designed
Public information architecture and visual proof surfaces with the agency team
Developed
Next.js routes, components, responsive media, and content templates
Integrated
Contact delivery, public-media pipeline, analytics, and SEO sources
Operated
Audits, publishing, validation, deployment, and ongoing maintenance
Collaborated
Que Media creative, production, strategy, and client teams
Decisions that carried the work
Let the work lead
Real campaign footage and public client examples carry more credibility than abstract agency claims.
Verified outcome
Live public website with real client video and case-study surfaces.
Responsive Work, Case Studies, Services, Blog, About, and Contact routes.
Active September 2026 content and SEO changes.
What I will not overclaim
Ayub is publicly listed as Website Developer. Agency view counts, testimonials, and campaign outcomes are not repeated as his personal impact.
Verified from the current repository, public site, commit history, and public team page.