Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update Front Page 'Whats New'

Browse source
This commit is contained in:
Henrik Helgesen 2022-02-28 14:04:33 -08:00
parent d2725b5bf0
commit 798ed63b53
1 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

22
content/_index.md
View file

@ -125,14 +125,14 @@ images: ["images/og-image-fission.png"]
<div class="card-shadow"> <div class="card-shadow">
<span class="card-badge">PATTERN</span> <span class="card-badge">PATTERN</span>
<h4 class="section-text-bold mt-4"> <h4 class="section-text-bold mt-4">
Event Bridge No. Series
</h4> </h4>
<div class="card-shadow-content"> <div class="card-shadow-content">
<p class="section-text"> <p class="section-text">
In the world of interfaces, it is important to preserve (certain) events over multiple implementation of the interface. The “Number Series” system is used extensively to provide numbers to master records, documents, and other transactions through Microsoft Dynamics 365 Business Central.
</p> </p>
<a href="/docs/patterns/event-bridge-pattern/"> <a href="/docs/patterns/no-series/">
<button class="hero-mid align-self-end">Read Now</button> <button class="hero-mid-2 align-self-end">Read Now</button>
</a> </a>
</div> </div>
</div> </div>
@ -140,15 +140,15 @@ images: ["images/og-image-fission.png"]
<div class="col-lg-4"> <div class="col-lg-4">
<div class="card-shadow"> <div class="card-shadow">
<span class="card-badge">BEST PRACTICE</span> <span class="card-badge">TAG</span>
<h4 class="section-text-bold mt-4"> <h4 class="section-text-bold mt-4">
CASE Action on next line API
</h4> </h4>
<div class="card-shadow-content"> <div class="card-shadow-content">
<p class="section-text"> <p class="section-text">
A CASE action should start on a line after the possibility. Two API Related Design Patterns and one Best Practice for working with API's
</p> </p>
<a href="/docs/bestpractices/case-actions/" <a href="/tags/api/"
><button class="hero-mid-2 align-self-end">Read Now</button></a ><button class="hero-mid-2 align-self-end">Read Now</button></a
> >
</div> </div>
@ -159,14 +159,14 @@ images: ["images/og-image-fission.png"]
<div class="card-shadow"> <div class="card-shadow">
<span class="card-badge">PATTERN</span> <span class="card-badge">PATTERN</span>
<h4 class="section-text-bold mt-4"> <h4 class="section-text-bold mt-4">
Façade Event Bridge
</h4> </h4>
<div class="card-shadow-content"> <div class="card-shadow-content">
<p class="section-text"> <p class="section-text">
The intent of this pattern is to provide a unified API to a single or a collection of potentially complex subsystems. In the world of interfaces, it is important to preserve (certain) events over multiple implementation of the interface.
</p> </p>
<a <a
href="/docs/patterns/facade-pattern/" href="/docs/patterns/event-bridge-pattern/"
><button class="hero-mid-2 align-self-end">Read Now</button></a ><button class="hero-mid-2 align-self-end">Read Now</button></a
> >
</div> </div>