diff --git a/content/how-tos/ci-logs.md b/content/how-tos/ci-logs.md
new file mode 100644
index 0000000..4984a61
--- /dev/null
+++ b/content/how-tos/ci-logs.md
@@ -0,0 +1,20 @@
+---
+title: "How do I access CI logs?"
+---
+
+{{< admonition warning >}}
+This is a draft document.
+{{< /admonition >}}
+
+Most packages use _continuous integration_ (CIs) to ensure that new code contributions don't break existing functionality.
+CIs do things like run code style checks, run unit tests on different operating systems or different dependency versions, and build documentation websites.
+Frequently, when you contribute bugfixes, new features, or documentation changes to a packages, one or more of the CIs will fail.
+Below, we show how to figure out _why_ they failed, and what to do to fix them.
+
+<!-- TODO screenshots of CIs with the doc build broken (CircleCI) -->
+
+<!-- TODO screenshots of CIs with the doc build broken (readthedocs) -->
+
+<!-- TODO screenshots of CIs with a GitHub actions unit test broken -->
+
+<!-- TODO screenshots of CIs with an azure-pipelines unit test broken -->