Add significant padding to articles.

Author: JimBobSquarePants

api/index.md

@@ -1,3 +1,9 @@
 # API Documentation
 
-The API documentation is automatically generated from source-code-level comments. Often, more information can be found by looking into the [source code](https://github.com/sixlabors) itself.
+The API documentation is generated from the public source comments for the Six Labors libraries. Use it when you need exact type names, overloads, constructor signatures, enum values, default behavior, inherited members, and namespace-level navigation.
+
+These reference pages are designed to sit alongside the article guides. Start with the articles when you are learning a feature or choosing an approach, then use the API reference when you need the precise member contract for implementation work.
+
+The API reference covers the libraries documented on this site, including ImageSharp, ImageSharp.Drawing, ImageSharp.Web, Fonts, and PolygonClipper. Each product area is grouped by namespace so you can move from high-level entry points, such as image processing extensions or drawing canvas APIs, down to the supporting options, primitives, and model types.
+
+When a reference page does not answer a design question, check the matching article section first. The source repositories remain available on [GitHub](https://github.com/sixlabors) for contributors and for cases where you need to inspect implementation details that are intentionally not part of the public API contract.

articles/fonts/caretsandselection.md

@@ -144,3 +144,10 @@ Use the full [`TextMetrics`](xref:SixLabors.Fonts.TextMetrics) overloads for sel
 Per-line selection uses the line-box height rather than per-glyph height, which matches normal text editor and browser behavior: selecting mixed font sizes on the same line paints a consistent line-height rectangle rather than one rectangle per glyph height. The selection geometry stays visually stable across mixed fonts and font sizes.
 
 For a wider tour of the measurement model and how line metrics are derived, see [Measuring Text](measuringtext.md).
+
+### Practical guidance
+
+- Paint the selection rectangles returned by the API instead of reconstructing selection geometry yourself.
+- Keep anchor and focus as logical text positions; let the metrics map them into visual rectangles.
+- Use editor interaction mode when selections must include terminal blank lines.
+- Test mixed LTR/RTL selections with real strings, not only simple Latin text.

articles/fonts/checkglyphcoverage.md

@@ -44,3 +44,10 @@ Glyph coverage is only the first question. A font can contain glyphs for individ
 Emoji and complex scripts are the usual cases where this distinction matters. A visible emoji can be a grapheme made from several code points, and Arabic, Indic, or Southeast Asian scripts can require shaping features that are not captured by a one-code-point probe.
 
 For the conceptual fallback guidance, see [Fallback Fonts and Multilingual Text](fallbackfonts.md). For face-level coverage inspection, see [Font Metrics](fontmetrics.md).
+
+### Practical guidance
+
+- Use coverage checks to choose fallback candidates, not to prove final rendered quality.
+- Test grapheme clusters such as emoji sequences as whole strings with production layout options.
+- Prefer face-level coverage inspection when building diagnostics or font picker tooling.
+- Keep fallback order intentional so broad-coverage fonts do not hide preferred design choices.

articles/fonts/colorfonts.md

@@ -103,3 +103,10 @@ Color-font support is part of text layout, not just final painting. If you measu
 Use the same [`TextOptions`](xref:SixLabors.Fonts.TextOptions) instance for both [`TextMeasurer`](xref:SixLabors.Fonts.TextMeasurer) and [`TextRenderer`](xref:SixLabors.Fonts.Rendering.TextRenderer) when you want a guaranteed match.
 
 For renderer implementation details, see [Custom Rendering](customrendering.md). For fallback across multiple families, see [Fallback Fonts and Multilingual Text](fallbackfonts.md).
+
+### Practical guidance
+
+- Use the same `ColorFontSupport` setting when measuring and rendering.
+- Test the actual emoji or color glyph set you intend to support; technologies vary by font.
+- Decide fallback order deliberately when both monochrome and color families can cover the same text.
+- Custom renderers should handle painted glyph callbacks even if most text is outline-based.

articles/fonts/customrendering.md

@@ -143,3 +143,10 @@ public TextDecorations EnabledDecorations()
 ```
 
 This makes it possible to render underline, overline, or strikeout using the same backend as the glyph outlines.
+
+### Practical guidance
+
+- Implement only the renderer callbacks your backend can honor correctly.
+- Keep layout in Fonts and rendering in your backend; do not recompute shaping inside the renderer.
+- Honor layer and paint callbacks when color-font output matters.
+- Use decoration callbacks instead of drawing underlines from guessed metrics.

articles/fonts/fallbackfonts.md

@@ -108,3 +108,10 @@ If a script needs shaping support, make sure the selected font actually supports
 - Mixing many broad-coverage fonts can make fallback order hard to reason about.
 
 If layout still looks wrong after fallback is configured, see [Troubleshooting](troubleshooting.md).
+
+### Practical guidance
+
+- Put the preferred design family first, then add fallbacks in the order you want missing glyphs to be searched.
+- Use `TextRuns` when a specific grapheme range must use a specific font rather than normal fallback.
+- Validate fallback with real content, especially emoji, RTL text, CJK text, and combining marks.
+- Remember that fallback solves missing glyphs; it does not guarantee matching style, metrics, or shaping behavior.

articles/fonts/fittexttowidth.md

@@ -50,3 +50,10 @@ For interactive systems, consider a two-stage search: probe coarse sizes first,
 >This example is intentionally naive. It remeasures from scratch on each iteration to keep the recipe easy to follow. Production layout engines would usually cache measurements, font instances, or intermediate fit results instead of doing a full linear probe every time.
 
 See [Measuring Text](measuringtext.md) and [Text Layout and Options](textlayout.md) for the fuller discussion.
+
+### Practical guidance
+
+- Fit with the same options you will use to render.
+- Define a minimum readable size before starting the search.
+- Use wrapping or truncation when shrinking would make the text unusable.
+- Cache fit results when the same string, font family, and target width repeat often.

articles/fonts/fontmetadata.md

@@ -113,3 +113,10 @@ FontDescription description = font.FontMetrics.Description;
 For loading fonts into collections, see [Loading Fonts and Collections](gettingstarted.md). For working with installed machine fonts, see [System Fonts](systemfonts.md).
 
 If you want the face-level metrics that drive layout and glyph inspection rather than just the descriptive metadata, see [Font Metrics](fontmetrics.md).
+
+### Practical guidance
+
+- Use metadata inspection before loading untrusted or user-supplied font files into normal collections.
+- Store invariant names for stable configuration and localized names for UI.
+- Inspect family styles before assuming bold or italic faces are available.
+- Use font paths for diagnostics, not as the only identity for a face.

articles/fonts/fontmetrics.md

@@ -229,3 +229,10 @@ Use [`FontMetrics`](xref:SixLabors.Fonts.FontMetrics) when you care about:
 - direct glyph inspection
 
 For face names and other descriptive metadata, see [Font Metadata and Inspection](fontmetadata.md). For variable-font usage, see [Variable Fonts](variablefonts.md).
+
+### Practical guidance
+
+- Use font metrics when layout, decoration, glyph coverage, or variation axes matter.
+- Use font descriptions when the question is identity, naming, style, or version metadata.
+- Treat glyph availability as a layout input, not as a guarantee of final script quality.
+- Cache metrics-derived decisions with the font face and variation values that produced them.

articles/fonts/gettingstarted.md

@@ -121,6 +121,13 @@ Font font = family.CreateFont(
 
 The active variation values become part of the [`Font`](xref:SixLabors.Fonts.Font) instance, so the same family can be reused to create multiple design-space instances.
 
+### Practical guidance
+
+- Use a private `FontCollection` when output must be stable across machines.
+- Use `SystemFonts` for host-dependent behavior such as diagnostics, user font pickers, or "use what is installed here" workflows.
+- Create `Font` instances for the size, style, culture, and variation values you actually intend to measure or render.
+- Keep font loading separate from per-request or per-frame layout work when the same files are reused.
+
 ### Next steps
 
 - Use [Measuring Text](measuringtext.md) when you need layout metrics before rendering.