Print page so can be copied to confluence.

Author: RossBugginsNHS

_includes/safs_print.html

@@ -75,15 +75,22 @@ <h3>  {{saf_dimension.title}}</h3>
 
 <table>
 <tr>
-  <th style="width:5%;">
-    Complete
+    <th style="width:3%;">
+    Item
+  </th>
+    <th style="width:10%;">
+    Title
+  </th>  
+      <th style="width:20%;">
+    Notes
   </th>  
-  <th style="width:5%;">
+  <th style="width:3%;">
+    Complete ✅ / ❌
+  </th>  
+  <th style="width:3%;">
     Score <br/> (0-5)
   </th>    
-  <th style="width:5%;">
-    Item
-  </th>
+
   <th>
     Description
   </th>
@@ -93,18 +100,25 @@ <h3>  {{saf_dimension.title}}</h3>
 {% continue %}
 {% endif %}
 <tr>
-    <td style="width:5%;">
+    <td style="width:3%;">
+     <b>{{ saf.title }}</b> 
+  </td>
+    <td style="width:10%;">
+   {{ saf.description }}
+  </td>
+      <td style="width:20%;">
 
   </td>
-      <td style="width:5%;">
+    <td style="width:3%;">
 
   </td>
-  <td style="width:5%;">
-      {{ saf.title }}
+      <td style="width:3%;">
+  
   </td>
+
   <td>
 
-    {% include saf_content.html summary_only=true saf=saf %}
+   {{saf.requirement | default: saf.content  | markdownify | remove: '<p>' | remove: '</p>' }}
   </td>
 
 </tr>

_safs/s/s03.md

@@ -8,6 +8,12 @@ description: Roadmap
 requirement: |
     A well-formed and maintained product vision & roadmap **MUST** exist with appropriate detail around architecture elements 
 
+todos:
+  - examples of good and bad product visions
+  - who should you be working with
+  - who should own those documents (vision and roadmap)
+  - what is the appropriate level of detail?
+
 more_info: |
  asd
  asd

_safs/s/s04.md

@@ -8,6 +8,11 @@ description: Objectives
 requirement: |
     The solution design **MUST** be able to meet the stated user needs and overall business objectives/drivers 
 
+todos:
+  - what are examples of what those needs look like
+  - how to critique those needs
+  - where to find the current overall business drivers?
+
 more_info: |
  asd
  asd