Skip to content

Conversation

@eshanrnh
Copy link
Contributor

@eshanrnh eshanrnh commented Mar 19, 2024

Description

Removed references to nested content from v10, v12, and v13. Let me know if I should do it for v14 as well.

Type of suggestion

  • Typo/grammar fix
  • Updated outdated content
  • New content
  • Updates related to a new version
  • Other

Product & version (if relevant)

Deadline (if relevant)

When should the content be published?

@alina-tincas
Copy link
Contributor

hmm, I think the main article should be left in the docs for v10, 12 and 13 as it can still be used even is if it is discontinued. It is only from v14 that it is completely removed.

@alina-tincas
Copy link
Contributor

and also leave the release notes as they are with nested content if they include something about nested content

@alina-tincas
Copy link
Contributor

ok, found it in CMS repo:
image

so the warning is "Nested content is obsolete, will be removed in V13"

@alina-tincas
Copy link
Contributor

alina-tincas commented Mar 19, 2024

So my recommendation is:

  1. Leave the release notes from deploy as they are with nested content included as am sure there is a reason why it was mentioned there.
  2. on v10 and v12 leave the main article umbraco-cms\fundamentals\backoffice\property-editors\built-in-umbraco-property-editors\nested-content.md in the summary so that people are aware that it has been discontinued and what to use instead
  3. on v13 and v14 you can remove everything about nested content 👍

@eshanrnh
Copy link
Contributor Author

@alina-tincas Thanks for your review 🙌I've incorporated the comments. Let me know what you think 🙂

…in-umbraco-property-editors/block-editor/block-list-editor.md
…in-umbraco-property-editors/block-editor/block-list-editor.md
@alina-tincas
Copy link
Contributor

LGTM 💪 🙌 #h5YR

@eshanrnh eshanrnh merged commit 7e8dea4 into main Mar 20, 2024
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