From bac7c0f87961f8bf8a67011b5538571c0989e103 Mon Sep 17 00:00:00 2001 From: Jeremy Vyska <35526546+JeremyVyska@users.noreply.github.com> Date: Sat, 30 Oct 2021 23:04:37 +0200 Subject: [PATCH] Fixing up some titles --- config.toml | 4 ++++ content/NAVPatterns/1-patterns/_index.md | 2 +- content/NAVPatterns/2-anti-patterns/_index.md | 2 +- .../3-cal-coding-guidelines/_index.md | 2 +- content/NAVPatterns/4-get-involved/_index.md | 6 +++++- content/NAVPatterns/_index.md | 16 ++++++++++++---- 6 files changed, 24 insertions(+), 8 deletions(-) diff --git a/config.toml b/config.toml index f90b17cc..a465b382 100644 --- a/config.toml +++ b/config.toml @@ -17,6 +17,10 @@ home = [ "HTML", "RSS", "JSON"] disableLandingPageButton = true # Enable GitHub editing editURL = "https://github.com/BC-Design-Patterns/AL-Dev-Help/edit/main/content" + # This controls whether submenus will be expanded (true), or collapsed (false) in the + # menu; if no setting is given, the first menu level is set to false, all others to true; + # this can be overridden in the pages frontmatter + alwaysopen = false # Additional menu (left sidebar) area links [[menu.shortcuts]] diff --git a/content/NAVPatterns/1-patterns/_index.md b/content/NAVPatterns/1-patterns/_index.md index ca811c91..76b499d6 100644 --- a/content/NAVPatterns/1-patterns/_index.md +++ b/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 diff --git a/content/NAVPatterns/2-anti-patterns/_index.md b/content/NAVPatterns/2-anti-patterns/_index.md index 6bf5d355..e0c88db2 100644 --- a/content/NAVPatterns/2-anti-patterns/_index.md +++ b/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. diff --git a/content/NAVPatterns/3-cal-coding-guidelines/_index.md b/content/NAVPatterns/3-cal-coding-guidelines/_index.md index 1b26924a..0caa5b25 100644 --- a/content/NAVPatterns/3-cal-coding-guidelines/_index.md +++ b/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). diff --git a/content/NAVPatterns/4-get-involved/_index.md b/content/NAVPatterns/4-get-involved/_index.md index b8b6bcd9..204c290f 100644 --- a/content/NAVPatterns/4-get-involved/_index.md +++ b/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. diff --git a/content/NAVPatterns/_index.md b/content/NAVPatterns/_index.md index ccd4abce..8f91df12 100644 --- a/content/NAVPatterns/_index.md +++ b/content/NAVPatterns/_index.md @@ -1,12 +1,20 @@ +++ chapter = true pre = " " -title = "NAVPatterns" +title = "NAV Patterns Archive" weight = 20 +++ -### Chapter X +# NAV Patterns Archive -# Some Chapter title +## About the archive -Lorem Ipsum. \ No newline at end of file +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. \ No newline at end of file