@riebeckite/plugin-taxonomy 0.0.14 → 0.0.15

package/README.md

@@ -35,7 +35,6 @@ export default defineConfig({
       tags: true,
       folders: true,
       related: true,
-      folderIndexes: true,
     }),
   ],
 });
@@ -53,7 +52,6 @@ export default defineConfig({
 | `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 |
@@ -133,11 +131,11 @@ 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.
+Folder entry resolution is owned by
+[`@riebeckite/plugin-folder-pages`](../folder-pages/README.md), so taxonomy only
+generates tag and folder terms from the manifest's public view. Enable that
+plugin when a note at `<folder>/README.md` or `<folder>/index.md` should become
+the folder's landing page.
 
 ## Page types
 
@@ -171,7 +169,6 @@ import "@riebeckite/plugin-taxonomy/style.css";
 - `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`
@@ -186,5 +183,6 @@ import "@riebeckite/plugin-taxonomy/style.css";
 
 ## See also
 
-- [Plugin guide](../../../docs/en/reference/plugin-api.md)
-- [Content system](../../../docs/en/framework/content-system.md)
+- [Plugin guide](../../../docs/en/docs/reference/plugin-api.md)
+- [Content system](../../../docs/en/docs/framework/content-system.md)
+

package/README_ja.md

@@ -36,7 +36,6 @@ export default defineConfig({
       tags: true,
       folders: true,
       related: true,
-      folderIndexes: true,
     }),
   ],
 });
@@ -54,7 +53,6 @@ export default defineConfig({
 | `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` / パス | 語の表示タイトル |
@@ -132,10 +130,11 @@ Core `seo` 拡張ポイント（たとえば `@riebeckite/plugin-seo`）へ委
 
 ## フォルダ index note
 
-`folderIndexes: true` のとき、プラグインの `resolveContentLocations` フックが
-`<folder>/index.md` のノートを `/<folder>/index` ではなく `/<folder>` に解決します。
-選ばれた permalink は `metadata["taxonomy.folder"]` に記録されます。すでに他の
-ノートが所有している location は決して奪わず、衝突は診断として報告します。
+フォルダ入口の解決は
+[`@riebeckite/plugin-folder-pages`](../folder-pages/README_ja.md) が所有します。
+taxonomy はマニフェストの公開ビューからタグ語とフォルダ語だけを生成します。
+`<folder>/README.md` や `<folder>/index.md` をフォルダのランディングページに
+する場合は、そのプラグインを有効にしてください。
 
 ## Page Type
 
@@ -169,7 +168,6 @@ import "@riebeckite/plugin-taxonomy/style.css";
 - `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`
@@ -185,5 +183,6 @@ import "@riebeckite/plugin-taxonomy/style.css";
 
 ## 関連
 
-- [プラグインガイド](../../../docs/ja/reference/plugin-api.md)
-- [コンテンツシステム](../../../docs/ja/framework/content-system.md)
+- [プラグインガイド](../../../docs/ja/docs/reference/plugin-api.md)
+- [コンテンツシステム](../../../docs/ja/docs/framework/content-system.md)
+

package/dist/index.d.ts

@@ -2,7 +2,6 @@ import { type ResolvedRiebeckiteConfig } from "@riebeckite/core";
 import type { ResolvedTaxonomyOptions, TaxonomyOptions } from "./src/types.js";
 export { buildTaxonomyIndex, serializeTaxonomyIndex, serializeTaxonomyTerm, toEntryReference, } from "./src/collections.js";
 export { buildFeedHeadTags, renderTermFeed } from "./src/feeds.js";
-export { resolveFolderIndexLocations } from "./src/locations.js";
 export { DEFAULT_TAXONOMY_CLASS_NAME, DEFAULT_TAXONOMY_DATA_ENDPOINT, DEFAULT_TAXONOMY_FEED_LIMIT, DEFAULT_TAXONOMY_FOLDERS_BASE_PATH, DEFAULT_TAXONOMY_MIN_ENTRIES, DEFAULT_TAXONOMY_RELATED_LIMIT, DEFAULT_TAXONOMY_TAGS_BASE_PATH, resolveTaxonomyOptions, } from "./src/options.js";
 export { renderRelatedTerms, renderTaxonomyPage } from "./src/pages.js";
 export { buildTaxonomySeo } from "./src/seo.js";

package/dist/index.js

@@ -324,48 +324,6 @@ function toIso(value) {
   return Number.isNaN(date.getTime()) ? null : date.toISOString();
 }
 
-// src/locations.ts
-import {
-  resolveDefaultContentLocation
-} from "@riebeckite/core";
-var PLUGIN_NAME = "taxonomy";
-function resolveFolderIndexLocations(entries, options, diagnostics) {
-  if (!options.folderIndexes) return [];
-  const permalinkOwners = /* @__PURE__ */ new Map();
-  for (const entry of entries) {
-    const location = resolveDefaultContentLocation(entry);
-    if (!permalinkOwners.has(location.permalink)) {
-      permalinkOwners.set(location.permalink, entry.slug);
-    }
-  }
-  const locations = [];
-  for (const entry of entries) {
-    const suffix = "/index";
-    if (!entry.slug.endsWith(suffix)) continue;
-    const folder = entry.slug.slice(0, -suffix.length);
-    if (folder === "") continue;
-    const target = `/${folder}`;
-    const owner = permalinkOwners.get(target);
-    if (owner && owner !== entry.slug) {
-      diagnostics.push({
-        code: "taxonomy-folder-index-collision",
-        severity: "warning",
-        pluginName: PLUGIN_NAME,
-        message: `Folder index "${entry.path}" already maps to a note at "${target}"; keeping the default location.`,
-        slug: entry.slug,
-        target
-      });
-      continue;
-    }
-    locations.push({
-      slug: entry.slug,
-      permalink: target,
-      metadata: { "taxonomy.folder": folder }
-    });
-  }
-  return locations;
-}
-
 // src/options.ts
 var DEFAULT_TAXONOMY_TAGS_BASE_PATH = "/tags";
 var DEFAULT_TAXONOMY_FOLDERS_BASE_PATH = "/folders";
@@ -393,7 +351,6 @@ function resolveTaxonomyOptions(options = {}) {
       options.relatedLimit,
       DEFAULT_TAXONOMY_RELATED_LIMIT
     ),
-    folderIndexes: options.folderIndexes ?? false,
     feeds: {
       rss: options.feeds?.rss ?? true,
       atom: options.feeds?.atom ?? true,
@@ -527,15 +484,15 @@ function taxonomy(options = {}) {
     name: TAXONOMY_PLUGIN_NAME,
     options,
     validateOptions: validateTaxonomyOptions,
-    resolveContentLocations: ({ entries, diagnostics }) => resolveFolderIndexLocations(entries, resolved, diagnostics),
     endpoints: createTaxonomyEndpoints(resolved),
     pageTypes: [
       {
         id: "taxonomy-term",
-        paths: ({ manifest }) => taxonomyPagePaths(manifest.publicEntries, resolved),
+        paths: ({ manifest }) => taxonomyPagePaths(manifest.discoverableEntries, resolved),
+        outputDependencies: [{ type: "global" }],
         resolve: ({ manifest, pathname }) => {
           const term = findTaxonomyTerm(
-            manifest.publicEntries,
+            manifest.discoverableEntries,
             resolved,
             pathname
           );
@@ -554,7 +511,7 @@ function taxonomy(options = {}) {
     buildEnd(context) {
       const { config, manifest } = context;
       if (!config) return;
-      const index = buildTaxonomyIndex(manifest.publicEntries, resolved);
+      const index = buildTaxonomyIndex(manifest.discoverableEntries, resolved);
       for (const term of [...index.tags, ...index.folders]) {
         for (const format of enabledFormats(resolved)) {
           const path = feedFilePath(term.path, format);
@@ -562,7 +519,8 @@ function taxonomy(options = {}) {
           emittedFeeds.add(path);
           context.output.emit({
             path,
-            content: renderTermFeed(config, term, format, resolved.feedLimit)
+            content: renderTermFeed(config, term, format, resolved.feedLimit),
+            dependencies: [{ type: "global" }]
           });
         }
       }
@@ -596,7 +554,7 @@ function createTaxonomyEndpoints(resolved) {
       resolved.dataEndpoint,
       ({ manifest }) => ({
         json: serializeTaxonomyIndex(
-          buildTaxonomyIndex(manifest.publicEntries, resolved)
+          buildTaxonomyIndex(manifest.discoverableEntries, resolved)
         )
       }),
       { cacheControl: "public, max-age=300" }
@@ -640,7 +598,7 @@ function validateTaxonomyOptions(options) {
       });
     }
   };
-  for (const key of ["tags", "folders", "related", "folderIndexes"]) {
+  for (const key of ["tags", "folders", "related"]) {
     assertBoolean(key);
   }
   for (const key of [
@@ -695,7 +653,6 @@ export {
   renderRelatedTerms,
   renderTaxonomyPage,
   renderTermFeed,
-  resolveFolderIndexLocations,
   resolveTaxonomyOptions,
   resolveTaxonomyOptionsFromConfig,
   serializeTaxonomyIndex,

package/dist/src/types.d.ts

@@ -27,8 +27,6 @@ export type TaxonomyOptions = {
     related?: boolean;
     /** Maximum related terms per tag. Defaults to `8`. */
     relatedLimit?: number;
-    /** Encode folder index notes (`<folder>/index.md`) as `<folder>`. Defaults to `false`. */
-    folderIndexes?: boolean;
     /** Per-format feed generation. Defaults to RSS, Atom, and JSON. */
     feeds?: TaxonomyFeedOptions;
     /** Maximum entries included in a per-term feed. Defaults to `50`. */
@@ -50,7 +48,6 @@ export type ResolvedTaxonomyOptions = {
     minEntries: number;
     related: boolean;
     relatedLimit: number;
-    folderIndexes: boolean;
     feeds: Required<TaxonomyFeedOptions>;
     feedLimit: number;
     className: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@riebeckite/plugin-taxonomy",
-  "version": "0.0.14",
+  "version": "0.0.15",
   "license": "Apache-2.0",
   "type": "module",
   "main": "./dist/index.js",
@@ -15,7 +15,7 @@
     "./style.css": "./style.css"
   },
   "dependencies": {
-    "@riebeckite/core": "0.0.14"
+    "@riebeckite/core": "0.0.15"
   },
   "devDependencies": {
     "tsx": "^4.22.4"

package/dist/src/locations.d.ts

@@ -1,14 +0,0 @@
-import { type ContentLocationInput, type ContentPublicLocation, type Diagnostic } from "@riebeckite/core";
-import type { ResolvedTaxonomyOptions } from "./types.js";
-/**
- * Public-location strategy for folder index notes.
- *
- * Core's default resolver collapses only the root `index` slug to `/`. When
- * `folderIndexes` is enabled, a note at `<folder>/index.md` resolves to
- * `/<folder>` instead of `/<folder>/index`, so each folder can own its index
- * page. The chosen permalink is recorded in `metadata["taxonomy.folder"]`.
- *
- * The resolver never overwrites a location that another note already claims as
- * its default permalink; it reports a diagnostic instead.
- */
-export declare function resolveFolderIndexLocations(entries: readonly ContentLocationInput[], options: ResolvedTaxonomyOptions, diagnostics: Diagnostic[]): ContentPublicLocation[];