@riebeckite/plugin-taxonomy 0.0.6

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright Rerurate_514
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,227 @@
+# @riebeckite/plugin-taxonomy
+
+Build-time tag and folder taxonomy for Riebeckite: listing data, per-term
+RSS / Atom / JSON feeds, related-tag navigation, and SEO metadata. No
+client-side JavaScript is required.
+
+[日本語](./README_ja.md)
+
+## Overview
+
+`taxonomy()` reads the manifest's public entries and produces two sets of
+listing terms with the Core collection contract (`buildContentCollections`):
+
+- **Tag terms** group by `tags` under `/tags/<slug>`.
+- **Folder terms** group by folder under `/folders/<path>`.
+
+Entries always link through their resolved `permalink`; the plugin never
+reconstructs a URL from a slug.
+
+The plugin owns data, feeds, and SEO only. It deliberately does **not** register
+application routes. Per-term feeds are written as static files through the
+build's generated-output sink, and an app renders `/tags/<tag>` and
+`/folders/<path>` from the exported helpers (see
+[App-route wiring](#app-route-wiring)).
+
+## Usage
+
+```ts
+import { defineConfig } from "@riebeckite/core";
+import { taxonomy } from "@riebeckite/plugin-taxonomy";
+
+export default defineConfig({
+  // ...
+  plugins: [
+    taxonomy({
+      tags: true,
+      folders: true,
+      related: true,
+      folderIndexes: true,
+    }),
+  ],
+});
+```
+
+## Options
+
+| Option | Type | Default | Description |
+| ------ | ---- | ------- | ----------- |
+| `tags` | `boolean` | `true` | Generate tag terms |
+| `folders` | `boolean` | `true` | Generate folder terms |
+| `tagsBasePath` | `string` | `"/tags"` | Tag listing prefix |
+| `foldersBasePath` | `string` | `"/folders"` | Folder listing prefix |
+| `folderDepth` | `number` | `0` | Folder grouping depth; `0` keeps the full path |
+| `minEntries` | `number` | `1` | Drop terms with fewer entries |
+| `related` | `boolean` | `true` | Compute related-tag navigation |
+| `relatedLimit` | `number` | `8` | Maximum related tags per tag |
+| `folderIndexes` | `boolean` | `false` | Resolve `<folder>/index.md` to `/<folder>` |
+| `feeds` | `{ rss?, atom?, json? }` | all `true` | Per-term feed formats |
+| `feedLimit` | `number` | `50` | Maximum entries per feed |
+| `resolveTitle` | `(context) => string` | `#value` / path | Custom term title |
+| `className` | `string` | `"rr-taxonomy"` | Root CSS class of page fragments |
+| `dataEndpoint` | `string` | `"/taxonomy/index.json"` | JSON data endpoint path |
+
+## Data endpoint
+
+The plugin registers one JSON endpoint (the endpoint contract is mounted by the
+HonoX integration, so it never contains framework routing itself):
+
+```
+GET /taxonomy/index.json
+```
+
+```json
+{
+  "tags": [
+    {
+      "kind": "tag",
+      "value": "featured",
+      "title": "#featured",
+      "path": "/tags/featured",
+      "permalink": "/tags/featured",
+      "count": 1,
+      "entries": [{ "slug": "example", "permalink": "/notes/example", "title": "Example Note", "updated": null, "summary": "..." }],
+      "related": [],
+      "feeds": { "rss": "/tags/featured/feed.xml", "atom": "/tags/featured/atom.xml", "json": "/tags/featured/feed.json" }
+    }
+  ],
+  "folders": []
+}
+```
+
+The payload is a deterministic, JSON-safe projection: it never includes rendered
+HTML, so it is safe to ship to an app route or a browser.
+
+## Generated feeds
+
+At build time the plugin emits one feed per term and format through
+`context.output.emit`:
+
+| Format | Path |
+| ------ | ---- |
+| RSS 2.0 | `/tags/<slug>/feed.xml` |
+| Atom | `/tags/<slug>/atom.xml` |
+| JSON Feed 1.1 | `/tags/<slug>/feed.json` |
+
+Folder terms get the same files under `/folders/<path>/…`. Feed channels carry
+their own term title and self link, so a tag subscription is distinguishable
+from the site-wide feeds owned by `@riebeckite/plugin-seo`. Only published,
+non-`noindex` entries reach the manifest's public view and therefore the feeds.
+
+## Related tags
+
+When `related` is enabled, each tag term carries tags that co-occur on the same
+entries, ranked by shared-entry count then alphabetically, clamped to
+`relatedLimit`. Related navigation is rendered by `renderTaxonomyPage`:
+
+```html
+<nav class="rr-taxonomy__related" aria-label="Related tags" data-rr-taxonomy-related>
+  <ul>
+    <li class="rr-taxonomy__related-item">
+      <a class="rr-taxonomy__related-link" href="/tags/featured" data-rr-taxonomy-related-count="2">#featured</a>
+    </li>
+  </ul>
+</nav>
+```
+
+## SEO
+
+`buildTaxonomySeo(config, term)` returns `SeoMetadata` for a listing page. It
+delegates to the configured Core `seo` extension point (for example
+`@riebeckite/plugin-seo`) so titles, canonical URLs, and JSON-LD stay consistent
+with the rest of the site, and falls back to a minimal object when no SEO
+provider is registered.
+
+## Folder index notes
+
+With `folderIndexes: true`, the plugin's `resolveContentLocations` hook maps a
+note at `<folder>/index.md` to `/<folder>` instead of `/<folder>/index`. The
+chosen permalink is recorded as `metadata["taxonomy.folder"]`. A location is
+never claimed when another note already owns it; the conflict is reported as a
+diagnostic instead.
+
+## App-route wiring
+
+The application owns routing. Register the listing paths in the app and render
+them from the plugin's data:
+
+```tsx
+// app/routes/tags/[slug{.+}].tsx
+import { ssgParams } from "hono/ssg";
+import { createRoute } from "honox/factory";
+import {
+  buildTaxonomyIndex,
+  buildTaxonomySeo,
+  renderTaxonomyPage,
+  resolveTaxonomyOptionsFromConfig,
+} from "@riebeckite/plugin-taxonomy";
+import Article from "../../components/article/article";
+import { config } from "../../config";
+import { content } from "../../content";
+
+export default createRoute(
+  ssgParams(async () => {
+    const options = resolveTaxonomyOptionsFromConfig(config);
+    const manifest = await content.getManifest();
+    return buildTaxonomyIndex(manifest.publicEntries, options).tags.map(
+      (term) => ({ slug: term.path.replace(/^\/tags\//, "") }),
+    );
+  }),
+  async (c) => {
+    const options = resolveTaxonomyOptionsFromConfig(config);
+    const manifest = await content.getManifest();
+    const term = buildTaxonomyIndex(manifest.publicEntries, options).tags.find(
+      (candidate) => candidate.path === c.req.path,
+    );
+    c.set("seo", term ? buildTaxonomySeo(config, term) : undefined);
+    if (!term) return c.notFound();
+    const page = renderTaxonomyPage(term, options);
+    c.set("headTags", page.headTags);
+    return c.render(<Article content={page} />);
+  },
+);
+```
+
+A folder route follows the same shape with `.folders` and `/folders/`. The
+`renderTaxonomyPage` result is `PostContent`-compatible (`frontmatter` + `html`),
+so it drops into the reference `Article` primitive; `headTags` adds the feed
+discovery `<link rel="alternate">` elements to the document head.
+
+## Style
+
+The package ships `style.css` with the stable `rr-taxonomy` root hook and
+`--rr-taxonomy-*` tokens (falling back to `--rb-*`). Register it like any other
+plugin stylesheet:
+
+```ts
+import "@riebeckite/plugin-taxonomy/style.css";
+```
+
+## Exports
+
+- `taxonomy(options?)` — plugin factory
+- `taxonomyPlugin` — alias of `taxonomy`
+- `resolveTaxonomyOptions(options?)` — apply option defaults
+- `resolveTaxonomyOptionsFromConfig(config)` — read resolved options back from a config
+- `buildTaxonomyIndex(entries, options)` — build tag and folder terms
+- `serializeTaxonomyIndex(index)` / `serializeTaxonomyTerm(term)` — JSON-safe projections
+- `renderTaxonomyPage(term, options)` / `renderRelatedTerms(term, options)` — page fragments
+- `renderTermFeed(config, term, format, limit?)` / `buildFeedHeadTags(term)` — per-term feeds
+- `buildTaxonomySeo(config, term)` — listing-page SEO metadata
+- `resolveFolderIndexLocations(entries, options, diagnostics)` — folder-index location strategy
+- `slugifyTaxonomyValue(value)` — URL/file slug
+- `buildTaxonomyAbsoluteUrl(config, pathOrUrl)` — absolute URLs
+- Types: `TaxonomyOptions`, `ResolvedTaxonomyOptions`, `TaxonomyTerm`, `TaxonomyIndex`, `TaxonomyPage`, `TaxonomyTermData`, `TaxonomyIndexData`
+
+## Limitations
+
+- Taxonomy is fixed at build time. A full rebuild always recomputes correctly.
+- Per-term feeds are static build output; the fixed JSON data endpoint is the
+  only runtime surface. A dev server does not enumerate per-term feed files.
+- Terms only reflect the manifest's public view; unpublished or `noindex`
+  entries are excluded.
+
+## See also
+
+- [Plugin guide](../../../docs/en/plugin-system.md)
+- [Content system](../../../docs/en/content-system.md)

package/README_ja.md

@@ -0,0 +1,225 @@
+# @riebeckite/plugin-taxonomy
+
+Riebeckite のビルド時タクソノミー（タグ・フォルダ）プラグインです。一覧用データ、
+語ごとの RSS / Atom / JSON フィード、関連タグナビゲーション、SEO メタデータを
+生成します。クライアント JavaScript は不要です。
+
+[English](./README.md)
+
+## 概要
+
+`taxonomy()` はマニフェストの公開エントリを読み、Core の collection contract
+（`buildContentCollections`）で 2 種類の一覧語を生成します。
+
+- **タグ**: `tags` でグルーピングし `/tags/<slug>` に配置します。
+- **フォルダ**: フォルダでグルーピングし `/folders/<path>` に配置します。
+
+エントリのリンクには常に解決済みの `permalink` を使い、slug から URL を組み立てる
+ことはありません。
+
+このプラグインが持つのはデータ・フィード・SEO だけです。アプリケーションの
+ルートは登録しません。語ごとのフィードはビルドの generated-output sink 経由で
+静的ファイルとして出力し、`/tags/<tag>` と `/folders/<path>` のページは
+エクスポートしたヘルパーを使ってアプリ側で描画します
+（[アプリルートの配線](#アプリルートの配線) を参照）。
+
+## 使い方
+
+```ts
+import { defineConfig } from "@riebeckite/core";
+import { taxonomy } from "@riebeckite/plugin-taxonomy";
+
+export default defineConfig({
+  // ...
+  plugins: [
+    taxonomy({
+      tags: true,
+      folders: true,
+      related: true,
+      folderIndexes: true,
+    }),
+  ],
+});
+```
+
+## オプション
+
+| オプション | 型 | 既定値 | 説明 |
+| ---------- | -- | ------ | ---- |
+| `tags` | `boolean` | `true` | タグ語を生成する |
+| `folders` | `boolean` | `true` | フォルダ語を生成する |
+| `tagsBasePath` | `string` | `"/tags"` | タグ一覧のパス接頭辞 |
+| `foldersBasePath` | `string` | `"/folders"` | フォルダ一覧のパス接頭辞 |
+| `folderDepth` | `number` | `0` | フォルダのグルーピング深さ。`0` は完全パス |
+| `minEntries` | `number` | `1` | これ未満のエントリ数しかない語を除外する |
+| `related` | `boolean` | `true` | 関連タグナビゲーションを生成する |
+| `relatedLimit` | `number` | `8` | タグごとの関連タグ上限 |
+| `folderIndexes` | `boolean` | `false` | `<folder>/index.md` を `/<folder>` に解決する |
+| `feeds` | `{ rss?, atom?, json? }` | すべて `true` | 語ごとのフィード形式 |
+| `feedLimit` | `number` | `50` | フィードあたりの最大エントリ数 |
+| `resolveTitle` | `(context) => string` | `#value` / パス | 語の表示タイトル |
+| `className` | `string` | `"rr-taxonomy"` | ページ断片のルート CSS クラス |
+| `dataEndpoint` | `string` | `"/taxonomy/index.json"` | JSON データのエンドポイント |
+
+## データエンドポイント
+
+プラグインは JSON エンドポイントを 1 つ登録します（endpoint contract は HonoX
+integration が接続するため、プラグイン自身は framework のルーティングを持ちません）。
+
+```
+GET /taxonomy/index.json
+```
+
+```json
+{
+  "tags": [
+    {
+      "kind": "tag",
+      "value": "featured",
+      "title": "#featured",
+      "path": "/tags/featured",
+      "permalink": "/tags/featured",
+      "count": 1,
+      "entries": [{ "slug": "example", "permalink": "/notes/example", "title": "Example Note", "updated": null, "summary": "..." }],
+      "related": [],
+      "feeds": { "rss": "/tags/featured/feed.xml", "atom": "/tags/featured/atom.xml", "json": "/tags/featured/feed.json" }
+    }
+  ],
+  "folders": []
+}
+```
+
+ペイロードは決定的で JSON 安全な射影です。描画済み HTML を含まないため、アプリの
+ルートやブラウザへそのまま渡せます。
+
+## 生成されるフィード
+
+ビルド時に、語と形式ごとに 1 つのフィードを `context.output.emit` で出力します。
+
+| 形式 | パス |
+| ---- | ---- |
+| RSS 2.0 | `/tags/<slug>/feed.xml` |
+| Atom | `/tags/<slug>/atom.xml` |
+| JSON Feed 1.1 | `/tags/<slug>/feed.json` |
+
+フォルダ語も同じファイルを `/folders/<path>/…` に持ちます。フィードの channel は
+語ごとのタイトルと self link を持つため、タグの購読と
+`@riebeckite/plugin-seo` が持つサイト全体のフィードを区別できます。公開かつ
+`noindex` でないエントリだけがマニフェストの公開ビューに入り、フィードへ届きます。
+
+## 関連タグ
+
+`related` が有効なとき、各タグ語は同じエントリに共起するタグを保持します。共起
+エントリ数で降順、同数ならアルファベット順に並べ、`relatedLimit` で打ち切ります。
+ナビゲーションは `renderTaxonomyPage` が描画します。
+
+```html
+<nav class="rr-taxonomy__related" aria-label="Related tags" data-rr-taxonomy-related>
+  <ul>
+    <li class="rr-taxonomy__related-item">
+      <a class="rr-taxonomy__related-link" href="/tags/featured" data-rr-taxonomy-related-count="2">#featured</a>
+    </li>
+  </ul>
+</nav>
+```
+
+## SEO
+
+`buildTaxonomySeo(config, term)` は一覧ページの `SeoMetadata` を返します。設定済みの
+Core `seo` 拡張ポイント（たとえば `@riebeckite/plugin-seo`）へ委譲するため、
+タイトル・canonical URL・JSON-LD がサイト全体と揃います。SEO プロバイダーが無い
+場合は最小限のオブジェクトへフォールバックします。
+
+## フォルダ index note
+
+`folderIndexes: true` のとき、プラグインの `resolveContentLocations` フックが
+`<folder>/index.md` のノートを `/<folder>/index` ではなく `/<folder>` に解決します。
+選ばれた permalink は `metadata["taxonomy.folder"]` に記録されます。すでに他の
+ノートが所有している location は決して奪わず、衝突は診断として報告します。
+
+## アプリルートの配線
+
+ルーティングはアプリケーションが所有します。一覧パスをアプリに登録し、プラグインの
+データから描画してください。
+
+```tsx
+// app/routes/tags/[slug{.+}].tsx
+import { ssgParams } from "hono/ssg";
+import { createRoute } from "honox/factory";
+import {
+  buildTaxonomyIndex,
+  buildTaxonomySeo,
+  renderTaxonomyPage,
+  resolveTaxonomyOptionsFromConfig,
+} from "@riebeckite/plugin-taxonomy";
+import Article from "../../components/article/article";
+import { config } from "../../config";
+import { content } from "../../content";
+
+export default createRoute(
+  ssgParams(async () => {
+    const options = resolveTaxonomyOptionsFromConfig(config);
+    const manifest = await content.getManifest();
+    return buildTaxonomyIndex(manifest.publicEntries, options).tags.map(
+      (term) => ({ slug: term.path.replace(/^\/tags\//, "") }),
+    );
+  }),
+  async (c) => {
+    const options = resolveTaxonomyOptionsFromConfig(config);
+    const manifest = await content.getManifest();
+    const term = buildTaxonomyIndex(manifest.publicEntries, options).tags.find(
+      (candidate) => candidate.path === c.req.path,
+    );
+    c.set("seo", term ? buildTaxonomySeo(config, term) : undefined);
+    if (!term) return c.notFound();
+    const page = renderTaxonomyPage(term, options);
+    c.set("headTags", page.headTags);
+    return c.render(<Article content={page} />);
+  },
+);
+```
+
+フォルダのルートも `.folders` と `/folders/` に置き換えると同じ形です。
+`renderTaxonomyPage` の戻り値は `PostContent` 互換（`frontmatter` + `html`）なので、
+参照アプリの `Article` primitive にそのまま渡せます。`headTags` はフィード検出用の
+`<link rel="alternate">` を document head に追加します。
+
+## スタイル
+
+パッケージは安定した `rr-taxonomy` ルートフックと `--rr-taxonomy-*` トークン
+（`--rb-*` へフォールバック）を持つ `style.css` を同梱します。他のプラグイン
+スタイルシートと同じように登録してください。
+
+```ts
+import "@riebeckite/plugin-taxonomy/style.css";
+```
+
+## エクスポート
+
+- `taxonomy(options?)` — プラグインファクトリー
+- `taxonomyPlugin` — `taxonomy` の別名
+- `resolveTaxonomyOptions(options?)` — 既定値を適用する
+- `resolveTaxonomyOptionsFromConfig(config)` — config から解決済みオプションを読む
+- `buildTaxonomyIndex(entries, options)` — タグ・フォルダ語を構築する
+- `serializeTaxonomyIndex(index)` / `serializeTaxonomyTerm(term)` — JSON 安全な射影
+- `renderTaxonomyPage(term, options)` / `renderRelatedTerms(term, options)` — ページ断片
+- `renderTermFeed(config, term, format, limit?)` / `buildFeedHeadTags(term)` — 語ごとのフィード
+- `buildTaxonomySeo(config, term)` — 一覧ページの SEO メタデータ
+- `resolveFolderIndexLocations(entries, options, diagnostics)` — フォルダ index の location 戦略
+- `slugifyTaxonomyValue(value)` — URL・ファイル用の slug
+- `buildTaxonomyAbsoluteUrl(config, pathOrUrl)` — 絶対 URL
+- 型: `TaxonomyOptions`, `ResolvedTaxonomyOptions`, `TaxonomyTerm`, `TaxonomyIndex`, `TaxonomyPage`, `TaxonomyTermData`, `TaxonomyIndexData`
+
+## 制約
+
+- タクソノミーはビルド時に固定されます。フルビルドで常に正しく再計算されます。
+- 語ごとのフィードは静的なビルド成果物です。実行時のサーフェスは固定の JSON
+  データエンドポイントだけです。dev サーバーは語ごとのフィードファイルを列挙
+  しません。
+- 語はマニフェストの公開ビューのみを反映します。非公開または `noindex` の
+  エントリは除外されます。
+
+## 関連
+
+- [プラグインガイド](../../../docs/ja/plugin-system.md)
+- [コンテンツシステム](../../../docs/ja/content-system.md)