Fixing up some titles

content/NAVPatterns/1-patterns/_index.md

@@ -1,6 +1,6 @@
 +++
 chapter = true
-title = "1-patterns.md"
+title = "1. Patterns"
 weight = 110
 +++
 ## Browse design patterns by tags

content/NAVPatterns/2-anti-patterns/_index.md

@@ -1,6 +1,6 @@
 +++
 chapter = true
-title = "2-anti-patterns.md"
+title = "2. Anti-Patterns"
 weight = 130
 +++
 Some of the software development practices, had **not** stood the test of time. Despite that, some are still being used today by developers everywhere.

content/NAVPatterns/3-cal-coding-guidelines/_index.md

@@ -1,6 +1,6 @@
 +++
 chapter = true
-title = "3-cal-coding-guidelines.md"
+title = "3. CAL Coding Guidelines"
 weight = 150
 +++
 We've decided to publish our current C/AL coding guidelines. They are actual, as per January 2015 when this is published (but might fall out of sync as time goes by). 

content/NAVPatterns/4-get-involved/_index.md

@@ -1,8 +1,12 @@
 +++
 chapter = true
-title = "4-get-involved.md"
+title = "(OLD) Get Involved"
 weight = 170
 +++
+
+**Reminder, this is an ARCHIVE of the Patterns site, this information is not current.**
+---
+
 **Spread the info**
 
 NAV Design Patterns are excellent materials for training and knowledge transfer. In your company, you can help new developer get to speed with NAV by recommending them to read and then present to the team one of the most common patterns: [No. Series][anchor0], [Setup Table][anchor1] and definitely [Hooks ][anchor2]which will be a great investment in reducing your upgrade time. The more experienced developers can read directly the newer patterns, like [Surrogate Key][anchor3], [Easy Update][anchor4], [Totals on Subpages][anchor5], [Using Queries instead of nested loops][anchor6] etc.

content/NAVPatterns/_index.md

@@ -1,12 +1,20 @@
 +++
 chapter = true
 pre = "<b><i class='fas fa-save'></i> </b>"
-title = "NAVPatterns"
+title = "NAV Patterns Archive"
 weight = 20
 +++
 
-### Chapter X
+# NAV Patterns Archive
 
-# Some Chapter title
+## About the archive
 
-Lorem Ipsum.
+This section of the site is a careful reproduction of the content of the Original Microsoft Community NAV Design Patterns project, created with permission.
+
+## Reading the archive
+
+Bear in mind, many of the style and formatting guidelines in this section have been brought forward into:
+- The automatic formatting provided by the AL Extension
+- The Code Analyzers
+
+Additionally, a variety of topics around the Windows Client and DotNet are outdated, and should only be used for either reference or if working in older environments.