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.

Back to development Jump to roadmap

Overall status · Amber

Board review deployment and service validation

Review-ready

The SSR board-review site is live on AWS with public CMS content loading through HTTPS. The current priority is collecting review feedback and validating authenticated member, registration, and form workflows before launch work continues.

Groups

Tracking sections in this page.

Checked off

10/15

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 CMS

Implemented public journeys and browser-safe content delivery

4/5

Quasar SSR public site is implemented

Responsive public, resource, news, event, and member-facing routes are in place.

Done

CMS content stays behind the SSR server

Narrow application endpoints keep Strapi URLs, credentials, and private fields out of browser code.

Done

Partners, supporters, and business directory are live-data ready

The public views use dedicated CMS read models and membership-aware directory records.

Done

Shared navigation and footer are CMS-managed

The current delivery batch adds public CMS models for global navigation and footer content.

Done

Local Strapi container environment is healthy

Blocked: docker-compose.yml currently fails YAML validation and the local stack cannot start.

Pending

Membership and events

Implemented account foundation and current event-service work

3/5

Signup and existing-member account claim are implemented

The Lambda coordinates Cognito account creation with the matching Strapi 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 Zoom access are service-validated

Pending: these workflows are in the current delivery batch and still need end-to-end validation against Strapi and Cognito.

Pending

Payments, capacity, and communications automation are complete

Pending: production payment and downstream event operations are not complete.

Pending

Review and launch readiness

Build health, deployment, and remaining approval gates

3/5

Lint and production SSR build pass

The current workspace passes the code-quality and production SSR build checks.

Done

SSR container packaging is prepared

The multi-stage Dockerfile runs the generated Node.js server and excludes local environment secrets.

Done

Broad-review deployment is live and smoke-tested

AWS ECS is serving the SSR application over HTTPS, and the public routes and CMS proxy 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 SSR application will use the existing AWS billing account rather than requiring a new Google Cloud billing profile.

SSR runtime and container

Quasar produces a Node.js server and the repository includes a production Dockerfile.

Ready

AWS access and image registry

The review image is stored in ECR and runs as an ECS Express Mode service in ca-central-1.

Ready

Runtime configuration

Public CMS reads use https://cms.cofsab.ca. Authenticated and write credentials remain omitted pending workflow validation.

Ready

Reviewer access and smoke test

The public site and CMS APIs 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 repo structure, Quasar app shell, local development flow, and board preview path.

Quasar SSR project scaffolded

Local MacBook development path documented

Containerized review path documented

Project structure and conventions defined

Development environment prepared

Google Workspace 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 CMS read models without exposing Strapi 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 Zoom access against the live services.

Membership signup, account claim, and password recovery

Member profile and membership self-service

Event sessions, video, registration, and Zoom access

Production membership renewal and payment workflow

Event capacity, payment, and communications workflow

Phase 6

Accessibility and Launch Prep

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 CMS delivery implemented

Public CMS content is delivered through narrow SSR endpoints, keeping Strapi URLs, tokens, and private operational fields on the server.

Complete

CMS

Membership and event service validation

Signup, account claim, password recovery, profile self-service, event registration, and protected Zoom access are implemented or in the current delivery batch and require live end-to-end validation.

Current

Membership + Events

AWS SSR board-review deployment

The containerized SSR application is live on ECS Express Mode with managed HTTPS, Fargate, health rollback, scaling, logging, and verified public CMS reads.

Complete

Deployment

Public launch approval

Accessibility review, data migration, payments, communications automation, operational documentation, and production infrastructure remain before launch.

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 eslint.

SSR build passed

The production SSR build completed successfully.

Container configured

The production image runs the generated SSR server, excludes local environment files, and passes local route and CMS proxy smoke tests.

Operational verification pending

Authenticated member, registration, form-write, payment, and event-operation workflows still require live verification.