@half-built/astro 0.4.2 → 0.5.0

package/README.md

@@ -24,6 +24,23 @@ wider preview concept (the blog's SHOW_DRAFTS builds, for example)
 passes its own gate through the `shown` prop; the component reads no
 consumer config itself.
 
+## WhenPublished and PostLink
+
+`content/WhenPublished.astro` renders its children only when the post
+at `slug` is visible, so a published post can tease one still in
+draft and the passage appears on its own when the target ships.
+`content/PostLink.astro` links to a post by slug and resolves the
+href at build time through `postPath`, so a re-dated post does not
+strand the links pointing at it. Both take the consumer's collection
+as the `posts` prop (the full collection, drafts included, so an
+unknown slug can throw instead of hiding as "still a draft");
+`WhenPublished` also takes the consumer's draft gate as `showDrafts`,
+and `PostLink` accepts an optional `tip` carried as `data-tooltip` for
+the link-tip island. A consumer wraps each in a one-line site
+component that injects `getCollection` and its own gate, the way the
+blog does. The resolvers live in `lib/drafts.ts` for consumers that
+want the logic without the components.
+
 ## Live code colors
 
 `shiki/code-theme` bakes its amber values into every highlighted span

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@half-built/astro",
-  "version": "0.4.2",
+  "version": "0.5.0",
   "description": "Astro components, islands, and pure helpers for the half-built design system.",
   "license": "MIT",
   "repository": {

package/src/components/content/PostLink.astro

@@ -0,0 +1,18 @@
+---
+/* Internal link to a post, addressed by slug rather than by URL, so the
+   href follows the target if its date changes. Pairs with WhenPublished
+   for forward links: put the PostLink inside the wrapper and the
+   passage carries only the slug, twice, with nothing to keep in sync.
+   Moved up from the blog's content/PostLink.astro (owner call
+   2026-09-10); the resolver was already here in lib/drafts. The
+   consumer passes its collection, and may pass `tip`, the hover text
+   the link-tip island reads from data-tooltip. Resolves drafts as well
+   (it has to, see resolvePostHref); the deploy-build guard against a
+   bare link to a draft is a consumer test on the built pages. */
+import { resolvePostHref, type Linkable } from "../../lib/drafts";
+
+interface Props { slug: string; posts: Linkable[]; tip?: string; class?: string }
+const { slug, posts, tip, class: className } = Astro.props;
+const href = resolvePostHref(slug, posts);
+---
+<a href={href} data-tooltip={tip} class={className}><slot /></a>

package/src/components/content/WhenPublished.astro

@@ -0,0 +1,22 @@
+---
+/* Forward-link gate: renders its children only when the post at `slug`
+   is visible in this build. A published post can tease a post that is
+   still a draft, and the passage appears on its own once the target
+   ships, with nothing to revise. Moved up from the blog's
+   content/WhenPublished.astro (owner call 2026-09-10); the logic was
+   already here in lib/drafts. The consumer passes its own collection
+   and its own draft gate, because a package component reads no
+   consumer content or config (the EditorNote precedent). Pass the
+   full collection, drafts included: the lookup has to tell "draft"
+   apart from "no such post", and the latter throws so a typo cannot
+   pass as "still a draft". Astro renders slot children eagerly, so a
+   PostLink inside a hidden passage still resolves; a consumer's guard
+   against a draft link leaking into a deploy build is a test on the
+   built pages, not this gate. */
+import { forwardLinkVisible, type ForwardLinkable } from "../../lib/drafts";
+
+interface Props { slug: string; posts: ForwardLinkable[]; showDrafts?: boolean }
+const { slug, posts, showDrafts = false } = Astro.props;
+const visible = forwardLinkVisible(slug, posts, showDrafts);
+---
+{visible && <slot />}