diff --git a/app/templates/new/templates_glossary.md b/app/templates/new/templates_glossary.md
index 1c52e75dc..7cd51f1a9 100644
--- a/app/templates/new/templates_glossary.md
+++ b/app/templates/new/templates_glossary.md
@@ -6,10 +6,9 @@ This document serves as a glossary for the templates directory structure of the
## Directory Structure
- `/templates`
- - `base.html`: The main base template from which all other templates inherit. This template is a combination of `main_template`, `admin_template`, `withoutnav_template`, `settings_templates`, and `content_template`.
+ - `base.html`: The main base template from which all other templates inherit. This template is a combination of `main_template`, `admin_template`, `withoutnav_template`, and `content_template`.
- **/layouts**: Contains shared layouts used across the site. Simply put, it defines the overall structure or skeleton of the application (less frequently revised).
- - `withnav_template.html`: A variation of the base layout that includes a sidebar.
- - `org_template.html`: A variaton of the withnav_template
+ - `withnav_template.html`: A variation of org_template and settings_template that includes a sidebar.
- **/components**: Houses reusable UI components that can be included in multiple templates and can be tailored with different content or links depending on the context.(more frequently revised or customized)
- `head.html`: Template for the site's , included in `base.html`.
- `header.html`: Template for the site's header, included in `base.html`.
@@ -23,20 +22,15 @@ This document serves as a glossary for the templates directory structure of the
### Best Practices
- Use **inheritance** `{% extends %}` to build on base layouts.
-- Employ **components** `{% include %}` for reusable UI elements to keep the code DRY and facilitate easier updates.
-
-### Observation Notes
-- The macro-options.json files in the header and footer component act as structural guides. They aren't directly used as data passed to the usaFooter function/macro. Instead, these files outline the expected properties and provide a description of their purpose. The `usaFooter` macro component is currently only invoked in the `admin_template`, which will eventually serve as the `base.html` template. This will simplify the approach when we change the footer macros to componenets by eliminating the need to dynamically pass this data from the base.html template. This is also true for `usaHeader` macro component.
-
-
+- Employ **components** `{% include %}` for reusable UI elements.
### Old Layout Templates We Don't Need
-- withoutnav_template.html Delete
-- main_template.html Delete
+- withoutnav_template.html Delete, it is now apart of base.html
+- main_template.html Delete, it is now apart of base.html
- settings_templates.html `withnav_template` can be used to replace `settings_template`.
- settings_nav.html (move to /components/ directory)
- main_nav.html (move to /components/ directory)
- service_navigation.html (move to /components/ directory)
-- org_template, could be under it's own directory called /layout/organization
+- org_template, Delete, it is now apart of withnav_template.html
- org_nav.html (move to /components/ directory)
-- content_template.html Delete
+- content_template.html Delete, it is now apart of base.html
diff --git a/app/templates/admin_template.html b/app/templates/old/admin_template.html
similarity index 100%
rename from app/templates/admin_template.html
rename to app/templates/old/admin_template.html
diff --git a/app/templates/content_template.html b/app/templates/old/content_template.html
similarity index 94%
rename from app/templates/content_template.html
rename to app/templates/old/content_template.html
index 34b488bb5..5f45027b3 100644
--- a/app/templates/content_template.html
+++ b/app/templates/old/content_template.html
@@ -1,4 +1,4 @@
-{% extends "withoutnav_template.html" %}
+{% extends "base.html" %}
{% from "components/sub-navigation.html" import sub_navigation %}
{% from "components/page-header.html" import page_header %}
diff --git a/app/templates/main_template.html b/app/templates/old/main_template.html
similarity index 100%
rename from app/templates/main_template.html
rename to app/templates/old/main_template.html
diff --git a/app/templates/withoutnav_template.html b/app/templates/old/withoutnav_template.html
similarity index 94%
rename from app/templates/withoutnav_template.html
rename to app/templates/old/withoutnav_template.html
index d31589086..b6b77088e 100644
--- a/app/templates/withoutnav_template.html
+++ b/app/templates/old/withoutnav_template.html
@@ -1,4 +1,4 @@
-{% extends "admin_template.html" %}
+{% extends "base.html" %}
{% set mainClasses = "margin-top-5 padding-bottom-5" %}
diff --git a/app/templates/org_template.html b/app/templates/org_template.html
index dd3fbee20..5e04003fd 100644
--- a/app/templates/org_template.html
+++ b/app/templates/org_template.html
@@ -1,4 +1,4 @@
-{% extends "admin_template.html" %}
+{% extends "base.html" %}
{% block per_page_title %}
{% block org_page_title %}{% endblock %} – {{ current_org.name }}
diff --git a/app/templates/settings_template.html b/app/templates/settings_template.html
index 8b086e9f7..a42f043b0 100644
--- a/app/templates/settings_template.html
+++ b/app/templates/settings_template.html
@@ -1,4 +1,4 @@
-{% extends "admin_template.html" %}
+{% extends "base.html" %}
{% block per_page_title %}
{% block service_page_title %}{% endblock %} – {{ current_service.name }}
diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index cbca9e59a..4a82fa9ed 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -1,4 +1,4 @@
-{% extends "content_template.html" %}
+{% extends "base.html" %}
{% from "components/service-link.html" import service_link %}
{% from "components/content-metadata.html" import content_metadata %}
@@ -168,7 +168,7 @@
The following content on the Notify status page is not compliant with the WCAG version 2.1 AA standard:
-
We are committed to doing all that we can to keep your data secure. To prevent unauthorized access or disclosure we have put in place technical and organizational procedures to secure the data we collect about you – for example, we protect your
@@ -70,7 +70,7 @@