Merge pull request #7 from Astro-Craft-Theme/chore/template-debt-cleanup

Template-debt cleanup + pixel icons (batches 1-7, buyer data, icon pixelation)

Author: domidex01

.claude/rules/seo.md

@@ -70,12 +70,13 @@ brackets and cost a normalizing ternary on every render; it was removed.
   none.
 - **`getBreadcrumbSchema` requires a _visible_ breadcrumb nav — it is not a free win.** Emitting a
   `BreadcrumbList` on a page with no on-screen breadcrumb is markup and schema disagreeing, which is
-  the one thing structured data must never do. The builder ships unused **on purpose**: it is the
-  schema counterpart to the `src/components/ui/breadcrumb/` primitive, the same way the other 43
-  primitives ship unused. Build the nav first, then pass the node — don't reach for the builder
-  because it happens to exist. (A dead export with no counterpart is a different matter: an unused
-  helper that sits long enough starts getting cited in other files' docs as though it were part of
-  the pattern, and then it is load-bearing fiction. Delete those.)
+  the one thing structured data must never do. It is **now used**: blog posts pair a `BlogPosting`
+  with a visible breadcrumb nav (built on the `src/components/ui/breadcrumb/` primitive — one of the
+  39 primitives this template ships), so the schema and the on-screen trail agree. That is the bar
+  for any new page — build the nav first, then pass the node; don't reach for the builder because it
+  happens to exist. (A dead export with no counterpart is a different matter: an unused helper that
+  sits long enough starts getting cited in other files' docs as though it were part of the pattern,
+  and then it is load-bearing fiction. Delete those.)
 - Validate output in Google's Rich Results Test before shipping a new schema type.
 
 ## Crawlability & indexation
@@ -94,20 +95,20 @@ brackets and cost a normalizing ternary on every render; it was removed.
   hreflang is only meaningful with 2+ locales. Re-adding i18n means re-adding per-locale alternates +
   `x-default` in `BaseHead` (git history has the old block).
 
-## Content pages (blog) — wire these when the blog route lands
+## Content pages (blog) — shipped with the live blog route
 
-The `blog` + `authors` collections and `@astrojs/mdx` are wired, but **no `/blog/` route ships** —
-a stated decision, not an oversight, and the README says so in the same words so the two can't
-drift. Every project wants its blog shaped differently; the collections are the starting point.
-When the route lands, these three come with it (**deliberately not built** until then — YAGNI):
+The `/blog/` route is **live** (`src/pages/blog/index.astro` + `[slug].astro`) over the `blog` +
+`authors` collections and `@astrojs/mdx`. The three pieces that ride with a content route are built:
 
-- **RSS**: add a dependency-free endpoint (`src/pages/rss.xml.ts`) that maps the `blog` collection
-  to escaped RSS 2.0 — hand-rolled, like everything else in `head`. Link it from `BaseHead`,
-  `llms.txt`, and the footer.
-- **Article schema + `article` prop** on the post page (pattern above).
-- **`heroImage`** is optional in the schema today; make it **required** for a real blog so every post
-  has an OG image, and add `og:image:width/height` from the bundled `ImageMetadata` (BaseHead already
-  emits real dims when you pass an `image`).
+- **RSS**: a dependency-free endpoint (`src/pages/rss.xml.ts`) maps the `blog` collection to escaped
+  RSS 2.0 via the `@js/rss` renderer — hand-rolled like everything else in `head` (no `@astrojs/rss`),
+  self-checked by `src/js/rss.test.ts`. Linked from `BaseHead`, `llms.txt`, and the footer.
+- **Article schema + `article` prop** on the post page (`[slug].astro`): `getArticleSchema` emits a
+  `BlogPosting` with a stable `@id` (`${url}#article`), a `publisher` reference to the site
+  Organization, and `author.url` (from the author's `authorLink`). `dateModified` is emitted **only**
+  when the post has an `updatedDate` — never invented from `datePublished`.
+- **`heroImage` is required** on blog posts (`content.config.ts` — `image()`, not `.optional()`), so
+  every post has an OG image; `BaseHead` emits `og:image:width/height` from the bundled `ImageMetadata`.
 
 ## Images & Core Web Vitals
 

.claude/rules/tailwind.md

@@ -92,7 +92,7 @@ export const button = tv({
 ## `@apply` is allowed here — for shared, cross-cutting classes
 
 This template uses `@apply` inside `@layer components`/`utilities` for reusable semantic classes, and that's
-correct usage: `.h1`, `.description`, `.site-container`, `.form__input`, `.primary-focus`,
+correct usage: `.h1`, `.description`, `.site-container`, `.primary-focus`,
 `.main-text-gradient`. Use `@apply` for a pattern repeated across many unrelated elements; reach for a
 **component** (or `tv`) when the thing has structure/variants. Don't `@apply` to "tidy" a one-off class list.
 
@@ -101,7 +101,7 @@ correct usage: `.h1`, `.description`, `.site-container`, `.form__input`, `.prima
 - `@import "tailwindcss";` (one line). Load plugins with `@plugin "@tailwindcss/forms";`.
 - Declare layer order explicitly: `@layer theme, base, components, utilities;` and import into a layer when
   needed: `@import "./buttons.css" layer(components);`.
-- Native CSS nesting is available (`.form__input { &::placeholder { @apply text-base-400; } }`).
+- Native CSS nesting is available (`.blog-prose { & a { @apply text-info; } }`, as in global.css).
 - Keep the `@theme` token file separate (`tailwind-theme.css`) so it can also be imported into a `.astro`
   `<style>` block.
 

.env.example

@@ -11,3 +11,17 @@ SITE_URL=https://example.com
 # reads. Set this to "production" in your production build environment — and nowhere else, or
 # preview deploys will start failing on the placeholder too.
 # DEPLOY_ENV=production
+
+# --- Contact form -----------------------------------------------------------------------------
+# The /contact/ route is server-rendered and sends through Resend (https://resend.com). Both keys
+# below are read at REQUEST time, so leaving them unset never breaks the build — the form simply
+# reports "not configured yet" until they are present. Create an API key in the Resend dashboard.
+RESEND_API_KEY=re_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+# Where contact submissions are delivered — your own inbox.
+CONTACT_TO_EMAIL=you@example.com
+
+# Optional. The From address on the sent mail. Defaults to Resend's shared onboarding@resend.dev,
+# which ONLY delivers to the Resend account owner's own address (fine for a first smoke test). To
+# send to anyone else, verify your own domain in Resend and set a From address on that domain here.
+# CONTACT_FROM_EMAIL=hello@yourdomain.com