Merge pull request #91 from cabinetoffice/change-digital-handbooks-domain

Change digital handbooks domain

Author: DanielMurray97

config/tech-docs.yml

@@ -1,6 +1,6 @@
 # Host to use for canonical URL generation (without trailing slash)
-host: https://guidance.cabinetoffice.gov.uk/digital-handbook
-service_link: /digital-handbook
+host: https://digital-handbook.cabinetoffice.gov.uk
+service_link: /
 
 # Header-related options
 show_govuk_logo: false
@@ -13,9 +13,9 @@ header_links:
   GitHub: https://github.com/cabinetoffice/digital-handbook
 
 footer_links:
-  Accessibility: /digital-handbook/accessibility.html
+  Accessibility: /accessibility.html
 
-enable_search: false
+enable_search: true
 
 # Tracking ID from Google Analytics (e.g. UA-XXXX-Y)
 # ga_tracking_id: UA-111409592-1

source/docs/cloud/aws-administration-min-requirements.html.md.erb

@@ -90,7 +90,7 @@ To ensure the continuous operation and security of Cabinet Office services, each
 
 #### **Minimum Administrator Coverage and the Principle of Least Privilege**
 
-To ensure both security and operational resilience, our approach to administrator access is founded on the [**Principle of Least Privilege**.](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/guidance/software/principle-least-privilege.html#principle-of-least-privilege) This principle dictates that individuals are not granted standing permissions. Instead, they are given the ability to assume a role with elevated privileges only when required to perform a specific, time-bound task. This model allows us to reconcile the need for resilience with the Principle of Least Privilege.
+To ensure both security and operational resilience, our approach to administrator access is founded on the [**Principle of Least Privilege**.](https://digital-handbook.cabinetoffice.gov.uk/docs/guidance/software/principle-least-privilege.html#principle-of-least-privilege) This principle dictates that individuals are not granted standing permissions. Instead, they are given the ability to assume a role with elevated privileges only when required to perform a specific, time-bound task. This model allows us to reconcile the need for resilience with the Principle of Least Privilege.
 
 * **Ensuring Redundancy:** To safeguard against single points of failure (e.g., due to unexpected absence or staff attrition), it is required that **more than one individual per team** meets the criteria for administrator access outlined in the 'Requirements for AWS Administrators' section. These individuals should be capable of assuming an administrative role when a need arises.  
 * **Case-by-Case Justification:** While multiple team members must be eligible, they should not hold permanent or standing administrator privileges. The Team Lead or Service Owner is responsible for assessing their service's specific needs and formally documenting the justification for the number of personnel who are granted the ability to assume an administrative role.  

source/docs/cloud/aws-shared-responsibility-model.html.md.erb

@@ -60,7 +60,7 @@ Our shared responsibility model is an extension to the [AWS Shared Responsibilit
 
  (1) *In an emergency situation such as a major cyber security incident, the Platform Engineering (COPE) Team may invoke temporary emergency access to the AWS accounts owned by the service teams to safeguard Cabinet Office assets. This should not be treated as routine operation, as it introduces security risk and must be governed by established approvals and audit trails.* 
 
-(2) *It is essential that the service team maintains continuous technical capability to support both the applications and the infrastructure of the services they own, irrespective of whether provision is in‑house or via outsourced providers. AWS administrators must comply with the [AWS Administration Policy](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/guidance/software/aws-administration-min-requirements.html), and [incident response](https://docs.google.com/document/d/1Kb6-It-LMbj7UiO9bl2QCC5sCm0TW_3-dYfS10ov2ow/edit?tab=t.0#heading=h.p99426yo0rbv) management should be followed and tested.*
+(2) *It is essential that the service team maintains continuous technical capability to support both the applications and the infrastructure of the services they own, irrespective of whether provision is in‑house or via outsourced providers. AWS administrators must comply with the [AWS Administration Policy](https://digital-handbook.cabinetoffice.gov.uk/docs/guidance/software/aws-administration-min-requirements.html), and [incident response](https://docs.google.com/document/d/1Kb6-It-LMbj7UiO9bl2QCC5sCm0TW_3-dYfS10ov2ow/edit?tab=t.0#heading=h.p99426yo0rbv) management should be followed and tested.*
 
 ## AWS Supplier Enterprise Support
 

source/docs/cloud/github-admin-access-policy.html.md.erb

@@ -27,7 +27,7 @@ If you are a GitHub administrator, you are responsible for the following for you
 ### **Access and permission management**
 
 * Grant and revoke collaborator access and team permissions.  
-* Maintain [least-privilege access](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/guidance/software/principle-least-privilege.html) and limit the number of full admin rights. We recommend 2 to 3 repo admins, or an automation GitHub App for the role.
+* Maintain [least-privilege access](https://digital-handbook.cabinetoffice.gov.uk/docs/guidance/software/principle-least-privilege.html) and limit the number of full admin rights. We recommend 2 to 3 repo admins, or an automation GitHub App for the role.
 
 ### **Repository configuration and lifecycle**
 

source/docs/cloud/request-new-aws-account.html.md.erb

@@ -65,5 +65,5 @@ Pattern 2:
 
 You are required to adhere to the Cabinet Office technical standards. Please review the following Digital Handbook guidance before configuring your environment:
 
-* [**AWS Administration Minimum Requirements**](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/cloud/aws-administration-min-requirements.html) \- Detailed security and setup obligations.  
-* [**Branching Strategies & Policies**](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/software/branching-strategies-policies-standards.html) \- Code management standards.
+* [**AWS Administration Minimum Requirements**](https://digital-handbook.cabinetoffice.gov.uk/cloud/aws-administration-min-requirements.html) \- Detailed security and setup obligations.  
+* [**Branching Strategies & Policies**](https://digital-handbook.cabinetoffice.gov.uk/docs/software/branching-strategies-policies-standards.html) \- Code management standards.

source/docs/data/data-minimum-enterprise-requirements.html.md.erb

@@ -64,7 +64,7 @@ Deviations from any of these requirements need to be explained and approved by t
 
 Each MER is given a MoSCoW prioritisation depending on the level of maturity of the organisation (see [MERs Scorecard](#heading=h.mtvit9w1silb)).    
 
-Designs that satisfy most requirements will score higher than those that only satisfy some, hence, have a greater likelihood of gaining approval from TDA. Minimum threshold for approval will be reviewed regularly by the TDA in line with the Data Maturity Assessment. This will be maintained in the [TDA Terms of Reference](https://guidance.cabinetoffice.gov.uk/digital-handbook/docs/governance/technical-design-authority)
+Designs that satisfy most requirements will score higher than those that only satisfy some, hence, have a greater likelihood of gaining approval from TDA. Minimum threshold for approval will be reviewed regularly by the TDA in line with the Data Maturity Assessment. This will be maintained in the [TDA Terms of Reference](https://digital-handbook.cabinetoffice.gov.uk/docs/governance/technical-design-authority)