Holiday Property Booking Website

Planning workspace for the new project based on the functional specification.

Current Status

Phase 1 scaffold has started. The repo now contains the Next.js app shell, Prisma schema, Docker entrypoint, and baseline project docs. Environment ports are mapped to 7003 for Dev, 6003 for QA, and 5003 for Production. The browser test harness is now being added as a separate action that targets Dev and QA only. The project has been onboarded to Vikunja and the board now uses the playbook lane model. The next public work is queued as tickets, with VIK-112 staged as the next active item after the current slice. Implementation tickets are expected to merge back to develop first, then hand off into Ready for Test / Deploying to Dev before Trinity validation and later QA promotion. Any new feature work should also update the Playwright suite so the browser tests become the main regression check as coverage expands. Operating cadence is now defined in 09-operating-cadence-and-batch-plan.md: Neo pulls the top Ready for Dev ticket every hour, posts a completion summary to Discord when finished, Morpheus reviews the lanes every hour, and the ready queue is replenished when fewer than 5 tickets remain unworked.

Working Rule

We will not build this in one shot. Each numbered document in this folder defines one stage of work and must be reviewed before the next stage starts.

Document Order

01-intake-and-scope.md
02-content-architecture-and-data-model.md
03-public-website-and-search.md
04-booking-availability-and-pricing.md
05-payments-and-notifications.md
06-admin-console.md
07-seo-accessibility-performance.md
08-implementation-plan-and-launch-readiness.md
09-operating-cadence-and-batch-plan.md

Source

Functional specification:

holiday-property-booking-functional-spec_1---5c2d597d-4cbf-48fb-9c94-05c8fd719627.md

Review Gate

Nothing in the build should start until the relevant document in this sequence is approved.

2.0 KiB Raw Blame History