OFQ-00008 Static Web Applications
Last updated: 1 October 2025
For some services, the use of a full-blown C# application or CRM system is not proportionate to the goals the service should achieve, and a lightweight solution is called for instead. This is particularly the case when we want non-developers to be able to contribute to sites in an effective manner, without overloading them with a technology knowledge burden. This is where a static web app comes in; this is where a prebuilt, distributable folder with HTML, CSS and JS is used to serve a basic website. Good use cases include documentation websites such as this one, and for simple sites such as the shutter pages.
Note that all relevant development standards are still relevant, including standards for Build Pipelines, Secret Management and Security
Requirement(s)
- Static Apps MUST only be used for simple websites
- Static Apps MUST use Node with an approved build and deployment tools
Static Apps MUST only be used for simple websites
- Static Apps are intended to be truly lightweight applications, otherwise their value is lost.
- We should only serve front-end websites that do not reach out to other APIs. The Static Web App deployment can facilitate the deployment of Azure Functions for a back-end, but you must never use this - particularly as there is not an available region for this functionality in the UK for unknown reasons.
- In most cases, sites that require data entry should not be made as a Static App, as these tend to involve more complexity and may introduce additonal security requires. Exceptions are for search bars tha are implemented by build tools, such as those used by our eleventy based documentation.
- Any form of site that requires authentication should not be a static site
Static Apps MUST use Node with an approved build tool
- All static sites should use Node and one of the following tools to create the static site:
- Eleventy for documentation sites, preferably with the use of the GOV.UK Eleventy Plugin
- Vite for non-documentation sites, using the standard install path for the GOV.UK Design System
- All static sites should be deployed onto an Azure Static Web App using the guidance found in the Build Pipelines.
- Automated testing is optional but encouraged