Add template file for local plan guidance

application/templates/pages/guidance/specifications/local-plan.html

@@ -0,0 +1,22 @@
+{%- do pageData.update({
+  'pageTitle': ((pageData.name | replace('-',' ')) + ' data') | capitalize
+}) %}
+{% set templateName = 'dl-info/guidance/specification/local-plan.html' %}
+{% extends "layouts/layout--guidance.html" %}
+
+{%- from "components/back-button/macro.jinja" import dlBackButton %}
+{% block breadcrumbs%}
+  {{ dlBackButton({
+    "parentHref": '/guidance/specifications/'
+  })}}
+{% endblock %}
+
+{% block content_primary %}
+
+    {% set markdown_content %}
+    {%- include pageData.root_url + "specifications/" + pageData.name  + ".md" with context -%}
+    {% endset %}
+
+    {{ markdown_content | render_markdown(govAttributes=True) }}
+
+{% endblock %}

application/templates/pages/guidance/specifications/local-plans.md → application/templates/pages/guidance/specifications/local-plan.md

@@ -9,7 +9,7 @@ There are 4 datasets you must provide for local plan data:
 * Local plan boundary dataset
 * Local plan document dataset
 * Local plan timetable dataset
-  
+
 ### Format
 
 You can provide data in one of these formats:
@@ -37,7 +37,7 @@ A complete record should contain the following fields (columns):
 A reference or ID for the local plan that is:
 * unique within your dataset
 * permanent - it doesn't change when the dataset is updated
-  
+
 If you don't use a reference already, you will need to create one. This can be a short set of letters or numbers.
 
 Example: `Leeds-LP01`
@@ -52,7 +52,7 @@ A brief description of the plan.
 
 Example: `The new local plan will set out how Bristol will develop up to 2040`
 
-### period-start-date 
+### period-start-date
 The start date of the period the plan covers.
 
 Example:
@@ -64,7 +64,7 @@ With dates, some data is better than no data, so:
 * `2024-03` is better
 * `2024-04-28` is brilliant
 
-### period-end-date 
+### period-end-date
 The end date of the period the plan covers.
 
 Example: `2030-03-28`
@@ -74,7 +74,7 @@ With dates, some data is better than no data, so:
 * `2030-03` is better
 * `2030-04-28` is brilliant
 
-### local-plan-boundary 
+### local-plan-boundary
 The reference code for the boundary the plan covers - use the same one you are using for the reference field in your local-plan-boundary dataset.
 
 Example: `YORK-LPB-01`
@@ -86,7 +86,7 @@ Example
 `http://www.LPAwebsite.org.uk/local-plan`
 
 ### organisations
-The code for the organisation or organisations responsible for the local plan. If it’s more than one organisation, separate them with a comma. 
+The code for the organisation or organisations responsible for the local plan. If it’s more than one organisation, separate them with a comma.
 Create this code by using the relevant prefix, a colon (:), and the reference for your organisation from this [list of organisations](https://www.planning.data.gov.uk/organisation/).
 
 Example: `local-authority:BUC`
@@ -103,9 +103,9 @@ With dates, some data is better than no data, so:
 * `2022` is fine
 * `2022-12` is better
 * `2022-12-20` is brilliant
-  
+
 ### start-date
-The date the validity of the record starts, written in YYYY-MM-DD format. 
+The date the validity of the record starts, written in YYYY-MM-DD format.
 
 Example: `2024-04-25`
 
@@ -116,7 +116,7 @@ With dates, some data is better than no data, so:
 * `2024-04-25` is brilliant
 
 ### end-date
-The date the validity of the record ends, written in YYYY-MM-DD format. 
+The date the validity of the record ends, written in YYYY-MM-DD format.
 
 Example: `2030-01-20`
 
@@ -131,7 +131,7 @@ This dataset is about local plan boundaries. Don’t worry if you don’t have a
 A complete record should contain the following fields (columns):
 
 ### reference
-A reference or ID for the boundary the plan covers. If it covers the exact planning authority boundary then use the planning authority boundary reference. 
+A reference or ID for the boundary the plan covers. If it covers the exact planning authority boundary then use the planning authority boundary reference.
 
 It must be:
 * unique within your dataset
@@ -142,7 +142,7 @@ If you don't use a reference already, you will need to create one. This can be a
 Example: `YORK-LPB-01`
 
 ### name
-A name for the boundary. 
+A name for the boundary.
 
 Example: `City of York boundary`
 
@@ -179,7 +179,7 @@ With dates, some data is better than no data, so:
 * `2022-12-20` is brilliant
 
 ### start-date
-The date the validity of the record starts, written in YYYY-MM-DD format. 
+The date the validity of the record starts, written in YYYY-MM-DD format.
 
 Example: `2024-04-25`
 
@@ -190,7 +190,7 @@ With dates, some data is better than no data, so:
 * `2024-04-25` is brilliant
 
 ### end-date
-The date the validity of the record ends, written in YYYY-MM-DD format. 
+The date the validity of the record ends, written in YYYY-MM-DD format.
 
 Example: `2030-01-20`
 
@@ -210,19 +210,19 @@ A reference or ID for the document that is:
 
 * unique within your dataset
 * permanent - it doesn't change when the dataset is updated
-  
+
 If you don't use a reference already, you will need to create one. This can be a short set of letters or numbers.
 
 Example: `CORESTRAT-2017-08`
 
 ### name
-The name of the document. 
+The name of the document.
 
 Example: `Borchester Core Strategy August 2017`
 
 ### description
 
-A description of the document. 
+A description of the document.
 
 Example: `The core strategy is the main planning document which guides development choices and decisions in Borchester. The strategy was adopted on 10 August 2017`
 
@@ -266,19 +266,19 @@ With dates, some data is better than no data, so:
 * `2022` is fine
 * `2022-12` is better
 * `2022-12-20` is brilliant
-  
+
 ### start-date
-The date the validity of the record starts, written in YYYY-MM-DD format. 
+The date the validity of the record starts, written in YYYY-MM-DD format.
 
 Example: `2024-04-25`
 
 With dates, some data is better than no data, so:
 * `2024` is fine
 * `2024-04` is better
 * `2024-04-25` is brilliant
-  
+
 ### end-date
-The date the validity of the record ends, written in YYYY-MM-DD format. 
+The date the validity of the record ends, written in YYYY-MM-DD format.
 
 Example: `2030-01-20`
 
@@ -288,7 +288,7 @@ With dates, some data is better than no data, so:
 * `2030-01-20` is brilliant
 
 ## Local plan timetable dataset
-This dataset is about local plan timetables. Don’t worry if you don’t have all the data we’ve asked for available right now. If you give us what you’ve got, we can help you fill in the gaps later. 
+This dataset is about local plan timetables. Don’t worry if you don’t have all the data we’ve asked for available right now. If you give us what you’ve got, we can help you fill in the gaps later.
 
 If you’re in the early stages of making your local plan, we expect the dates you give us to be estimated to at least the nearest month in which you think the event will happen. When they actually happen we’d expect you to update the dataset with the actual date (YYYY-MM-DD).
 
@@ -328,7 +328,7 @@ With dates, some data is better than no data, so:
 * `2022` is fine
 * `2022-12` is better
 * `2022-12-20` is brilliant
-  
+
 ### notes
 Optional text on how this data was made or produced, or how it can be interpreted.
 
@@ -352,7 +352,7 @@ With dates, some data is better than no data, so:
 * `2022-12-20` is brilliant
 
 ### start-date
-The date the validity of the record starts, written in YYYY-MM-DD format. 
+The date the validity of the record starts, written in YYYY-MM-DD format.
 
 Example: `2024-04-25`
 
@@ -362,12 +362,11 @@ With dates, some data is better than no data, so:
 * `2024-04-25` is brilliant
 
 ### end-date
-The date the validity of the record ends, written in YYYY-MM-DD format. 
+The date the validity of the record ends, written in YYYY-MM-DD format.
 
 Example: `2030-01-20`
 
 With dates, some data is better than no data, so:
 * `2030` is fine
 * `2030-01` is better
 * `2030-01-20` is brilliant
-