[libadwaita/wip/exalm/docs: 2/4] doc: Add a Styles & Appearance page

[Alexander Mikhaylenko <alexm src gnome org>]

commit 293d297f2bd4b65b64f975d7958aee715e6599df
Author: Alexander Mikhaylenko <alexm gnome org>
Date:   Sun Dec 26 21:34:46 2021 +0500

    doc: Add a Styles & Appearance page

 doc/libadwaita.toml.in       |   8 ++-
 doc/meson.build              |   1 +
 doc/styles-and-appearance.md | 132 +++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 139 insertions(+), 2 deletions(-)
---
diff --git a/doc/libadwaita.toml.in b/doc/libadwaita.toml.in
index 2dcd4a73..ffca0ffd 100644
--- a/doc/libadwaita.toml.in
+++ b/doc/libadwaita.toml.in
@@ -39,10 +39,14 @@ file_format = "{filename}#L{line}"
 urlmap_file = "urlmap.js"
 content_files = [
   "build-howto.md",
-  "migrating-between-development-versions.md",
-  "migrating-libhandy-1-4-to-libadwaita.md",
+
+  "styles-and-appearance.md",
   "named-colors.md",
   "style-classes.md",
+
+  "migrating-between-development-versions.md",
+  "migrating-libhandy-1-4-to-libadwaita.md",
+
   "visual-index.md",
 ]
 content_images = [
diff --git a/doc/meson.build b/doc/meson.build
index 46c49564..77e83b31 100644
--- a/doc/meson.build
+++ b/doc/meson.build
@@ -7,6 +7,7 @@ expand_content_md_files = [
   'migrating-between-development-versions.md',
   'migrating-libhandy-1-4-to-libadwaita.md',
   'named-colors.md',
+  'styles-and-appearance.md',
   'style-classes.md',
   'visual-index.md',
 ]
diff --git a/doc/styles-and-appearance.md b/doc/styles-and-appearance.md
new file mode 100644
index 00000000..e06560bc
--- /dev/null
+++ b/doc/styles-and-appearance.md
@@ -0,0 +1,132 @@
+Title: Styles & Appearance
+Slug: styles-and-appearance
+
+# Styles & Appearance
+
+## Dark Style
+
+Libadwaita applications can use a light or a dark appearance. This can be used
+to request a darker UI, or to support a system-wide dark style preference if one
+exists.
+
+By default applications use light appearance unless the system prefers dark
+appearance, matching the `ADW_COLOR_SCHEME_PREFER_LIGHT` color scheme. The
+[property@StyleManager:color-scheme] property allows to change this behavior
+when set to:
+
+* `ADW_COLOR_SCHEME_PREFER_DARK`: Use dark appearance unless the system prefers
+  light appearance.
+* `ADW_COLOR_SCHEME_FORCE_DARK`: Always use dark appearance.
+* `ADW_COLOR_SCHEME_FORCE_LIGHT`: Always use light appearance.
+
+<table>
+  <tr>
+    <th>App \ System</th>
+    <th>Prefer Light</th>
+    <th>No Preference</th>
+    <th>Prefer Dark</th>
+  </tr>
+  <tr>
+    <th><tt>FORCE_LIGHT</tt></th>
+    <td>Light</td>
+    <td>Light</td>
+    <td>Light</td>
+  </tr>
+  <tr>
+    <th><tt>PREFER_LIGHT</tt></th>
+    <td>Light</td>
+    <td>Light</td>
+    <td>Dark</td>
+  </tr>
+  <tr>
+    <th><tt>PREFER_DARK</tt></th>
+    <td>Light</td>
+    <td>Dark</td>
+    <td>Dark</td>
+  </tr>
+  <tr>
+    <th><tt>FORCE_DARK</tt></th>
+    <td>Dark</td>
+    <td>Dark</td>
+    <td>Dark</td>
+  </tr>
+</table>
+
+Common use cases:
+
+1. An application wants to use dark UI. Use the `ADW_COLOR_SCHEME_PREFER_DARK`
+   color scheme.
+
+2. An application has a style switcher with the system, light and
+dark states. Use the following color scheme values:
+
+    * System: `ADW_COLOR_SCHEME_PREFER_LIGHT`
+    * Light: `ADW_COLOR_SCHEME_FORCE_LIGHT`
+    * Dark: `ADW_COLOR_SCHEME_FORCE_DARK`
+
+If the system does not provide a style preference, the
+[property@StyleManager:system-supports-color-schemes] property can be used to
+provide a fallback. For example, applications with a system/light/dark switcher
+may want to hide or disable the system value.
+
+All standard GTK and Libadwaita widgets automatically support both styles.
+Applications that use custom drawing or styles may need to ensure the UI
+remains legible in both appearances:
+
+* When possible, use [named colors](named-colors.html) instead of hardcoded
+  colors. For custom drawing, use [method@Gtk.StyleContext.get_color] to get the
+  current text color for your widget, or [method@Gtk.StyleContext.lookup_color]
+  to look up other colors.
+
+* If that's not possible, use the [property@StyleManager:dark] property to check
+  the current appearance and vary the drawing accordingly.
+
+* [class@Application] allows to load additional styles for dark appearance via
+  the `style-dark.css` resource.
+
+## High Contrast
+
+The system can provide a high contrast preference. Libadwaita applications
+automatically sepport it; applications cannot disable it.
+
+High contrast appearance can be combined with the [dark style](#dark-style) and
+is independent from it.
+
+All standard GTK and Libadwaita widgets automatically support the high contrast
+appearance. Applications that use custom drawing or styles may need to support
+it manually.
+
+* Use style classes such as [`.dim-label`](style-classes.html#dim-label) instead
+  of changing widget opacity manually.
+
+* Use the [<code>&#64;borders</code>](named-colors.html#helper-colors) color for
+  borders instead of hardcoded colors.
+
+* The [property@StyleManager:high-contrast] property can be used to check the
+  current appearance.
+
+* [class@Application] allows to load additional styles for high contrast
+  appearance via the `style-hc.css` and `style-hc-dark.css` resources.
+
+## Custom Styles
+
+[class@Application] provides a simple way to load additional styles from
+[struct@Gio.Resource], relative to the application's base path (see
+[method@Gio.Application.set_resource_base_path]).
+
+When using custom styles, applications should be careful to 
+
+The following resources will automatically be loaded if present:
+
+- `style.css` contains styles that are always used.
+- `style-dark.css` contains styles only used with the dark appearance.
+- `style-hc.css` contains styles used with the high contrast appearance.
+- `style-hc-dark.css` contains styles used when both dark and high contrast
+
+Styles are stacked on top of each other: when using dark appearance, both
+`style.css` and `style-dark.css` are loaded, and so on.
+
+## See Also
+
+- [Style Classes](style-classes.html)
+- [Named Colors](named-colors.html)