Astro

npm install @nohead/astro

​

Content collections

// src/content.config.ts
import { defineCollection } from "astro:content"
import { noheadLoader } from "@nohead/astro"

// Astro reads .env into import.meta.env, not process.env.
const apiKey = import.meta.env.NOHEAD_API_KEY

export const collections = {
  people: defineCollection({
    loader: noheadLoader({ collection: "people", apiKey }),
  }),
  posts: defineCollection({
    loader: noheadLoader({ collection: "posts", expand: ["cover"], body: "body", apiKey }),
  }),
}

• Rich text reads as HTML, for <Fragment set:html={post.data.summary} />. body names one rich text field that moves out of data for render(entry) to render as <Content />. With richText: "markdown", rich text reads as Markdown and that field goes through Astro’s own Markdown pipeline (your plugins, syntax highlighting, headings).
• Assets named in expand replace their ID with the asset: its image_url, width, height, alt and the rest, ready for <Image> through imageMetadata and the image service.
• Relations are references, for getEntry, to the Astro collection named like the related one, so define a collection for every one that relations point to. If you load it under another name, say so: references: { people: "authors" }.
• The record’s own times are in data too: published_at (when it was published; publishing again moves it), created_at and updated_at, for feeds and a sitemap’s lastmod. A date readers see, such as a post’s, is better a date field of its own: Content modelling explains why.
• Empty fields are left out of data, so they are optional.
• Dates without a time become Dates at midnight UTC, as Astro makes front-matter dates. Format them in UTC, date.toLocaleDateString("en-GB", { timeZone: "UTC" }), or west of Greenwich they show as the day before.
• Order: Astro keeps no order for a collection, so sort entries in the page: posts.sort((a, b) => b.data.date.valueOf() - a.data.date.valueOf()).
• Published records are the ones that load, so a published-only key is enough. filter adds conditions, such as { featured: true }, and filter: { published_at: undefined } loads every record, for a key that reads unpublished ones.

​

Schema and types

• Text and rich text fields are strings (with richText: "document", rich text is the API’s document object), numbers are numbers, dates are Dates, enums are their options, booleans are boolean (false when unset) and JSON is unknown. A multiple field is an array.
• A required field is required and the others optional. An expanded asset or relation is always optional, since one deleted or unpublished since is left out.
• A relation is a reference() to its collection, and an expanded one is { id, data }. An asset that isn’t expanded stays its ID.

​

From the schema file

import { defineCollection } from "astro:content"
import { noheadLoader } from "@nohead/astro"

const posts = defineCollection({
  loader: noheadLoader({
    collection: "posts",
    schemaFile: "nohead.schema.yaml",
    apiKey: import.meta.env.NOHEAD_API_KEY,
  }),
})

​

Your own schema

​

Builds and changes

​

Images

---
import { Image } from "astro:assets"
import { imageMetadata } from "@nohead/astro"

const cover = imageMetadata(post.data.cover)
---
{cover && <Image src={cover} widths={[480, 960]} sizes="30rem" alt={post.data.cover?.alt ?? ""} />}

​

Source