Documentation ecosystems

Boring Doc is ecosystem-agnostic: every table, the search index, the comparison engine and the UI are keyed by ecosystem. Flutter is live; the ecosystems below are planned and list the authoritative sources their adapters will read.

Official sources
Adapters
Shared pipeline
Validation & policy
Same UI

Flutter

Dart active

Google's UI toolkit for mobile, web, desktop and embedded apps.

Adapters

flutter-releases, flutter-changelog, flutter-website, flutter-api-index

Learning topics

Docs Repository Releases

React Native

TypeScript planned

Build native apps with React.

facebook/react-native-website (docs markdown) — documentation pages, versioned docs folders
GitHub Releases + CHANGELOG.md — versions, release notes, breaking changes sections
Upgrade Helper — template diffs between versions

Docs Repository Releases

Android

Kotlin planned

Android platform and Jetpack libraries.

AndroidX release notes — library versions, behaviour changes, deprecations
Android platform release notes — platform versions, behaviour changes for apps
androidx/androidx source — source diffs, API text files (api/*.txt) for API-level comparison

Docs Repository Releases

Jetpack Compose

Kotlin planned

Android's declarative UI toolkit.

Compose release notes — versions, new APIs, deprecations
androidx compose API files — verified public-API diffs between versions

Docs Repository Releases

Swift & SwiftUI

Swift planned

Apple's language and declarative UI framework.

swiftlang/swift CHANGELOG.md — language versions and changes (SE proposals)
swift-evolution — proposal status, implemented-in version
Apple release notes — SDK/framework deprecations

Docs Repository Releases

React

TypeScript planned

The library for web and native user interfaces.

reactjs/react.dev (docs markdown) — documentation pages
facebook/react CHANGELOG.md + Releases — versions, release notes, breaking changes

Docs Repository Releases

Next.js

TypeScript planned

The React framework for the web.

vercel/next.js docs folder — documentation pages (MDX)
GitHub Releases — versions and release notes
Upgrade guides / codemods — migration instructions

Docs Repository Releases

How an ecosystem is added

Scaffold
One command creates the adapter folder (built on the generic GitHub docs + releases adapters) and an empty topic folder.
pnpm new-ecosystem react-native "React Native" --docs-repo facebook/react-native-website --docs-root docs --releases-repo facebook/react-native
Parse what is different
Incremental page sync, snapshots, deletions, versions and heuristically classified release notes come for free. Add parsers only for formats the project invents (breaking-change guides, API indexes, changelogs).
Register
Add the ecosystem to the registry and its topics to the content registry. The TypeScript compiler enforces the nine-section topic structure.
Ingest
Run the pipeline for the new source keys; validation, publishing policy and search indexing behave exactly as they do for Flutter.
pnpm ingest --source react-native-releases

src/lib/sources/registry.ts — a planned ecosystem becoming active

typescript

export const reactNativeEcosystem: EcosystemDefinition = {
  key: "react-native",
  name: "React Native",
  tagline: "Build native apps with React.",
  language: "TypeScript",
  status: "active",
  adapters: reactNativeAdapters,   // from src/lib/sources/react-native
  links: { docs: "https://reactnative.dev/docs", repo: "https://github.com/facebook/react-native", releases: "https://github.com/facebook/react-native/releases" },
};

Full guide: docs/ADDING-AN-ECOSYSTEM.md