This commit is contained in:
waldo1001 2021-11-11 13:59:35 +00:00
parent fd4c4e6198
commit aca2511c9a
134 changed files with 2618 additions and 2618 deletions

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contributing on AL Guidelines</title><link>https://alguidelines.dev/contributing/</link><description>Recent content in Contributing on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/contributing/index.xml" rel="self" type="application/rss+xml"/><item><title>Templates</title><link>https://alguidelines.dev/contributing/templates/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/contributing/templates/</guid><description>Templates We have foreseen some template-files that you can simply copy and use. Look at them as &amp;ldquo;Patterns for describing patterns&amp;rdquo; 😉.
We have foreseen a Template for:
Guidelines Patterns</description></item><item><title>Formatting tips</title><link>https://alguidelines.dev/contributing/formattingtips/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/contributing/formattingtips/</guid><description>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
We have foreseen a Template:
for patterns for guidelines</description></item><item><title>Formatting tips</title><link>https://alguidelines.dev/contributing/formattingtips/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/contributing/formattingtips/</guid><description>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:</description></item><item><title>Guide to Fork &amp; PR</title><link>https://alguidelines.dev/contributing/forkandpr/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/contributing/forkandpr/</guid><description>Abstract (coming soon)
Steps Step 1: Fork Step 2: Branch Step 3: Pullrequest</description></item><item><title>Understanding the Approval Process</title><link>https://alguidelines.dev/contributing/theapprovalprocess/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/contributing/theapprovalprocess/</guid><description>(coming soon)</description></item></channel></rss>