Board review · Updated 5 August 2026
Review progress, current work, and launch gates.
The development build is ready to put in front of reviewers, but it is not approved for public launch. This page separates completed foundations from the service validation, deployment, migration, and operational work still ahead.
Overall status · Amber
Board review deployment and service validation
Review-ready
The board-review site is live with public content loading securely. The current priority is collecting review feedback and validating authenticated member, registration, and form workflows before launch work continues.
Groups
3
Tracking sections in this page.
Checked off
11/16
Items already complete.
Current phase
Phase 5
Active project window.
Validation
Lint + build
Workspace checks are passing.
Progress checks
Completed and remaining work
Checked items are implemented in the current workspace. Pending items still require delivery or live verification.
Public experience and content
Implemented public journeys and browser-safe content delivery
4/5
Public website is implemented
Responsive public, resource, event, and member-facing routes are in place.
Done
Content services stay behind the application server
Narrow application endpoints keep service addresses, credentials, and private fields out of browser code.
Done
Partners, supporters, and business directory are live-data ready
The public views use dedicated content read models and membership-aware directory records.
Done
Shared navigation and footer are centrally managed
The current delivery batch adds managed records for global navigation and footer content.
Done
Local content environment is healthy
Blocked: the local environment configuration currently fails validation and cannot start.
Pending
Membership and events
Implemented account foundation and current event-service work
4/6
Signup and existing-member account claim are implemented
The account service coordinates sign-in account creation with the matching member record.
Done
Member profile self-service is implemented
Authenticated members can read and update profile and membership choices through verified server endpoints.
Done
Account guidance and password recovery are implemented
The login flow routes existing, claimable, and new-member emails to the appropriate next step.
Done
Event sessions, registration, and online meeting access are service-validated
Pending: these workflows are in the current delivery batch and still need end-to-end validation against the live services.
Pending
Atomic event capacity and waitlisting are implemented
Concurrent seat assignment, first-in-first-out promotion, and distinct waitlist and confirmation emails are implemented; live end-to-end validation remains.
Done
Production payments and remaining communications automation are complete
Pending: production payment validation and downstream event operations are not complete.
Pending
Review and launch readiness
Build health, deployment, and remaining approval gates
3/5
Code-quality and production build checks pass
The current workspace passes the automated code-quality and production build checks.
Done
Production packaging is prepared
The production package runs the generated application server and excludes local environment secrets.
Done
Broad-review deployment is live and smoke-tested
The hosting service is serving the application over HTTPS, and the public routes and content endpoints pass external smoke tests.
Done
Review baseline is committed
Pending: the current functional delivery batch is still uncommitted.
Pending
Migration, accessibility, and operating documentation are complete
Pending: these remain formal public-launch gates after broad review.
Pending
Broad review
Deployment readiness
The application will use the existing hosting account rather than requiring a new billing profile.
Production runtime and package
The repository includes a production-ready application package.
Ready
Hosting access and deployment package
The review package is stored securely and runs in the designated Canadian region.
Ready
Runtime configuration
Public content reads are active. Authenticated and write credentials remain omitted pending workflow validation.
Ready
Reviewer access and smoke test
The public site and content services pass external checks. Confirm whether reviewers beyond @cofsab.ca should receive access.
Board action
Roadmap
Timeline sequence
The phases track the project from setup through launch readiness.
Phase 1
Project Setup
Complete
Initialize the project structure, application shell, local development flow, and board preview path.
Website project scaffolded
Local MacBook development path documented
Containerized review path documented
Project structure and conventions defined
Development environment prepared
Preview access outlined
Phase 2
Information Architecture
Complete
Shape the site navigation, status page layout, and reusable content sections.
Main navigation defined
Status page mounted as a core route
Homepage and subpage route map prepared
Reusable tracker sections created
Phase 3
Frontend Development
Implemented
Build the public interface and member-facing layouts with responsive, accessible patterns that can be reviewed in the preview environment.
Responsive layout system implemented
Public content sections created
Member-facing sections prepared
Core UI states handled
Phase 4
CMS Integration
Implemented
Connect public pages and shared site content to narrow server-side read models without exposing private credentials to the browser.
Content models mapped
SSR CMS integration established
Resources, events, partners, and directory content wired up
CMS-managed navigation and footer prepared
Editorial workflows documented
Phase 5
Membership and Events
Current
Validate member account access, profile self-service, event sessions, registration, and member-only online meeting access against the live services.
Membership signup, account claim, and password recovery
Member profile and membership self-service
Event sessions, video, registration, and online meeting access
Production membership renewal and payment workflow
Atomic event capacity, waitlisting, payment, and communications workflow
Phase 6
Accessibility and Launch Prep
Next
Finish migration, accessibility, and documentation before launch while keeping board preview routes intact.
Accessibility checks completed
Legacy content migration completed
Volunteer documentation written
Launch review checklist completed
Milestones
Checkpoint trail
Milestones highlight the next visible outcomes in sequence, not just the final launch.
Public site and information architecture implemented
Responsive public journeys, navigation, resources, events, partners, the business directory, member-facing layouts, and board status views are implemented in the repository.
Complete
Frontend
Browser-safe content delivery implemented
Public content is delivered through narrow application endpoints, keeping service addresses, credentials, and private operational fields on the server.
Complete
Content
Membership and event service validation
Signup, account claim, password recovery, profile self-service, event registration, and protected online meeting access are implemented or in the current delivery batch and require live end-to-end validation.
Current
Membership + Events
Board-review deployment
The review application is live with managed HTTPS, health rollback, scaling, logging, and verified public content reads.
Complete
Deployment
Public launch approval
Accessibility review, data migration, payments, communications automation, operational documentation, and production infrastructure remain before launch.
Next
Board + Operations
Validation
Current build health
These checks are useful for board and internal review because they verify the app still builds cleanly.
Lint passed
The current workspace passes automated code-quality checks.
Production build passed
The production build completed successfully.
Production package configured
The production package runs the application server, excludes local environment files, and passes local route and content-service smoke tests.
Operational verification pending
Authenticated member, registration, form-write, payment, and event-operation workflows still require live verification.