Dhruv Seth — PortfolioSheet 01/01—X 0000 · Y 00000Rev b4dbfbaScale 1:1
dhruvseth.in
  • Home
  • Projects
dhruvseth.in

© 2026 Dhruv Seth · India · Remote

HomeProjectsEmailLinkedIn ↗
Index/Projects/Nexus
Case study2026

NexusNexus

A product & engineering workspace — from a single task to the release it ships in.

Role
Creator & Engineer
Status
In progress
Stack
React logoReactTypeScript logoTypeScriptVite logoViteReact Router logoReact RouterZZustandTanStack Query logoTanStack QueryTailwind CSS logoTailwind CSSRRechartsRReact FlowFramer Motion logoFramer Motion
Links
Private
01 · Interface02 · Client state03 · Data layerDashboard & inboxIssues & KanbanPlanningAnalyticsZustand storesTanStack QueryWorkspace dataAPI layerLocal persistence
Fig. 01 — System overviewSwipe to explore →
Summary

Nexus brings issue tracking, delivery planning, team coordination, documentation and progress reporting into one connected app. It's built so you can move from a single task to the project, cycle, release, goal and dependencies that give the work its context.

Measured
Frontend
React 18 · TypeScript
State
Zustand + TanStack Query
Architecture
API-first
Contents
  1. 01The problem
  2. 02What it does
  3. 03How the data flows
  4. 04Product quality
  5. 05Status

Nexus

Nexus is a project-management workspace for product and engineering teams. It connects issue tracking, delivery planning, team coordination, documentation and progress reporting, so you can move from a single task to the project, cycle, release, goal and dependencies that give the work its context.

The problem

Work context gets scattered: the task lives in one tool, the roadmap in another, decisions in a doc, and nobody can see what's blocking the release. Nexus keeps the work and its context in one place — every issue knows which project, cycle, release and goal it belongs to, and what it's blocked by.

What it does

  • A personal home — active tasks, blockers, reviews, deadlines, project health, upcoming releases and goal progress at a glance; My Work splits your work into focused, active, planned, blocked, in-review and done.
  • An inbox — filter notifications, mark read, archive, and jump straight to the task or project.
  • Issues, properly — list and Kanban views; filter, group, sort, search, reorder and bulk-update. Each issue has subtasks, comments with reactions, attachments, activity history, watchers, review status, labels, estimates, due dates, and relations: blocks, duplicates, related.
  • Planning and delivery — projects, cycles, initiatives, roadmaps, goals and releases, with cycle burndown, release-readiness review, and project health (on track, at risk, off track).
  • Team context — teams and members, documents and decisions, customer feedback and sentiment, and portfolio risks kept next to the work they affect.
  • Analytics — throughput, cycle time, delivery progress, quality signals and review state, plus an interactive dependency graph that surfaces blocked work and delivery risk.
  • Fast to drive — global search, a command palette and keyboard shortcuts.
  • Yours to shape — light, dark and system themes, reduced motion, workspace switching, notification preferences, and workspace-level teams, workflow, labels, statuses and cycles. Export the workspace as JSON, or reset it to the demo.

How the data flows

The frontend is built API-first: every screen reads through the same data layer it will use against a production backend.

01
Load
Workspace data loaded on startup
02
Stores
Zustand is the client-side source of truth
03
UI
Components render from the stores
04
Update
Edits apply instantly and log activity
05
Persist
Saved to localStorage, survives refresh
Fig. — Today

TanStack Query sits between resource pages and a pluggable transport layer with configurable latency and failure modes, so loading, retry, empty and error states are exercised exactly as they would be in production.

01
Database
Real persistence
02
Backend API
Plugs into the transport layer
03
TanStack Query
Same caching, retry and loading
04
Zustand
Same client state
05
UI
Largely unchanged
Fig. — With a backend: swap the transport, keep the app

Product quality

The details that make it feel finished: loading skeletons, empty states, error states with retry, toast feedback, confirmation flows, responsive navigation, and motion that respects reduced-motion preferences.

Status

The frontend is feature-complete across every workspace area. Next up: a production backend, authentication and real-time collaboration — plugged in through the existing data layer.

Built with

  • Dhruv Seth
    Dhruv Seth
    Creator & Engineer
    LinkedIn ↗
Next sheet→
docker-frame-tooldocker-frame-tool

An npx CLI that Dockerizes a Node.js app in one command.