Domus Digitalis Webapp
Project Summary
Project |
Domus Digitalis Webapp |
Priority |
P2 |
Status |
Active Development |
Location |
|
Started |
June 2025 |
URL |
localhost:3000 (local dev) |
Fullstack development learning project. Hands-on TypeScript/React practice building a project management and knowledge dashboard.
Architecture
domus-digitalis/
├── apps/
│ ├── frontend/ # Next.js 14 (port 3000)
│ │ ├── app/ # App Router pages
│ │ ├── components/ # React components
│ │ └── services/ # API client layer
│ └── backend/ # Express (port 8000)
│ ├── prisma/ # Schema + migrations
│ └── seed-data/ # JSON seed files
├── docker-compose.yml # PostgreSQL + Redis
└── .env # Environment config
Improvement Proposals
|
Proposals from ecosystem audit — 2026-04-04. For team review and prioritization. |
| Priority | Proposal | Rationale | Effort |
|---|---|---|---|
P1 |
Add API reference documentation |
Core webapp but no API surface documented. Internal and external consumers need endpoint contracts. |
L |
P1 |
Add database schema / data model documentation |
Data model drives everything. Undocumented schema means every developer reads migrations instead of docs. |
M |
P2 |
Deployment guide (local dev to production) |
3 pages and 8 partials exist but no deployment workflow. New contributors cannot stand up a dev environment. |
M |
P2 |
Architecture decision records (ADRs) |
Technical choices (framework, auth strategy, hosting) are undocumented. ADRs prevent relitigating decisions. |
M |
P3 |
User journey / feature roadmap |
Product direction is implicit. A visual roadmap aligns the team on what ships next. |
S |
Notes
Learning-first project. Focus is on understanding fullstack patterns (API routes, ORM, state management, component architecture) rather than shipping features quickly.