42 lines
1.6 KiB
Markdown
42 lines
1.6 KiB
Markdown
# Holiday Property Booking Project
|
|
|
|
## Project Classification
|
|
|
|
Public holiday property booking website with a booking engine, admin management, and transactional notifications.
|
|
|
|
## Status
|
|
|
|
Phase 1 scaffold started from the approved planning docs, and the Vikunja board is now onboarded.
|
|
|
|
## Stack
|
|
|
|
- Next.js
|
|
- TypeScript
|
|
- Bootstrap 5
|
|
- Sass
|
|
- PostgreSQL
|
|
- Prisma
|
|
- Stripe Checkout
|
|
- Session-based admin auth
|
|
|
|
## Current Build Scope
|
|
|
|
- Repo scaffold
|
|
- App shell
|
|
- Base styling
|
|
- Prisma schema
|
|
- Health endpoint
|
|
- Environment ports aligned to `7003`, `6003`, and `5003` for dev, QA, and production
|
|
- Container and host ports match for each environment
|
|
- Playwright browser test harness for dev and QA
|
|
- Vikunja board normalized to the playbook lane model
|
|
- The first build tickets are queued on the board, with later phase work staged behind them
|
|
- Post-dev flow is documented so implementation tickets always merge to `develop`, then hand off into test/validation before QA promotion
|
|
- New functionality should extend the Playwright suite so browser regression coverage grows with the app
|
|
- Operating cadence is documented so Neo takes the top `Ready for Dev` ticket every hour, posts a completion summary to Discord when done, Morpheus reviews the lanes every hour, and the queue is refilled before it drops below 5 unworked tickets
|
|
|
|
## Next Build Step
|
|
|
|
- Start with `VIK-108`, then work through `VIK-109` to `VIK-112` in order before pulling from the backlog queue.
|
|
- Once fewer than 5 tickets remain unworked, create the next batch from the next unresolved phase instead of letting the queue drain.
|