All projects

Full stack / UI and UX

DesignHub Studio

A responsive website and project workspace for a fictional design studio. The public site has services, a filterable portfolio, six case studies, and a working inquiry form. The workspace has a dashboard, projects, clients, tasks, inquiries, team, and settings, with real create, edit, and delete.

React 19Vite 8Tailwind CSS 4React RouterZodExpress 5PostgreSQLPlaywrightaxe-core
Type
Website and workspace
Components
29 reusable
Tests
84 Playwright, 20 API
Accessibility
0 axe violations
DesignHub workspace dashboard

Overview

Two connected experiences on one data layer.

Inquiries sent from the public contact form appear in the workspace, and every dashboard number is computed from the data rather than typed in.

Public website

Home, services, a portfolio with working filters, six case studies, about, and a project-inquiry form.

Studio workspace

Dashboard, projects, clients, tasks as Kanban and table, inquiries, team, and settings.

Design system

A design system, not just styles.

One token file holds colour, type, spacing, radius, shadow, and motion. Tailwind's defaults are cleared, so components can only use tokens. All 29 reusable components are shown live on a /design-system page, and a Figma handoff document describes frames, variables, and per-screen specs.

Accessibility

Accessible by construction.

01

Dialogs and menus

Focus-trapped dialogs and WAI-ARIA menus and tabs.

02

Forms

Labelled controls and announced errors.

03

Not colour alone

Status never relies on colour, and reduced motion is respected.

04

Keyboard drag

Every drag-and-drop task move has a keyboard alternative through a status menu.

Responsive

Phones get their own compositions.

Verified with no horizontal overflow at 1440, 1280, 1024, 768, 390, and 375 px. On phones the layout switches to a navigation drawer, collapsible filters, bottom-sheet dialogs, and a two-up stat grid.

Data layer

One switch between a mock API and a real one.

A central API client talks to an in-browser mock REST API or to an Express and PostgreSQL backend, chosen by one environment variable. A shared folder holds the dataset, domain rules, and Zod schemas, so the frontend and backend always validate the same way.

Testing

Tests that found real defects.

84 Playwright testsDesktop, mobile, real API, responsive sweep, and axe scans in light and dark themes.
20 API testsnode:test and Supertest against the Express API.
16 defects fixedFound by the suites and listed in the testing report.
0 axe violationsOn every page, in both themes.

Scope and limits

Known limitations.

  • All companies, people, and projects are fictional. Emails use the reserved .example domain.
  • Workspace access is a client-side demo gate, clearly labelled, and not real authentication.
  • The PostgreSQL repository and Docker setup are implemented but were not run in the development environment.
  • Automated tests run in Chromium only, and no manual screen-reader testing has been done.

Screenshots

The site and workspace.

Next projectAI Customer Support Ticket Automation