From 59fe05ae47e1ba5cb27d5ad541da93f12a2af65f Mon Sep 17 00:00:00 2001
From: Ricardo <rick@rmendes.net>
Date: Wed, 4 Mar 2026 19:49:01 +0100
Subject: [PATCH] fix: use pinned property for featuredPosts collection

Renamed from "featured" to "pinned" to avoid conflict with the
"featured" hero image property in MF2/Micropub. Handles both boolean
and string "true" values from YAML frontmatter.

Confab-Link: http://localhost:8080/sessions/bd3f7012-c703-47e9-bfe2-2ad04ce1842d
---
 eleventy.config.js | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/eleventy.config.js b/eleventy.config.js
index abf07a7..4a30de0 100644
--- a/eleventy.config.js
+++ b/eleventy.config.js
@@ -856,12 +856,13 @@ export default function (eleventyConfig) {
       .slice(0, 5);
   });
 
-  // Featured posts — curated selection via `featured: true` frontmatter
+  // Featured posts — curated selection via `pinned: true` frontmatter
+  // Property named "pinned" to avoid conflict with "featured" (hero image) in MF2/Micropub
   eleventyConfig.addCollection("featuredPosts", function (collectionApi) {
     return collectionApi
       .getFilteredByGlob("content/**/*.md")
       .filter(isPublished)
-      .filter((item) => item.data.featured === true)
+      .filter((item) => item.data.pinned === true || item.data.pinned === "true")
       .sort((a, b) => b.date - a.date);
   });