Skip to content

Welcome

Audience: Anyone brand-new to the Portal project.

  1. TL;DR tour – 5-minute overview of the architecture, core user journeys and the tech stack.
  2. Local setup – from cloning the repo to the first successful php artisan test.
  3. Glossary – key terms (e.g. “Care Package”, “Service Group”, “RCTI”).
  4. Who to ask – Teams channels, usual reviewers and team rituals.

How we collaborate and ship.

  • Cadence – daily stand ups, fortnightly sprints with retros and planning.
  • Discovery and Design process – how do uncover requirements and shape the solution.
  • Definition of Ready / Done – what each ticket must tick before dev starts and before merge.
  • Branching & releases – Gitflow-light (main, dev, release/*).
  • Code review etiquette – one approvals, tests and lints must pass.
  • Incident response – TBA.

Step-by-step path for new joiners (devs, designers, QA or PMs).

  1. Day 1 – hardware, access, mandatory training.
  2. Week 1–2 – first ticket/design and pair-programming slots.
  3. Useful links – HR forms, leave policies, expense claims.
  • Onboarding for engineers
  • Onboarding for QA
  • Onboarding for designers

Where and how the Portal runs.

  • Environmentsdev, staging, main and others on AWS.
  • CI/CD – GitHub Actions → Envoyer → deployed
  • Secrets & config – TBC.
  • Observability stack – Sentry, CloudWatch Logs.
  • Data stores – Aurora MySQL, S3 for documents, Redis for queues/cache.

  • Design system – colour tokens, typography scale, component library (Figma + Storybook).
  • UX guidelines – accessibility (WCAG 2.1 AA), responsive grids, form validation patterns.
  • Research vault – persona cards, journey maps, past usability test videos.

  • Tech stack – Laravel 12, Vue 3 with Inertia.js, TypeScript, Tailwind.
  • Key domains – Billing, Documents, Reporting, Admin.
  • Coding standards – PSR-12, Laravel Pint preset, ESLint/Prettier.
  • Testing – Pest for PHP, Vitest for Vue, end-to-end Playwright suite.
  • Performance – TBC.

  • Test pyramid – unit, service, E2E proportions and tooling.
  • Release checklist – regression pack, accessibility spot-checks, smoke tests.
  • Bug triage process – severity matrix and SLA.
  • Test data – anonymised fixtures and seeders.
  • Reporting – Xray dashboards and weekly quality metrics.

  • Vision & OKRs – how the Portal supports Trilogy Care’s strategic goals.
  • Roadmap – next two quarters at a glance (link to Productboard).
  • Feature flags – naming convention and rollout stages.
  • User feedback loops – NPS surveys, support ticket tagging, community calls.
  • Analytics – Posthog analytics, retention cohorts, key product metrics.