Arboretum is useful when your team needs both a human-readable sitemap and a developer-friendly way to resolve routes.
Four capabilities that matter in day-to-day use.
For editors, the main benefit is visibility. You can see the sitemap as a structure instead of piecing it together from linked entries, slugs, and parent references spread across the space.
That makes routine work simpler: checking where a page sits, spotting gaps, understanding hierarchy, and discussing changes with less ambiguity. The sitemap lives where the content already lives — inside Contentful.
There is no separate planning tool to keep in sync. No extra source of truth to mistrust.
For developers, Arboretum helps with route resolution. It provides a way to translate a path into the Contentful entry ID behind it, and to go the other way from an entry ID to its resolved path.
That is useful in frontends, preview tools, middleware, migrations, and debugging. Instead of rebuilding sitemap logic in several places, teams can use one consistent model tied to the Contentful space.
The practical result is less duplicated logic and fewer route mismatches between editorial structure and implementation.
Editors can inspect page hierarchy in a format that matches how people think about a site: parent, child, path, and structure.
The sitemap stays tied to Contentful instead of being copied into another planning tool or maintained in a separate service.
Developers can resolve a URL path to the entry ID behind it. Useful for routing, previews, middleware, and diagnostics.
Developers can go from a Contentful entry ID back to the resolved path. Useful when content changes need to map cleanly to frontend routes.
Same plugin. Different practical value depending on the job.
Use Arboretum to understand the site structure without opening ten entries in separate tabs. It is easier to check hierarchy, discuss navigation changes, and verify where a page belongs.
Use Arboretum when route resolution matters. It helps connect Contentful entries and frontend paths in a way that is easier to inspect, test, and reason about.
Use Arboretum as a shared reference point. Editors and developers can discuss the same sitemap model instead of working from separate spreadsheets, assumptions, or undocumented conventions.
Direct answers on setup, storage, and technical behaviour.
No. The point of the plugin is to work with sitemap structure in Contentful, not to introduce a second system that has to be kept in sync.
That matters for governance and for day-to-day work. Editors and developers can inspect the structure where the content already lives instead of relying on a parallel database or spreadsheet.
