Platform

This section documents the HVC platform as a whole — the technology choices, the end-to-end architecture, how it can run standalone, coding conventions, design decisions, and lessons learned.

The platform consists of:

• Three client applications — Web, Mobile, Headset.
• One client-facing API — Api.
• A platform admin console — Admin.
• A set of supporting .NET services — Services.

Pages

| Page | What it covers | |---|---|---| | Technology Stack | Languages, frameworks, and infrastructure used across the platform | | Architecture | How the pieces fit together end-to-end | | Stand-alone | Running HVC as a standalone/private installation | | Coding Styles | Conventions followed in the codebase | | Design Decisions | Why key technologies were chosen | | Lessons Learnt | Hard-won experience from building HVC | | Data Model | The main tables across tenant + admin databases | | Deprecated | Removed technologies and what replaced them |

Also see the cross-cutting Glossary and Getting Started.