Web applications / React web application · PWA · 2025–2026

MZSS Patrol System

Two connected web experiences: patrol operations on the mountain and an Academy for shared knowledge.

MZSS Patrol System — project preview
Type of work
React web application · PWA
Year
2025–2026
Technologies
ReactTypeScriptWordPress REST APIPHPMySQLTanStack QueryPWA

The challenge

MZSS, the association of ski resort rescuers that I co-founded, needs to coordinate patrol teams across a whole winter season. The original WordPress plugin brought shift sign-ups, attendance and payments together. The next step was a dedicated application that patrollers could use on their phones and coordinators could manage from a desktop, with room for incident reporting, team communication and training resources.

My role

Designed and built the new MZSS application in React and TypeScript, with a custom PHP REST backend inside WordPress and dedicated MySQL tables. The project now has two distinct frontends: the patrol workspace at app.mzss.info and the Academy at kb.mzss.info. My work spans the responsive interface, navigation, data model, API integration, permissions, operational workflows and the Academy’s structured content tools. Both frontends use the same account system and backend, while each has its own navigation and purpose.

The solution

The patrol workspace connects season planning, shift applications, approval, attendance and payment reporting. Patrollers see a personal dashboard and use a monthly calendar to apply for shifts. Coordinators handle capacity, assignments, cancellations and handovers. The mobile interface gives QR scanning a central place in the bottom navigation. The Academy is a separate reading and editing experience, where members can find materials by area, topic, search or saved favorites, and authorized editors can maintain them over time.

PROJECT FLOW / Web application workflow

From a planned shift to a recorded patrol day

  1. Plan the season

    Configure dates, locations and daily capacity.

  2. Coordinate the team

    Patrollers apply; coordinators manage approvals and shift changes.

  3. Record attendance

    QR scanning leads to server-side location and time checks.

  4. Review and report

    Attendance feeds payment periods, budgets and accounting reports.

React PWA frontend with a WordPress REST backend. The screenshots use demonstration data.

Two frontends, one shared foundation

The patrol app focuses on the working day: who is assigned, where they need to be, what has happened and what needs attention. The Academy focuses on knowledge: finding the right material, reading it clearly and keeping the published version current. They share WordPress accounts and a custom REST API rather than duplicating member records. The application links to the Academy, and the Academy provides a route back to the patrol workspace.

Key features

Implementation and current validation

The project now combines a dedicated patrol workspace and a separate Academy, with shared accounts and backend services. The interfaces above come from the current source code rather than redesigned concept screens. Portfolio screenshots use local API fixtures to demonstrate the UI. They do not verify live authentication, camera scanning, GPS attendance, payments or migration. The project documentation still lists staging checks before a complete operational rollout.

01 / The patrol app on a phone

Seven mobile views, built around the tasks a patroller needs during a shift.

The solution

The phone layout changes the way people move through the app. A fixed five-item navigation connects Home, Schedule, Scan, Injuries and Menu. The scan action sits in the middle because attendance is recorded at the start and end of a shift. The home screen highlights today’s assignment and the next one, then gives direct access to personal shifts, announcements and the Academy. On smaller screens, content stacks into readable cards while the primary navigation stays available.

What I built

  • A personal dashboard with a direct action for the next attendance scan.
  • A monthly calendar with season selection, capacity and application status.
  • A separate “My shifts” view for approved and pending assignments.
  • A camera-based QR reader with clear guidance when permission is unavailable.
  • Announcements with categories, important items and read status.
  • A dedicated injury-report form accessible from the home screen.
  • A menu that exposes additional tools according to the signed-in member’s permissions.

02 / From season planning to attendance

The calendar is part of a larger operational workflow.

The solution

Administrators configure seasons, dates, locations, capacity and shift windows. Members apply through the calendar, and coordinators approve or reject applications. Waiting lists cover full shifts. A cancellation request for an approved assignment follows an approval workflow, and a handover can involve both the receiving patroller and the coordinator. Attendance then links an approved shift to a QR scan and server-side location and time checks. Corrections are possible through an administrative override, with a history of the change.

What I built

  • Multiple seasons with their own dates, locations and capacity.
  • One active place per member and date across seasons, enforced by the scheduling rules.
  • Approval, rejection, cancellation requests and shift handovers.
  • A waiting-list workflow when normal capacity is reached.
  • QR validation, configured attendance windows and distance checks on the backend.
  • Separate check-in and check-out records, with administrative correction history.
  • Notifications and queued email support around operational changes.

03 / MZSS Academy

A dedicated knowledge platform, with its own layout and build at kb.mzss.info.

The solution

The Academy gives training materials a structured home beyond messages and scattered files. Its landing page starts with search and a set of subject areas, followed by quick procedures and recently published material. Each area can contain topics. The desktop sidebar provides access to quick procedures, favorites, recently opened materials and, for editors, drafts and archived content. Library results can switch between list and grid views, and show useful context such as category, author, update date and version.

What I built

  • A separate Academy frontend using the shared WordPress account and REST backend.
  • Areas and topics managed as structured categories rather than hard-coded pages.
  • Search by query, with category and topic filters.
  • Quick procedures, personal favorites and recently opened materials.
  • List and grid views for browsing the library.
  • Article pages with summary, author, version, update information and related material.
  • Public guides available without login, alongside member and role-restricted material.

04 / The Academy on a phone

The knowledge library has its own mobile experience.

The solution

The Academy keeps the reading experience separate from operational navigation. Search and subject areas remain the primary entry points. A compact layout makes category lists, article metadata and content readable on a phone, while the navigation drawer provides access to areas and saved views. Members can move from finding a guide to reading it and saving it as a favorite without opening a desktop interface.

What I built

  • A responsive search-led home page and subject-area cards.
  • A compact library with topic filters and material details.
  • Article content adapted to the screen width.
  • Favorites for returning to frequently used materials.
  • A mobile navigation drawer for areas, quick procedures and recently opened content.

05 / Authoring, publishing and access

The Academy includes the tools needed to maintain a living library.

The solution

Authorized editors compose materials from typed content blocks rather than unrestricted HTML. Supported blocks include headings, paragraphs, lists, checklists, tables, images, files, video links and informational callouts. Each material has a category, optional topic, summary, keywords and related materials. Editors can record a change note, choose a minor or major revision and set a review date. Draft, published and archived states separate editing from the material members can read. Administrators can assign editors to particular categories.

What I built

  • Structured content blocks validated by the backend.
  • Minor and major revisions, change notes and visible version metadata.
  • Draft, published and archived states.
  • Review dates to make future editorial checks explicit.
  • Visibility for all members, selected roles or public readers.
  • Category-specific editorial permissions.
  • Protected attachments delivered through access-checked API routes.
  • Related materials, favorites and printable reading views.

06 / Administration, payments and reporting

Tools for coordinators, administrators and the wider patrol organization.

The solution

The administration area groups shift approval, attendance, seasons and budgets, locations and QR codes, patroller roles, payments, settings, audit history and migration. Payment reporting draws on attendance across the season, with period finalization storing a snapshot of the relevant rates and amounts. Injury reports are a separate operational record with a structured form and server-side visibility rules. The information board supports targeted communication without treating sensitive incident records as ordinary announcements.

What I built

  • Season budgets, daily rates, payment periods and accounting exports.
  • Finalization and reopening of payment periods.
  • Role and patroller-profile management.
  • Injury-report fields for the intervention, team, location and circumstances.
  • Access to injury records checked on the server; unauthorized records are not exposed.
  • Information-board categories, pinned or important notices and read tracking.
  • An audit log for relevant changes and a preview-based legacy migration.

07 / Application architecture

React frontends, a custom REST API and a shared membership foundation.

The solution

React Router handles navigation, while TanStack Query manages server data and refreshes after mutations. The PHP backend separates controllers, services and persistence logic, and stores operational records in dedicated MySQL tables. Authentication uses WordPress sessions and REST nonces. The frontend obtains a fresh nonce after reload and keeps it in memory. Permissions and record ownership are evaluated on the backend. The patrol PWA caches static application assets, while private API responses are not cached. The Academy is built separately from the same frontend codebase and does not use the patrol app’s service worker.

What I built

  • React and TypeScript for both interfaces; Vite provides the separate builds.
  • TanStack Query for server state and React Router for navigation.
  • Custom WordPress REST endpoints backed by PHP services and MySQL tables.
  • Cookie-based WordPress sessions with REST nonce checks for mutations.
  • Restricted application origins and server-side role and ownership checks.
  • Static-asset PWA caching with an explicit offline screen for the patrol app.
  • The offline screen asks members to reconnect; this is not an offline patrol-data workflow.
  • Explicit legacy migration with preview, preserving the original source records.