https://alguidelines.dev/contributing/Recent content in Contributing on AL GuidelinesHugo -- gohugo.ioen-ushttps://alguidelines.dev/contributing/templates/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/contributing/templates/Templates We have foreseen some template-files that you can simply copy and use. Look at them as “Patterns for describing patterns” 😉. We have foreseen a Template: for patterns for guidelineshttps://alguidelines.dev/contributing/formattingtips/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/contributing/formattingtips/Tips and tricks in terms of working with MarkDown and Hugo Markdown Cheat Sheet Here you can find a rather interesting Cheat Sheet regarding markdown: https://www.markdownguide.org/cheat-sheet Code Fences / Syntax highlighting The syntax to use codefences is with backticks. If you provide the language after the first block of backticks, github will automatically put that in decent syntax highlighting. So, A simple code fence with AL code, can simply be done by:https://alguidelines.dev/contributing/forkandpr/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/contributing/forkandpr/Abstract AL Guidelines is a community project, and as such YOU are encouraged to submit corrections and new ideas. In order to get your content included, you must submit a pull request to the GitHub Repository (Located here: https://github.com/microsoft/alguidelines). All Pull Requests are subject to approval by a minimum three admins. If You are toying with an idea, but You aren’t ready to create a document just yet, you are encouraged to create a project discussion thread here: https://github.https://alguidelines.dev/contributing/theapprovalprocess/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/contributing/theapprovalprocess/(coming soon)