Adapters
Takuhon’s data model and logic live in @takuhon/core, independent of where
your profile is hosted. Adapters connect that core to a specific platform —
its storage, its runtime, and its deploy flow — so the same takuhon.json runs
anywhere.
How it layers
Section titled “How it layers”@takuhon/core— schema, validation, locale resolution, JSON-LD generation, and storage interfaces.@takuhon/api— framework-agnostic Hono handlers and an RFC 7807 error envelope.- Adapter — wires the API to a platform’s storage and runtime, and provides the deploy path.
Available adapters
Section titled “Available adapters”| Adapter | Platform | Status |
|---|---|---|
@takuhon/cloudflare | Cloudflare Workers + KV | Available |
| Static | Prebuilt static output (takuhon build) | Available |
@takuhon/vercel | Vercel | Available (read-only) |
| WordPress | WordPress plugin | Available (Phase 1) |
The Cloudflare adapter is the reference deployment today: GET / (and each
/<locale>/) returns a server-rendered profile page with Schema.org JSON-LD
embedded for crawlers, alongside the public JSON API, Workers KV storage, and a
token-protected admin endpoint. takuhon build produces the same pages as a
prebuilt static site you can host anywhere — no account or KV required. See the
@takuhon/cloudflare adapter README
for routes and the full deploy flow.
The @takuhon/vercel
adapter publishes the same profile page, public API, and JSON-LD on Vercel. It is
read-only — no database, admin UI, or auth: you edit takuhon.json in Git
and Vercel redeploys. The Cloudflare-only surfaces (image uploads, the MCP
endpoint, and the activity badge) are not part of it. Use Cloudflare when you
need the admin editor or those features.
The WordPress adapter ships as a plugin (Phase 1), distributed as a zip on the
project’s GitHub Releases
(tags wordpress-v*). Because WordPress runs PHP — which cannot run the
TypeScript @takuhon/api — the plugin’s admin screen derives the public
artifacts (privacy-filtered profile, JSON-LD, and the server-rendered page) in
the browser with @takuhon/core/@takuhon/api when you save; PHP only stores
and serves them, so none of Takuhon’s logic is reimplemented in PHP. A
takuhon/profile Gutenberg block then embeds the profile from this site or a
remote takuhon API. Phase 1 is a minimal JSON editor; a richer form editor is
planned for Phase 2.
Licensing note
Section titled “Licensing note”Core packages and most adapters are Apache-2.0. The WordPress adapter, when distributed, is GPL-2.0-or-later (required by WordPress derivative-work licensing). The license for your profile content is a separate choice — see Licensing.