feature: content collections

[jurgenbelien]

Changes

Associated issue

How to test

Checklist

• I have performed a self-review of my own code
• I have made sure that my PR is easy to review (not too big, includes comments)
• I have made updated relevant documentation files (in project README, docs/, etc)
• I have added a decision log entry if the change affects the architecture or changes a significant technology
• I have notified a reviewer

[cloudflare-workers-and-pages]

Deploying head-start with    Cloudflare Pages

Latest commit:	63a800d
Status:	✅  Deploy successful!
Preview URL:	https://86fbdcdc.head-start.pages.dev
Branch Preview URL:	https://feat-content-collections.head-start.pages.dev

View logs

[jurgenbelien]

• Consider paths as identifiers for entries in collections, instead of pure slugs or ids, for those items that have routes, ie. /en/files/...
• Collection block:
  • Specify type of collection
  • Specify sorting
  • Specify limit
  • Layout (?)

type CollectionItem = {
  recordId,
  id, // path,
  type,
  locale,
  publishedAt,
}

[jurgenbelien]

Suggested change

	.then(entries => normalizeEntries(entries, collection))
	.then(entries => normalizeEntries<typeof entries[number]>(entries, collection))

Without it, entries might become a union of collection entries.