Sample Issue — Development Content

This is development content. It is not a TechRoom360 issue, it was never sent to anyone, and nothing below is editorial. It exists so the content pipeline can be verified end to end, and it should be deleted before launch.

What this file verifies

Each section below exercises a specific part of the pipeline described in docs/content-system.md.

• Frontmatter parses and validates against the issue schema
• The body compiles as MDX
• The allowlisted components resolve
• The content API returns the issue by slug, by number, and in listings
• /newsletter/sample-development-issue renders and generates metadata

Base elements

Regular prose, with inline code, strong emphasis, and a link to the about page alongside an external link.

A blockquote, which is distinct from the Quote component below — this one cites material, that one is an editorial pull quote.

1. Ordered lists work
2. So do nested structures
3. And so does a third item

Code blocks

The validator rejects import and export statements in content, but only outside fenced code — a technical publication needs to print them. If this file builds, the fence handling is working:

import { getLatestIssue } from "@/lib/content";

export async function example() {
  const latest = await getLatestIssue();
  return latest?.title ?? "no issues yet";
}

Allowlisted components

SubscribeCta is the mid-article marker (O-020) — an author places it wherever a specific issue earns a second ask, and it reuses the one subscription flow rather than a second one:

Figure is in the allowlist and typechecks, but it is not exercised here — it renders through next/image and there is no image asset in public/ yet.

Not verified by this file

• Draft exclusion, which needs status: draft and a production build
• Topic pages, the archive, RSS and search, which are not built yet
• Email rendering, which arrives with the Kit integration