This website — the Chimbuk platform

The build

We practice on ourselves first. The content layer is typed and adapter-based so the same UI will swap from local data to Firestore without a rebuild; the admin that manages it will be the exact tooling we sell to clients.

What we handled

• Design system built from scratch for a new identity — no template
• Every page: own metadata, canonical, OG cards, JSON-LD
• Offline-first PWA shell with a network-aware strategy
• Accessibility and motion discipline checked at build time

Why rebuild on ourselves first

The old site had the failure mode we sell against: generic brochure copy, no data layer, no way for the owner to edit anything, and SEO left to whatever the template shipped with. Rebuilding it was both dogfooding and proof — if the “typed data → static page → per-page schema” pattern cannot carry our own story, we have no business pitching it to anyone else.

There is also a trust calculation. A client evaluating a platform rebuild can inspect the thing itself: open any page, watch the single script chunk load, view the JSON-LD, run Lighthouse, resize to 320px. The marketing is the product demo, which is the only kind of marketing we want to make.

A content layer before a content policy

Everything rendered here comes from typed sources — services, projects, technologies, concepts, FAQ — behind one accessor boundary. Pages never import raw data; they go through the content contract, which is where filtering (published + owner-approved) and the future Firestore adapter hook in. Swapping the source changes one file, not forty pages.

The typing carries a policy: a project entry physically has fields for proof status and case-study state, so the UI can render “verified ledger” versus “Concept Lab” honestly. Fake states are not possible to express, which is the point — we design databases the way we want businesses to have to tell the truth.

Static where it counts, animated where it sells

The whole site generates at build (75 pages in ~2 seconds) and revalidates hourly; there is no server render path to fall over. Motion is CSS-first — scroll reveals, the auto-advancing screenshot carousels on product pages, hover states — with exactly the client islands that need to exist: header dropdowns, ⌘K search, the assistant dock, the gallery, the form. Reveal-on-scroll uses one shared IntersectionObserver; reduced-motion users get the same content with none of the movement.

Theming is token-level: the same site renders in dark and light through a single attribute and a pre-paint script, and the print stylesheet is real. Device mockups — the phone and tablet frames on the Concept Lab — are painted with CSS, not images: no alt-text lies about screenshots, no image budget spent on chrome.

The SEO program, not the SEO plugin

Every page owns its metadata: title sized to the SERP, one canonical, per-page OG cards generated on demand, JSON-LD matched to content type (Service, Article, FAQPage, MobileApplication with screenshots, Breadcrumb). The sitemap and robots generate from the same typed content as the pages, so nothing indexable can drift unlisted. Structured data even includes the Google Play listings themselves — app icon, screenshots, install URL — tying the store presence to this domain.

The long tail is engineered too: 26 technology pages and a per-project decision story exist to answer questions people actually type, each interlinked with three or more edges. What we do not do: doorway pages, fabricated review markup, or schema claiming ratings we have not earned.

Ship states, not vibes

Contact delivery today is an honest interim: the composer validates locally and routes through your own mail client straight to the studio — real intake with Firebase Firestore + notification lands in the backend phase, and the form's schema already reserves the fields that phase needs. Project screenshots on store pages are live listing pixels from Google's CDN until deploy-time mirroring; studio renders are labelled as renders. The backlog is a public document.

That shipped-versus-claimed discipline is the actual deliverable of this project. A client platform that can state its own status honestly is one that will survive audits, staff changes and bad quarters.