HSLG application documentation
This is the reference manual for the current High Spirits Leisure Group application, spanning its shared user interface, WordPress presentation, native Capacitor design, application API and business data. It explains how code behaves, why architectural choices were made and how a customer or operator uses each feature. It also records limits: a demonstration screen is not proof that a payment, booking or Android plugin works.
Navigation
- Code and module reference: components, entry points, dependencies, errors and tests.
- Architecture and decisions: why, alternatives, costs and deployment boundaries.
- Customer and operator guide: procedures, outcomes and troubleshooting.
- Licensing and commercial-use evidence: package and artwork rights.
- Disaster recovery: one authoritative zero-backup rebuild and verification procedure.
- Development chronology: dated actions, changes and evidence.
How to interpret status
Source implemented, locally tested, staging verified and physical-device verified are separate states. A page must say which applies. Unresolved financial, privacy or operational decisions are not filled with defaults merely to make a document look complete.