- Dhruv SethCreator & Engineer
Nexus
A product & engineering workspace — from a single task to the release it ships in.
- Role
- Creator & Engineer
- Status
- In progress
- Stack
React
TypeScript
Vite
React RouterZustand
TanStack Query
Tailwind CSSRechartsReact Flow
Framer Motion
- Links
- Private
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.
- Frontend
- React 18 · TypeScript
- State
- Zustand + TanStack Query
- Architecture
- API-first
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.
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.
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
An npx CLI that Dockerizes a Node.js app in one command.