diff --git a/index.md b/index.md
index 2c700d20..b6300c6a 100644
--- a/index.md
+++ b/index.md
@@ -16,49 +16,62 @@ An OME-Zarr is a file format optimized for storing, viewing, & sharing large ima
 There are two parts to an OME-Zarr:
 
 * **The "Zarr" part describes how the pixel data for the images are laid out**
-* The "OME", which stands for [Open Microscopy Environment](https://www.openmicroscopy.org/), part describes metadata about the pixel data. This includes metadata such as:
-   * spatial relationships
-   * high content screening data
-   * well data
-   * [and more](./specifications/index)!
+* **The "OME" part, which stands for [Open Microscopy Environment](https://www.openmicroscopy.org/), describes metadata about the pixel data. This includes metadata such as:
+  * spatial relationships
+  * high content screening data
+  * well data
+  * [and more](./specifications/index)!
 
 ## Why would I use OME-Zarr?
 
+In general, OME-Zarr is growing as a default [FAIR](https://en.wikipedia.org/wiki/FAIR_data) choice for storing and sharing microscopy images.
+
 OME-Zarr files have two major benefits:
 
-* Chunking is inherent to "Zarr" files. This means "Zarr" files are stored in independently-accessible blocks.
-   * **Storage**: Microscopy images can be quite large and can therefore reach Cloud system storage limits for individual files; the chunked nature of a Zarr can alleviate this issue. Some storage systems may also duplicate byte-equivalent files, so a chunked file like Zarr may save storage space.
-   * **Viewing**: Viewers can target specific chunks to load based upon the current view, reducing lag, & enabling massive images to be viewed within browsers.
-   * **Cost**: When viewing or reading data, the total cost of accessing a Zarr file on the cloud may be less than a more monolithic file format due to the more efficient data access patterns. Ex. A viewer can just access the chunks of the image it needs to display rather than the entire image.
-* "OME-Zarr" is a "Zarr" with embedded standardized metadata in the Open Microscopy Environment (OME) format.
-   * **Sharing**: A standardized imaging metadata format can ease cross-organization file sharing and can therefore aid organizational collaboration and data sharing.
-   * **Interoperability**: Standardized metadata can also enable the interoperability of tools.
+* **Standardization:** "OME-Zarr" is a "Zarr" with embedded standardized metadata in the Open Microscopy Environment (OME) format.
+  * **_Sharing_**: It eases cross-organization file sharing, aiding organizational collaboration and data sharing. Repositories like the [Image Data Resource](https://idr.openmicroscopy.org/) and [BioImage Archive](https://www.ebi.ac.uk/bioimage-archive/) are currently migrating to having OME-Zarr as a standard format for _all_ their data.
+  * **_Interoperability_**: Standardized metadata enables the ability to "mix and match" tools from different organizations, benefiting from the strengths of multiple tools as needed.
+
+* **Parallel access**: Chunking is inherent to "Zarr" files. This means "Zarr" files are stored in independently-accessible blocks.
+  * **_Storage_**: Microscopy images can be quite large and can therefore reach Cloud system storage limits for individual files; the chunked nature of a Zarr can alleviate this issue. Some storage systems may also duplicate byte-equivalent files, so a chunked file like Zarr may save storage space.
+  * **_Viewing_**: Viewers can target specific chunks to load based upon the current view, reducing lag, & enabling massive images to be viewed within browsers.
+  * **_Cost_**: When viewing or reading data, the total cost of accessing a Zarr file on the cloud may be less than a more monolithic file format due to the more efficient data access patterns. Ex. A viewer can just access the chunks of the image it needs to display rather than the entire image.
+
+Of note, both benefits contribute to **_AI-readiness_**: the standardized metadata & access patterns provide a common layer for machine-learning workflows, reducing the friction for developers to build and test models.
+
+The [tools](./tools/index), [data](./data/index), and [ecosystem](./ecosystem/index) may provide a better sense of the range of scientific use cases that may benefit from OME-Zarr. The [publications](./publications/index) page provides a list of publications that have used OME-Zarr in their work.
 
 ## When would I not use OME-Zarr?
 
-* If your file isn't very big and you're working with local data, the current specification of OME-Zarr can be less convenient than a single-file format and the benefits are limited. Planned expansions to the OME-Zarr specification will make it more convenient to work with it in these scenarios (e.g. single-file Zarrs) and add features that might make it beneficial to use OME-Zarr even in these scenarios (e.g. transformations).
-* If your original file is lossy compressed, you will see a large increase in file size as the images are decompressed into OME-Zarr. There is not yet support for transferring lossy compressed image tiles to OME-Zarr. This currently impacts most whole slide image (WSI) formats such as SVS, CZI, and NDPI, which are lossy JPEG compressed by default and see about a 10x size increase into OME-Zarr.
+While the format matures, it may be frustrating to use OME-Zarr in some cases, for example:
+
+* If you are working with small images, not planning to share them and your current tools already work well, then using OME-Zarr may not be necessary. Planned expansions to the specification (such as single-file Zarrs) will make it more convenient in these scenarios.
+
+* If you need specific conditions for which OME-Zarr support is not mature, you may need to use a different file format.
+  * Particularly, if your original file is lossy compressed, you will see a large increase in file size (about an order of magnitude) as the images are decompressed into OME-Zarr, since transferring lossy compressed tiles is not yet supported. This currently impacts most whole slide image (WSI) formats such as SVS, CZI, and NDPI, which are lossy JPEG compressed by default.
 
 ## Who is using OME-Zarr?
 
-These are *some* of the organizations (and their dataset pages) that are using OME-Zarr for their data.
+These are _some_ of the organizations (and their dataset pages) that are using OME-Zarr for their data.
 
-- [Allen Institute](https://bff.allencell.org/datasets)
-- biohub
-- [Broad Institute](https://broadinstitute.github.io/cellpainting-gallery/overview.html)
-- [EMBL - Image Data Resource (IDR)](https://idr.openmicroscopy.org/)
-- [Howard Hughes Medical Institute, Janelia (HHMI)](https://openorganelle.janelia.org/)
-- [Jackson Laboratory (JAX)](https://images.jax.org/)
-- ... [and more](./data/index)
+* [Allen Institute](https://bff.allencell.org/datasets)
+* biohub
+* [Broad Institute](https://broadinstitute.github.io/cellpainting-gallery/overview.html)
+* [EMBL - Image Data Resource (IDR)](https://idr.openmicroscopy.org/)
+* [Howard Hughes Medical Institute, Janelia (HHMI)](https://openorganelle.janelia.org/)
+* [Jackson Laboratory (JAX)](https://images.jax.org/)
+* ... [and more](./data/index)
 
 ## How do I use OME-Zarr?
 
 * Already have a Zarr?
-   * Check out the [tools section](./tools/index)!
+  * Check out the [tools section](./tools/index)!
 * Want to create a Zarr?
-   * Check out the [tools section](./tools/index)!
+  * Check out the [tools section](./tools/index)!
 * Want to see or download a Zarr?
-   * Check out the [data section](./data/index)!
+  * Check out the [data section](./data/index)!
+* Want to cite OME-Zarr/NGFF in your work?
+  * Check out the [publications section](./publications/index)!
 
 ## Have other questions?
 
diff --git a/resources/publications/index.md b/resources/publications/index.md
index 3ab917c1..dfd12201 100644
--- a/resources/publications/index.md
+++ b/resources/publications/index.md
@@ -1,6 +1,142 @@
-Publications
-============
+# Publications
 
-* [OME-NGFF: a next-generation file format for expanding bioimaging data-access strategies](https://www.nature.com/articles/s41592-021-01326-w) 29th November 2021
-* [OME-Zarr: a cloud-optimized bioimaging file format with international community support](https://link.springer.com/article/10.1007/s00418-023-02209-1) 10th July 2023
-* [2024 OME-NGFF workflows hackathon Preprint](https://osf.io/preprints/biohackrxiv/5uhwz_v2) 13 March 2025
+Core publications on NGFF and OME-Zarr. If you plan to cite OME-Zarr in your work, please use one or more of the following references, as appropriate.
+
+- [OME-NGFF: a next-generation file format for expanding bioimaging data-access strategies](https://www.nature.com/articles/s41592-021-01326-w) 29th November 2021
+- [OME-Zarr: a cloud-optimized bioimaging file format with international community support](https://link.springer.com/article/10.1007/s00418-023-02209-1) 10th July 2023
+- [2024 OME-NGFF workflows hackathon Preprint](https://osf.io/preprints/biohackrxiv/5uhwz_v2) 13 March 2025
+
+## Recent publications mentioning NGFF or OME-Zarr
+
+This feed is generated live from Europe PMC and will show the most recent publications that mention NGFF or OME-Zarr in the title, abstract, or keywords.
+
+```{raw} html
+<style>
+  #pubfeed { max-width: 720px; }
+  #pubfeed-status { color: #888; font-size: 0.85em; margin-bottom: 0.5em; }
+  #pubfeed ol { list-style: none; margin: 0; padding: 0; min-height: 18em; }
+  #pubfeed li {
+    padding: 0.75em 0;
+    border-bottom: 1px solid rgba(128,128,128,0.2);
+  }
+  #pubfeed li:first-child { padding-top: 0; }
+  #pubfeed .pub-title { font-weight: 600; text-decoration: none; line-height: 1.4; }
+  #pubfeed .pub-title:hover { text-decoration: underline; }
+  #pubfeed .pub-meta { color: #888; font-size: 0.85em; margin-top: 0.25em; }
+  #pubfeed .pub-authors {
+    color: #666; font-size: 0.85em; margin-top: 0.15em;
+    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
+  }
+  #pubfeed-nav {
+    display: flex; align-items: center; justify-content: space-between;
+    gap: 1em; margin-top: 1em;
+  }
+  #pubfeed-nav button {
+    padding: 0.4em 1em; font-size: 0.9em; cursor: pointer;
+    background: transparent; color: inherit;
+    border: 1px solid rgba(128,128,128,0.4); border-radius: 6px;
+  }
+  #pubfeed-nav button:hover:not(:disabled) { border-color: rgba(128,128,128,0.8); }
+  #pubfeed-nav button:disabled { opacity: 0.35; cursor: default; }
+  #pubfeed-page { color: #888; font-size: 0.85em; }
+</style>
+
+<div id="pubfeed">
+  <p id="pubfeed-status">Loading recent publications…</p>
+  <ol id="pubfeed-list"></ol>
+  <div id="pubfeed-nav" hidden>
+    <button id="pubfeed-prev">← Prev</button>
+    <span id="pubfeed-page"></span>
+    <button id="pubfeed-next">Next →</button>
+  </div>
+</div>
+
+<script>
+(async function () {
+  const QUERY = '"NGFF" OR "OME-Zarr"';
+  const PAGE = 4;
+  const BASE = "https://www.ebi.ac.uk/europepmc/webservices/rest/search";
+
+  const status = document.getElementById("pubfeed-status");
+  const list = document.getElementById("pubfeed-list");
+  const nav = document.getElementById("pubfeed-nav");
+  const prevBtn = document.getElementById("pubfeed-prev");
+  const nextBtn = document.getElementById("pubfeed-next");
+  const pageLabel = document.getElementById("pubfeed-page");
+
+  const pages = [];          // cached results per page index
+  const cursors = ["*"];     // cursor to fetch page i
+  let total = null;
+  let current = 0;
+  let loading = false;
+
+  function urlFor(cursor) {
+    return BASE +
+      "?query=" + encodeURIComponent(QUERY) +
+      "&format=json&resultType=lite" +
+      "&pageSize=" + PAGE +
+      "&sort=" + encodeURIComponent("P_PDATE_D desc") +
+      "&cursorMark=" + encodeURIComponent(cursor);
+  }
+
+  function render(results) {
+    list.innerHTML = results.map(function (p) {
+      const link = p.doi
+        ? "https://doi.org/" + p.doi
+        : "https://europepmc.org/article/" + p.source + "/" + p.id;
+      const authors = (p.authorString || "").length > 90
+        ? p.authorString.slice(0, 90).replace(/,?\s*$/, "") + "…"
+        : (p.authorString || "");
+      const journal = p.journalTitle ? " · " + p.journalTitle : "";
+      const date = p.firstPublicationDate || p.pubYear || "";
+      return '<li>' +
+        '<a class="pub-title" href="' + link + '" target="_blank" rel="noopener">' +
+          (p.title || "Untitled") + '</a>' +
+        (authors ? '<div class="pub-authors">' + authors + '</div>' : '') +
+        '<div class="pub-meta">' + date + journal + '</div>' +
+      '</li>';
+    }).join("");
+  }
+
+  function totalPages() {
+    return total ? Math.ceil(total / PAGE) : 1;
+  }
+
+  function updateNav() {
+    nav.hidden = false;
+    pageLabel.textContent = "Page " + (current + 1) + " of " + totalPages();
+    prevBtn.disabled = loading || current === 0;
+    nextBtn.disabled = loading || current >= totalPages() - 1;
+  }
+
+  async function show(i) {
+    if (loading) return;
+    if (pages[i]) { current = i; render(pages[i]); updateNav(); return; }
+
+    loading = true; updateNav();
+    try {
+      const r = await fetch(urlFor(cursors[i]));
+      const j = await r.json();
+      const results = j.resultList?.result || [];
+      if (total === null) total = j.hitCount ?? results.length;
+      pages[i] = results;
+      if (j.nextCursorMark) cursors[i + 1] = j.nextCursorMark;
+      current = i;
+      status.textContent = total + " publications";
+      render(results);
+    } catch (e) {
+      status.textContent = "Could not load publications.";
+      console.warn(e);
+    } finally {
+      loading = false;
+      updateNav();
+    }
+  }
+
+  prevBtn.addEventListener("click", function () { if (current > 0) show(current - 1); });
+  nextBtn.addEventListener("click", function () { show(current + 1); });
+
+  show(0);
+})();
+</script>
+```