paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 48 Packages Projects Releases Wiki Activity

Fix markdown styling

Browse Source 
Signed-off-by: Johan Haals <johan.haals@gmail.com>
This commit is contained in:
Johan Haals
2022-12-13 14:20:46 +01:00
parent 9b0c053e91
commit cb5393aefe
4 changed files with 61 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/utility-apis.md
+7 -7
View File
@@ -283,14 +283,14 @@ long as they adhere to the contract established by an
implementation they want.
The figure below shows the relationship between
<span style="color: #82b366">different Apps</span>, that provide
<span style="color: #6c8ebf">different implementations</span> of the
<span style="color: #9673a6">FooApi</span>.
<span style="color: #d6b656">Components</span> within Plugins then access the
<span style="color: #9673a6">FooApi</span> via the
<span style="color: #b85450">fooApiRef</span>.
<span class="textGreen" className="textGreen">different Apps</span>, that provide
<span class="textBlue" className="textBlue"> different implementations</span> of the
<span class="textPurple" className="textPurple"> FooApi</span>.
<span class="textYellow" className="textYellow"> Components</span> within Plugins then access the
<span class="textPurple" className="textPurple"> FooApi</span> via the
<span class="textRed" className="textRed"> fooApiRef</span>.
<div style="text-align:center">
<div className="textAlignCenter" class="textAlignCenter">
<img src="../assets/utility-apis-fig1.svg" alt="Figure showing the relationship between utility APIs, the apps that provide them, and the plugins that consume them" />
</div>