diff --git a/content/blog/2024-06-28-doc-include.md b/content/blog/2024-06-28-doc-include.md
new file mode 100644
index 0000000..a075a70
--- /dev/null
+++ b/content/blog/2024-06-28-doc-include.md
@@ -0,0 +1,127 @@
++++
+title = "#![doc = include_str!()] with intra-doc links"
+authors = ["Daniel McNab"]
++++
+
+Creating crate level documentation by [including](https://doc.rust-lang.org/rustdoc/write-documentation/the-doc-attribute.html#the-doc-attribute) your README can lower maintenance burden, as you do not need to manually keep the crate level docs synchronised.
+However, when writing this documentation, you will also want to link directly to some mentioned [items][].
+These links need to work in all the places that the README is rendered, such as on your package's <https://crates.io> homepage, in addition to in rustdoc output.
+To achieve this, you can link to the online documentation for the items:
+
+```md
+To get started with foobar, use the [`frobnicate`][] function.
+
+[`frobnicate`]: https://docs.rs/foobar/latest/foobar/fn.frobnicate.html
+```
+
+This would however mean that users of `cargo doc` will be redirected to your crate's online docs (as opposed to their local docs) when clicking on that link.
+It is however possible to make links in included markdown files behave as intra-doc links, by adding a second link reference definition in the documentation comment.
+This must be placed *before* the `doc = include_str!()` line, for example:
+
+```rust
+//! [`frobnicate`]: frobnicate
+#![doc = include_str("../README.md")]
+```
+
+This means that the link has the expected link target on <https://crates.io> *and* in rustdoc (including on <https://docs.rs>).
+This trick works because when there are duplicate markdown link reference definitions, ["the first one takes precedence"](https://spec.commonmark.org/0.31.2/#example-204).
+rustdoc sees the intra-doc link before the link to the online docs, and so uses the intra-doc link.
+However, when the README is rendered standalone, only the link reference definition for the online docs is present, and so that target is used.
+
+### Example
+
+For an example of both of these techniques in action, see the Android Trace crate (`android_trace`).
+In particular, the text of interest is: "the main entry point to the library is **AndroidTrace**".
+You can observe that this link goes to version 0.1.1 on the docs page, but version 0.1.0 elsewhere.
+
+- [GitHub rendered readme](https://github.com/linebender/android_trace/blob/v0.1.1/android_trace/README.md)
+- [crates.io page](https://crates.io/crates/android_trace/0.1.1)
+- [docs.rs page](https://docs.rs/android_trace/0.1.1/android_trace/)
+
+And the corresponding source code:
+
+- [README.md](https://github.com/linebender/android_trace/blob/v0.1.1/android_trace/README.md?plain=1)
+- [lib.rs](https://github.com/linebender/android_trace/blob/v0.1.1/android_trace/src/lib.rs)
+
+The links have since been updated to use `latest`, but the direct link being to version 0.1.0 shows how this pattern works.
+
+### Getting external documentation links
+
+rust-analyzer has an "Open External Docs" command when you have an item selected.
+This will open the online documentation for the selected item, generally on <https://docs.rs>.
+This works even if the item is yet to be published, in which case it will open the URL where the item would be.
+You may wish to replace the resolved version number in the URL with `latest`, e.g. `https://docs.rs/foobar/latest/foobar/`
+
+### Limitations
+
+`#![doc = include_str!("../README.md")]` has two main relevant limitations which you may need to work around.
+
+The first of these is in code blocks.
+Normal rustdoc examples can include hidden setup lines, starting with a `#` character.
+These will not be rendered by rustdoc.
+
+````md
+```rust
+# use foobar::frobnicate;
+frobnicate();
+```
+````
+
+However, other markdown renderers do not support this extension, so the example above will be rendered as something like:
+
+```rust
+# use foobar::frobnicate;
+frobnicate();
+```
+
+Unfortunately, I am not aware of a workaround for this; my current best suggestion is to avoid using these hidden lines in your README.
+Doctests in included markdown files do also have some diagnostics issues, as reported in [rust-lang/rust#81070](https://github.com/rust-lang/rust/issues/81070).
+
+The second limitation is with file links, such as a link to your license file of the form `[LICENSE-MIT](LICENSE-MIT)` (as recommended in [C-PERMISSIVE][]).
+This is because rustdoc does not support relative file links in Markdown.
+This can be solved by using the "opposite" of this trick - you can use a web link in your `lib.rs`, and a file link in the README.
+
+## A second trick
+
+READMEs contain some content which are not expected to be present in a crate's documentation.
+For example, a top-level title, which would duplicate the `crate foobar` header added by rustdoc.
+This can be resolved by using css in your documentation to hide these items; rustdoc allows embedding CSS in your documentation.
+However, this should only be included in your `lib.rs`, so that the header is shown in other contexts.
+
+```rs
+//! <style>
+//! .rustdoc-hidden { display: none; }
+//! </style>
+```
+
+Any text in the README which should be excluded from your docs page can then be surrounded by a `div` with the `rustdoc-hidden` class, for example:
+
+```md
+<div class = "rustdoc-hidden">
+
+# Foobar
+
+</div>
+```
+
+As far as I'm aware, this does not have any accessibility considerations, as browsers will not make `display: none` items available in their accessibility tree.
+
+Tracing Android Trace (see [above](#example)) also uses this trick to hide the license section from the crate docs.
+The license information is already present in the crate's info box.
+
+## Conclusion
+
+Using `#![doc = include_str!("../README.md")]` can integrate nicely with intra-doc links, if you use some tricks.
+I believe that this pattern reduces the quality gap between bespoke documentation in `lib.rs` enough that using README includes becomes the right pattern for most crates.
+This avoids the maintenance burden of needing to ensure that text in the crate level docs and the README do not become out-of-sync.
+I intend to evaluate this technique by applying it across Linebender crates.
+It may still be better to have bespoke documentation for each location, for projects which can afford the maintenance costs of that solution.
+But for other projects, this can provide an easy way to improve their crate level documentation.
+
+These patterns can also be applied when including non-`README` markdown documents.
+I suggest linking to this post when using these patterns, to allow future readers of your code to understand the technique being used.
+
+Discuss on [the Linebender Zulip](https://xi.zulipchat.com/#narrow/stream/181284-blogging/topic/.23!.5Bdoc.20.3D.20include_str!.28.29.5D.20with.20intra-doc.20links).
+
+[items]: https://doc.rust-lang.org/reference/items.html
+[C-PERMISSIVE]: https://rust-lang.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive
diff --git a/sass/main.scss b/sass/main.scss
index 2511708..a48b120 100644
--- a/sass/main.scss
+++ b/sass/main.scss
@@ -104,25 +104,25 @@ blockquote {
 blockquote>:last-child {
   margin-bottom:0
 }
-pre,
-code {
-  font-size:15px;
-  border:1px solid #e8e8e8;
-  border-radius:3px;
-  background-color:#eef
-}
-code {
-  padding:1px 5px
-}
-pre {
-  padding:8px 12px;
-  overflow-x:auto
-}
-pre>code {
-  border:0;
-  padding-right:0;
-  padding-left:0
-}
+// pre,
+// code {
+//   font-size:15px;
+//   border:1px solid #e8e8e8;
+//   border-radius:3px;
+//   background-color:#eef
+// }
+// code {
+//   padding:1px 5px
+// }
+// pre {
+//   padding:8px 12px;
+//   overflow-x:auto
+// }
+// pre>code {
+//   border:0;
+//   padding-right:0;
+//   padding-left:0
+// }
 .wrapper {
   max-width:-webkit-calc(800px - (30px * 2));
   max-width:calc(800px - (30px * 2));
@@ -588,4 +588,4 @@ table td {
 }
 .list-post-title {
   font-size: 120%;
-}
\ No newline at end of file
+}