Most of the formatting is not up-to-date and sometimes users are not shown any subsections because the file is named index.md instead of _index.md.

As this project hopefully lasts for the future, I would suggest honoring its predecessors and adapting all chapters as closely as possible to the original.

I already started doing so as I'm also interested in each and every topic and I already found out that most of the linked resources aren't available anymore or the link is not directed to the right location.

Already started this process and hope to create a pull request soon (might take some time).

(could be a guideline as well)

Put it in the new template format.

Working list:

• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/begin-as-an-afterword/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/begin-end/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/binary-operator-line-start/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/case-actions/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/comments-spacing/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/end-else-pair/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/keyword-pairs-indentation/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/line-start-keywords/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/lonely-repeat/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/named-invocations/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/one-statement-per-line/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/separate-if-and-else/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/spacing-binary-operators/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/suggested-abbreviations/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/temporary-variable-naming/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/unnecessary-else/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/unnecessary-truefalse/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/variable-naming/
• https://alguidelines.dev/navpatterns/3-cal-coding-guidelines/readability/variables-declarations-order/

Specific guidelines for "avoiding OnPrem-only code"

Discussed in https://github.com/microsoft/alguidelines/discussions/102

Show Count or even previews

The Welcome page in empty

(also find the right name for it)

Describe the facade pattern in the context of the AL programming language.

For a better reviewing of how the documentation would look like in the production environment it would be awesome if there's an additional subsection "Set up local environment" or "Containerization" in the Contributing section.

EDIT:
Just to give you an example on how this could look like:

We could think about using user-defined taxonomies which is supported by Hugo: https://gohugo.io/content-management/taxonomies/ as a good practice as we move on with this project.

Example:

One of my friends told me he'd like to choose something like clean code for his thesis topic.

With that being said, I think it would be a good idea to provide a CITATION.cff in this repo.

Related links:

• https://github.blog/2021-08-19-enhanced-support-citations-github/
• https://github.com/citation-file-format/citation-file-format

https://alguidelines.dev/docs/bestpractices/named-invocations/

Would be interesting if a tip / links section could be added pointing to
https://github.com/StefanMaron/BusinessCentral.LinterCop/wiki/LC0012

Since with either implicit or explicit are being deprecated, shouldn't this recommend not using with at all?

In the world of interfaces, it is important to preserve (certain) events over multiple interface implementations.

Microsoft preferred in the base app IsHandled instead of Handled.
I think this should be adapted in the generic method pattern examples.

Just an idea to add a list of available books.

The video for Blocked Entity https://alguidelines.dev/docs/navpatterns/patterns/blocked-entity/ is showing as unavailable as it is private.

The video should be removed or contact the publisher and see if it can be made public.

https://github.com/microsoft/alguidelines/blob/9a0922e35ff8567630bf5e0aceec5bb327512d50/content/docs/_index.md?plain=1#LL43C17-L43C17

add /docs/

• Fork
• branch
• PR

Too often I see people that assign meaning to random numbers. We see this standard if people refer to objects by number or options by the integer value, however it happens to when importing file formats outside our control or people try to sort stuff with more. The rule should be "No Magic Numbers". Use meaning full abstractions that make the code readable instead. Magic Numbers obscured the intent for the reader.

Please discuss

Please fix the indentation of the code. It is incorrect under the "else"

Existing

    END ELSE
        TempErrorMessage.LogSimpleMessage(TempErrorMessage."Message Type"::Error,NoSATAccountDefinedErr);

        IF NOT TempErrorMessage.HasErrors(TRUE) THEN
            SaveXMLToClient(Document,Year,Month,'CT');
        TempErrorMessage.ShowErrorMessages(FALSE);

Should be

    END ELSE
        TempErrorMessage.LogSimpleMessage(TempErrorMessage."Message Type"::Error,NoSATAccountDefinedErr);

     IF NOT TempErrorMessage.HasErrors(TRUE) THEN
         SaveXMLToClient(Document,Year,Month,'CT');
     TempErrorMessage.ShowErrorMessages(FALSE);

The BC Guidelines template has a typo:

[...], please feel fee to [...] => [...], please feel free to [...]

Renaming affacts all published BC Guidelines and it's template.

Would be great to have validation / scoring

The upperleft alguidelines.dev text links to a non-existing url:
https://alguidelines.dev/%20/

Why are the requirements not simply lists and in code blocks? Also broken link, probably due to being in a code block.