I build websites where design direction, content needs, and practical implementation have to work together.
I’m a developer based in Bandung, Indonesia. I work at Forest Interactive as a Senior WordPress Developer & Frontend Engineer and currently take on freelance website work with brands and creative teams.
My work follows two paths: Custom WordPress Development when content workflows or custom functionality lead, and Marketing Website Development when the visitor-facing message and experience lead.
My current work combines a corporate technology role with freelance website work, giving each brief a practical implementation context.
Since 2020, I have designed and developed custom WordPress themes, plugins, and integrations for internal and client marketing websites at Forest Interactive. I also contribute to and maintain React-based applications and am working on a migration from Webflow to Astro, with Sanity replacing Webflow CMS.
Since 2025, I have partnered with brands and creative teams on custom WordPress development, marketing websites, and selected front-end work. I translate approved Figma direction into responsive interfaces with close design fidelity and purposeful interaction, shaped around each project's content, design direction, and goals.
These are working priorities rather than promises about a project’s outcome. The brief and its constraints still lead the decisions.
Type, spacing, components, responsive states, and interaction states all matter when an approved visual direction becomes a working interface.
Content structures and technical choices should stay connected to how a team will create, edit, and maintain the website.
I consider real content, layout changes, type, media, and interaction across the screen sizes the project needs to support.
Semantic markup, keyboard paths, readable contrast, and useful focus states belong in the implementation rather than as a late checklist.
Motion can help explain content or guide a journey. I consider its role, supported devices, and reduced-motion behavior together.
Assets, markup, and front-end decisions stay focused so the technical foundation remains practical for the project and its visitors.
WordPress, Sanity, Astro, React, and GSAP are implementation tools within the two website offers, not standalone services. The project’s editing, integration, responsive, and interaction needs guide the choice.
WordPress, PHP, ACF, and Gutenberg support custom builds and familiar editing workflows, while Sanity supports structured content for headless websites.
Astro, React, TypeScript, HTML, CSS, and Tailwind CSS help carry an approved visual direction into real content, screen sizes, and browser states.
GSAP, ScrollTrigger, LottieFiles, SVG, and CSS animation can support explanation or guidance when motion belongs in the experience.
Start with the service path that matches the brief, then follow the public examples that help you understand the implementation context.
For websites where content editing, custom functionality, integrations, or an existing WordPress setup needs to lead.
Explore WordPress developmentFor websites where a brand, campaign, product, or service needs a clear, responsive visitor experience.
Explore marketing websitesReview public client website, open-source plugin, and database tool examples on the selected work page.
Review selected workAn open-source WordPress plugin for mobile engagement, with a sticky floating button for calls, messaging, and booking.
View ButtonFlowA public custom WordPress website based on an approved Figma direction, with responsive implementation and purposeful GSAP and LottieFiles interaction.
Read case studyAn AI-generated product prototype reframed as a specification for a maintainable WordPress and React rebuild.
Read case studyAn anonymous Webflow and Webflow CMS migration to Astro and Sanity where measurement corrected assumptions about content, rendering, and verification.
Read case studyShare your goals, current site, design direction, content workflow, or project constraints. The contact page is the place to outline the context and start a practical conversation about the right website path.
Go to contact