contentbit.dev valid

contentbit (Content Blocks)

Structured Markdown components for LLM-written content. LLMs write plain

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:50:09.040Z. Cached copy · Source on contentbit.dev

# contentbit (Content Blocks)

> Structured Markdown components for LLM-written content. LLMs write plain
> Markdown with directive blocks (:::callout, :::comparison, ...). The library
> parses to a source-mapped AST, validates against per-block schemas with
> file:line:col diagnostics, and renders through React, Astro, or a
> plain-Markdown fallback. npm scope: @contentbit. CLI:
> `npx contentbit@latest init`.

## Start here

- [Authoring rules](https://contentbit.dev/contentbit-guide.md): the generated block-authoring instructions — paste these into a system prompt before writing Content Blocks documents
- [Full documentation as one file](https://contentbit.dev/llms-full.txt)

## Docs

- [Get started with programmatic SEO](https://contentbit.dev/docs): Scaffold Contentbit, define one page family, create a brief, and validate the finished page.
- [Changelog](https://contentbit.dev/docs/changelog): What shipped in each release.
- [Stability and compatibility](https://contentbit.dev/docs/compatibility): The interfaces Contentbit 1.x will keep stable and how changes are classified.
- [LLM & agent authoring](https://contentbit.dev/docs/concepts/llm-authoring): How generated authoring instructions keep schemas, docs, prompts, and validation aligned.
- [Rendering model](https://contentbit.dev/docs/concepts/rendering-model): How parsing, validation, Markdown rendering, and framework adapters fit together.
- [Block syntax moved](https://contentbit.dev/docs/concepts/syntax): The syntax page now lives in the Reference section.
- [Why contentbit?](https://contentbit.dev/docs/concepts/why-contentbit): The content model behind typed Markdown blocks, validation, renderers, and LLM-agent workflows.
- [Why not MDX?](https://contentbit.dev/docs/concepts/why-not-mdx): MDX embeds components. Content Blocks defines a content protocol.
- [Adopt an existing content library](https://contentbit.dev/docs/guides/adoption): Inspect an existing Markdown library, find integrity issues, and generate reviewable Contentbit setup proposals without modifying files.
- [LLM-agent integration](https://contentbit.dev/docs/guides/agents): Give Codex, Claude Code, Cursor, Copilot, and other LLM agents a fast validated writing loop.
- [Astro](https://contentbit.dev/docs/guides/astro): Render validated documents with .astro components — renderer only, one validation path.
- [Defining custom blocks](https://contentbit.dev/docs/guides/custom-blocks): Add project-specific blocks in under 20 lines with defineBlock.
- [Content doctor](https://contentbit.dev/docs/guides/doctor): Run validation, link checks, content-quality heuristics, and optional SEO contract checks as one ranked repair plan.
- [Internal linking](https://contentbit.dev/docs/guides/internal-linking): Build and validate a frontmatter-authored internal-link graph with contentbit links.
- [Plug in your Markdown library](https://contentbit.dev/docs/guides/markdown): One function connects Content Blocks to react-markdown, marked,
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=contentbit.dev · GET /v1/domain/contentbit.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for contentbit.dev:
1. POST https://agentwebmap.com/v1/sites/contentbit.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://contentbit.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/contentbit.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/contentbit.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.