Add page for taxonomies

[carolromero]

Remove the local configuration from antora.yml please

Summary by CodeRabbit

• Documentation
  • Added comprehensive Taxonomies documentation under the Admin Settings section, explaining the unified content classification system that replaces previous organizational methods like Categories and Scopes.
  • Includes step-by-step configuration guides covering taxonomy management, item creation with hierarchical organization, filter creation, and integration with participation spaces and components for enhanced content navigation and discovery.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@andreslucena has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 39 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c1a67ad7-bd28-4a36-96aa-ce233addfae9

📥 Commits

Reviewing files that changed from the base of the PR and between 683a522 and 987b08d.

📒 Files selected for processing (2)

• docs/en/modules/admin/pages/settings.adoc
• docs/en/modules/admin/pages/settings/taxonomies.adoc

📝 Walkthrough

Walkthrough

Three documentation files were updated to introduce Taxonomies feature documentation. Changes include adding a new navigation entry in the ROOT navigation file, updating the Settings navigation with Taxonomies, and creating a comprehensive new documentation page explaining Taxonomies concept, configuration steps, and usage guidelines.

Changes

Cohort / File(s)	Summary
Documentation Navigation & Content docs/en/modules/ROOT/nav.adoc, docs/en/modules/admin/pages/settings.adoc, docs/en/modules/admin/pages/settings/taxonomies.adoc	Added Taxonomies to navigation structure and created comprehensive documentation page explaining Taxonomies as a unified content classification system, including configuration steps, hierarchy management, filter creation, and usage guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A taxonomy of wonders, now put to page,
Where docs unfold like clover in the sage,
New chapters bloom, with filters bright and clear,
Classification magic—admin's treasure here!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add page for taxonomies' accurately reflects the main change: adding a new documentation page (taxonomies.adoc) along with related navigation updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/taxonomies-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In `@docs/en/modules/admin/pages/settings.adoc`:
- Around line 23-28: Update the Scopes and Areas list entries to clarify their
relationship to Taxonomies: edit the xref:admin:settings/scopes.adoc[Scopes] and
xref:admin:settings/areas.adoc[Areas] lines to add a short parenthetical note
such as “(legacy — superseded by
xref:admin:settings/taxonomies.adoc[Taxonomies])” or “(still available in vX,
replaced by Taxonomies)”, ensuring the Taxonomies xref remains and clearly
indicates replacement; keep the wording brief and consistent with the other list
items.

In `@docs/en/modules/admin/pages/settings/taxonomies.adoc`:
- Line 9: Replace the abbreviated "e.g." in the sentence "Administrators can
define various taxonomies (e.g., territorial scopes, thematic areas) and apply
them consistently across different participation spaces and components." with
the full phrase "for example" so it reads "Administrators can define various
taxonomies (for example, territorial scopes, thematic areas) and apply them
consistently across different participation spaces and components." This change
will satisfy the Vale lint rule and unblock CI.
- Line 21: Replace the abbreviation "e.g." with the phrase "for example" in the
sentence that reads 'Enter the name of the taxonomy (e.g., "Geographic Scope" or
"Thematic Area")' so it becomes 'Enter the name of the taxonomy (for example,
"Geographic Scope" or "Thematic Area")' to satisfy the Vale lint rule; update
the text in the taxonomies.adoc content where that exact sentence occurs.

🧹 Nitpick comments (2)

docs/en/modules/admin/pages/settings/taxonomies.adoc (2)

31-38: Tighten wording to meet style rules (active voice, “will”, “click on”, “functionality”).

Several Vale warnings can be addressed with a small rewrite.

✏️ Proposed fix

-4. Use the drag-and-drop functionality to reorder items as desired.
+4. Use the drag-and-drop feature to reorder items as desired.

-You can create filters with all or some taxonomy items that will be used to classify and filter participation spaces and components:
+You can create filters with all or some taxonomy items to classify and filter participation spaces and components:

-1. From the Actions menu, click on **Apply filters** to create or see the existing filters of a taxonomy.
-2. Click on the **New filter** button, enter the label of the filter, that is the title that will be displayed in the frontend, and select which items are available for that filter. You can select only parents or only children.
+1. From the Actions menu, click **Apply filters** to create or view existing filters for a taxonomy.
+2. Click the **New filter** button, enter the filter label (the title displayed in the frontend), and select which items are available for that filter. You can select only parents or only children.

---

63-63: Prefer active voice here.

Small style fix to avoid passive phrasing.

✏️ Proposed fix

-Taxonomy filters can also be associated with components to facilitate content classification:
+You can also associate taxonomy filters with components to facilitate content classification:

[andreslucena]

@carolromero can you check the review from CodeRabbit?

Also I see that there's a problem with the vale linter. Maybe if you do another commit here it will kick in again, as it seems like a bug in their side.