BuildZnDiscuss your workflow
← All work

Public build · Technical case study

BuildZn web platform

The working studio site: structured service pages, reviewed content, interactive previews and a tested deployment workflow.

Next.js / ReactPlaywright / axeVercel

PUBLIC IMPLEMENTATION / SOURCE WALKTHROUGH

BuildZn web platform

Live website, working previews and automated browser checks for core flows, mobile layout and accessibility.

  1. 01

    Define service and portfolio content in shared records

    Input and entry point

  2. 02

    Keep draft and quarantined articles out of public pages and the sitemap

    Implementation stage

  3. 03

    Exercise review gates, downloads and contact-response states in browser tests

    Implementation stage

  4. 04

    Run accessibility and mobile-layout checks before deployment

    Output and operational boundary

IMPLEMENTATION EXCERPT / lib/posts.ts

if (data.status !== 'published' || data.reviewed !== true) return null;

const date = String(data.date || '');
if (!date || Number.isNaN(Date.parse(date))) return null;

Selected implementation lines with explanatory comments. Omitted work is marked with “…”. Inspect the complete source below.

Evidence boundary

An accepted form response proves provider acceptance, not inbox delivery. Public copy and tests keep that distinction visible.

THE PROBLEM

Where the work gets stuck.

A service website needs to explain scope, show credible evidence and keep drafts or outdated claims out of public search results.

Follow the implementation

  1. Define service and portfolio content in shared records
  2. Keep draft and quarantined articles out of public pages and the sitemap
  3. Exercise review gates, downloads and contact-response states in browser tests
  4. Run accessibility and mobile-layout checks before deployment

Technical scope

Next.js App Router site with shared service and project data, reviewed-only article loading, canonical metadata, sitemap generation, redirects and browser-tested sample workflows.

The decision that matters

An accepted form response proves provider acceptance, not inbox delivery. Public copy and tests keep that distinction visible.

Inspect the evidence

Public source reviewed October 1, 2026. Pinned implementation links preserve the version reviewed. This walkthrough does not reproduce private client details.

Have a similar repetitive task?

Share the input, the tools and the decision that should stay with a person.

Discuss your workflow ↗