saf links

Author: RossBugginsNHS

_config.yml

@@ -55,7 +55,7 @@ defaults:
       path: "" # an empty string here means all files in the project
       type: "saf_dimensions" # previously `post` in Jekyll 2.2.
     values:
-      layout: "home"            
+      layout: "saf_dimensions"            
   -
     scope:
       path: "guidance" # an empty string here means all files in the project

_includes/saf_dimension.html

@@ -0,0 +1,21 @@
+<h2>SAFs</h2>
+
+<table>
+{% for saf in site.safs %}
+{% if saf.dimension != include.saf_dimension_name %}
+{% continue %}
+{% endif %}
+
+<tr>
+  <td>
+    <a href="{{ saf.url | relative_url }}">
+      {{ saf.title }}
+    </a>
+  </td>
+  <td>
+    {{saf.content | markdownify | remove: '<p>' | remove: '</p>' }}
+  </td>
+</tr>
+
+{% endfor %}
+</table>

_layouts/home.html

@@ -2,7 +2,7 @@
 layout: default
 ---
 
-<link rel="stylesheet" href="./assets/nhsuk/css/nhsuk-9.6.1.min.css">
+<link rel="stylesheet" href="{{ 'assets/nhsuk/css/nhsuk-9.6.1.min.css' | relative_url  }}" />
 
 {{ content }}
 

_layouts/saf_dimensions.html

@@ -0,0 +1,11 @@
+---
+layout: home
+---
+
+<h1>{{ page.code }}: {{ page.title }}</h1>
+{{ content }}
+
+
+
+
+{%- include saf_dimension.html saf_dimension_name=page.name -%}

_layouts/safs.html

@@ -1,6 +1,11 @@
 ---
 layout: home
 ---
+{%- assign saf_dimension = site.saf_dimensions | find:"name", page.dimension -%} 
+
+
+<h1>{{ page.title }}: {{ saf_dimension.title }}</h1>
+
 
-<h1>{{ page.title }}</h1>
 {{ content }}
+

_saf_dimensions/non_functional.md

@@ -1,5 +1,5 @@
 ---
-name: design
+name: non functional
 code: NF
 title: Non-Functional Design 
 description: Do we understand the non-functional needs of the service, are we creating a solution which can meet those need and be flexible, without over engineering? 

_safs/d/d01.md

@@ -0,0 +1,8 @@
+---
+title: D01
+dimension: documentation
+tags: [req]
+nav_order: 2.71
+---
+
+All architecture documentation **MUST** be maintained within the appropriate NHS England knowledge store e.g. Aalto, SharePoint, Confluence  

_safs/nf/nf01.md

@@ -0,0 +1,8 @@
+---
+title: NF01
+dimension: non functional
+tags: [req]
+nav_order: 2.51
+---
+
+Solutions **MUST** incorporate workload observability, understand service health, and respond to events  

_safs/ru/ru01.md

@@ -0,0 +1,8 @@
+---
+title: RU01
+dimension: reuse
+tags: [req]
+nav_order: 2.61
+---
+
+If reusing existing capabilities, we MUST be confident that any additional functionality required can be sensibly and cost effectively added to the existing service i.e we are not bending something out of shape