Editorial home & work
Hero narrative, selected work, services framing, and FAQ.
NeedFirst impression must feel premium and intentional.
ValueBetter-qualified conversations.
ProjectsCase Study

Zohaib Nawaz Dev is a personal portfolio website—not a SaaS console. It presents work, services, pricing, and story so prospective clients can evaluate fit and start a conversation.
The craft layer is the story: Serwist PWA with offline fallbacks, a multi-axis theme customizer, GSAP/Lenis motion, and a Gemini chatbot that answers common questions before a call.
Share Studio, Hire, leads, and approvals live in ZN CMS. This case study focuses on the public brand experience only.
A static portfolio for credibility—fast to ship, easy to forget: weak theme control, no offline story, generic motion, and no in-page way to answer recurring prospect questions.
Premium clients judge the whole system. A portfolio that feels intentional, fast, and installable signals the same craft expected on their product work.
Zohaib Nawaz Dev treats the public site as a showcase product:
Home, work, projects, services, pricing, about, and contact—clear narrative and next steps.
Serwist service worker with offline fallback; theme customizer for mode, accent, font, and radius.
Lenis smooth scroll and GSAP transitions that create hierarchy—not noise.
Portfolio-aware Gemini chat that answers common questions before a discovery call.
Stronger first impressions, a site that feels engineered under real use, and better-prepared inquiries—while delivery ops stay in ZN CMS.
Hero narrative, selected work, services framing, and FAQ.
NeedFirst impression must feel premium and intentional.
ValueBetter-qualified conversations.
Clear engagement framing and commercial expectations.
NeedClients need scope and investment context early.
ValueShorter path from interest to inquiry.
Inquiry form and printable resume.
NeedProfessional close for serious prospects.
ValueLower friction to start a project discussion.
Service worker with precached marketing paths and an offline page; APIs stay NetworkOnly.
NeedReturn visits and flaky networks should not empty the brand.
ValueInstallable, resilient portfolio experience.
Theme, accent, font, radius—floating panel and /customize studio.
NeedOne fixed palette is not how people browse.
ValueVisitors can make the site feel theirs while exploring.
Lenis scroll, GSAP transitions, and liquid image reveals.
NeedMotion should create hierarchy, not distraction.
ValueMemorable presence that still feels fast.
Gemini-powered Q&A grounded in portfolio context, with suggested prompts.
NeedCommon questions should not wait for office hours.
ValueBetter-prepared inquiries.
Visitor opens the portfolio
Reviews work, services, and pricing
Optional theme tune or chatbot questions
Sends a contact inquiry
Discovery conversation
Opens floating customizer or /customize
Tries theme, accent, font, and radius
Continues reading work with a tuned look
Serwist precaches marketing routes and serves /offline; API and sensitive paths stay NetworkOnly so the worker never caches private traffic.
Business valueThe brand feels installable on return visits without trapping mutating requests.
A cookie-booted theme script applies mode, accent, font, and radius early; the customizer and /customize studio write the same preferences.
Business valueVisitors see a tuned look without a flash of the wrong theme.
Lenis scroll and GSAP page transitions are coordinated with App Router navigation so motion supports hierarchy instead of fighting the layout.
Business valuePresence that still reads as fast and intentional.
Gemini answers from curated portfolio context and suggested prompts—not an open-ended generic assistant.
Business valueProspects arrive to a call with clearer questions already answered.
| Challenge | Solution |
|---|---|
| A service worker that caches too broadly will trap API calls and make a “premium” portfolio feel broken after install. | Selective Serwist precache for marketing routes only, NetworkOnly for APIs, plus an offline fallback page. |
| Multi-axis theming flashes the wrong skin if preferences load after React paints. | Cookie-booted theme script on first load, with the floating customizer and /customize studio writing the same cookie-backed prefs. |
| GSAP and smooth-scroll libraries easily fight App Router navigations and tank mobile performance. | A deliberate motion system—page transitions and reveals tied to hierarchy, not decorative noise on every element. |
Recommended capture order for the case-study gallery.
A portfolio wins serious work when craft is visible on the public site—and private ops tools stay out of the hero narrative.
PWA rules are a product decision: cache the brand shell, never the request paths that must stay live.
Splitting showcase (this site) from ops (ZN CMS) keeps both stories honest and easier to evolve.
| Priority | Improvement | Business value |
|---|---|---|
| High | Richer journals publishing pipeline | Ongoing thought leadership without a separate blog stack. |
| Medium | Deeper Lighthouse / Core Web Vitals budgets in CI | Keep motion and PWA gains from regressing. |
Zohaib Nawaz Dev is a live personal portfolio—editorial storytelling, PWA polish, theme control, motion, and an AI chatbot. If you want a showcase that feels engineered, start with a discovery call.
Start a conversationFull Stack Product Engineer
Personal brand site
2026
Solo build
Next Project
Ask about projects, skills, or how to hire.