Skip to content

Conversation

@madsrasmussen
Copy link
Contributor

Deleted the 'section-trees.md' and 'searchable-trees.md' documentation files from versions 15, 16, and 17 of Umbraco CMS, and removed their references from the SUMMARY.md files.

✅ Contributor Checklist

I've followed the Umbraco Documentation Style Guide and can confirm that:

  • Code blocks are correctly formatted.
  • Sentences are short and clear (preferably under 25 words).
  • Passive voice and first-person language (“we”, “I”) are avoided.
  • Relevant pages are linked.
  • All links work and point to the correct resources.
  • Screenshots or diagrams are included if useful.
  • Any code examples or instructions have been tested.
  • Typos, broken links, and broken images are fixed.

📚 Helpful Resources

Deleted the 'section-trees.md' and 'searchable-trees.md' documentation files from versions 15, 16, and 17 of Umbraco CMS, and removed their references from the SUMMARY.md files.
@madsrasmussen madsrasmussen marked this pull request as ready for review November 18, 2025 20:05
@AndyButland AndyButland merged commit 312b33f into umbraco:main Nov 18, 2025
8 checks passed
@eshanrnh
Copy link
Contributor

@madsrasmussen @AndyButland You might want to consider deleting the references from the following files, too:

  1. 15/umbraco-cms/customizing/overview.md
  2. fundamentals/backoffice/README.md (for all versions)
  3. extending/backoffice-search.md (for all versions)
  4. implementation/composing.md has references to ISearchableTree (for all versions).
  5. tutorials/editors-manual/getting-started-with-umbraco/umbraco-interface.md -- The Section Tree section at the end.
  6. There are references to section tree in the UI Builder docs: umbraco-ui-builder/areas/sections.md#configuring-the-section-tree
  7. A couple of other places in the CMS docs. For example: Folder - a container for organizing media items in the Media section tree. Is this to be replaced with another term instead?

Finally, since these articles are removed, we need to add redirects in .gitbook.yaml file to point users to another feature/article that is recommended to use instead.

@AndyButland
Copy link
Contributor

Sorry @eshanrnh - I'll have a look at this. Thought we were saving you a job by merging this one in, but probably should have checked.

We did discuss the redirect though and didn't really have one. Part of the content references something that's removed, and the other was very slight and didn't add much value. So actually a 404 would be OK I think.

@AndyButland
Copy link
Contributor

@eshanrnh - I've created a PR for this here: #7637 It's not actually everything you've mentioned that needs to be removed - sections and trees are still a thing, it was just one feature we no longer have implemented as it was in 13.

@eshanrnh
Copy link
Contributor

@AndyButland No problem at all. I appreciate you trying to lighten my load 🙌

If there’s no redirect to add, would it make sense to include a small note somewhere explaining that this particular feature is no longer supported? That way, anyone looking for it isn’t surprised that the articles have disappeared.

@AndyButland
Copy link
Contributor

If you think we need something, then on reflection a redirect is likely best. Could you send the articles to the parent index page please, which would be https://docs.umbraco.com/umbraco-cms/customizing/overview?

@eshanrnh
Copy link
Contributor

Sure will do 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants