This is title
One plugin. Two concrete jobs.
Arboretum is useful when your team needs both a human-readable sitemap and a developer-friendly way to resolve routes.
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.
