Design and build of our own studio site — AJAX page transitions, Lenis smooth scroll, a full dark/light system, and a Webflow CMS that runs the entire portfolio.
Dark/Light layout switcher
PeThemes is a digital studio building high-end websites and premium templates since 2013 — 7,000+ users worldwide, 5x featured on Envato Market.
Our own site is the hardest brief we take. It's the one project where the work is the pitch: if we build websites for a living, the site selling that has to be the best-executed thing in the portfolio. No client to blame, no budget to hide behind.
So we built it the way we'd build for a client with no ceiling.
The site never does a full reload. Click anything and content transitions out and in while the shell, the scroll engine, and the theme state persist. No white flash, no re-initialization, no losing your place.
That's the invisible engineering: every page-specific animation has to tear down and rebuild cleanly on each navigation, or you get memory leaks, stacked scroll listeners, and animations that fire twice. Getting it seamless is a lot of work that, done right, nobody ever notices.
Project Page
Lenis smooth scroll
The whole site runs on Lenis, so scroll has weight and inertia instead of the native step. Everything scroll-driven is synced to it — the featured works sequence, section reveals, progress counters — which means motion stays smooth rather than fighting the browser's scroll timing.
Scroll is the primary interaction on a portfolio site. It should feel like something.
Dark / light switcher
Not a filter — a full second design. Both themes are properly art-directed: contrast, image treatment, the blue accent, and every interaction state tuned separately. The choice persists across navigation, and because of AJAX transitions it survives page changes without a flicker.
About Page
Webflow CMS running the portfolio
Every project — 28 and counting — is a CMS item. Thumbnails, frameworks, client/platform, year, scope of work, main features, live link: all structured fields.
That means the featured works sequence on the homepage, the works archive, and every project detail page are generated from one source. Adding a project is filling a form, not rebuilding a page. Sounds boring. It's the reason the site is still current.
Service Layer
Inner-page interactions
The detail is where the site earns its positioning:
Featured works — a sticky-column sequence where the right-hand meta (frameworks, client/platform, year) scrambles and re-decodes as each project comes into view, with a live index counter
Project pages — sticky info column against a scrolling visual stack, with a live scroll-progress percentage
Services — numbered chapters, each with its own isometric line illustration
About — a pinned manifesto with a dotted orbit motion, a timeline that reveals on scroll, and a light section that inverts the whole page mid-scroll
Contact — split layout with two office cards running live local clocks for Ankara and Dubai, plus a structured brief form (service, timeline, budget) instead of a blank message box
Throughout: custom cursor, page loader, and hover states on everything that moves
Contact Page
WHAT I DID
Art direction, UI design, full Webflow build, CMS architecture, AJAX transition layer, Lenis scroll integration, dark/light theming system, all custom interactions, multi-language setup (EN/TR/AR), responsive, performance pass.
Webflow studio site where every projects ships as a CMS entry, not a new page. Design system in Figma, GSAP motion, and it's our main portfolio website.