Optimize (CQA) - Split Managing CVs per user story#4895
Conversation
github-actions
Bot
added
Needs tech review
Lennonka
removed
Needs tech review
maximiliankolb
left a comment
maximiliankolb
left a comment
There was a problem hiding this comment.
I found one issue about CCVs (which also exists on "master"). Rest LGTM minus some nitpicks.
| ifeval::["{context}" == "planning"] | ||
| .Additional resources | ||
| * {ContentManagementDocURL}Managing_Content_Views_content-management[Managing content views in _{ContentManagementDocTitle}_] | ||
| * {ContentManagementDocURL}managing-content-views-and-related-configuration[Managing content views in _{ContentManagementDocTitle}_] |
There was a problem hiding this comment.
Please also adjust the title; applied to other files too.
There was a problem hiding this comment.
As soon as we agree on the title.
| :_mod-docs-content-type: CONCEPT | ||
|
|
||
| [id="managing-content-views-and-related-configuration"] | ||
| = Managing content views and related configuration |
There was a problem hiding this comment.
non-blocking: I am a tiny bit unsure about the title. What do you think about
| = Managing content views and related configuration | |
| = Managing content views |
Too short?
There was a problem hiding this comment.
Ah, is it mainly because we already have guides/common/modules/con_managing-content-views.adoc?
There was a problem hiding this comment.
Yes, among other reasons. The assembly now includes CV Envs as well. I'm open to further suggestions for the umbrella title. My initial idea was Managing content views, filters, and versions. WDYT?
I'm also uncertain about including CV Envs in the same assembly.
There was a problem hiding this comment.
Maybe "Managing content views and content view environments"? IMO filters and versions are just part of managing CVs.
As mentioned above, non-blocking from my side.
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
Lennonka
force-pushed
the
premig-mng-content-CVs-stories
branch
from
898374a to
6c3b523
Compare
|
Rebased. |
|
@jafiala or @aneta-petrova Can one of you, please, review the new structure? |
jafiala
left a comment
jafiala
left a comment
There was a problem hiding this comment.
I like it. When you agree on the name, it should be good to go. I don't have a preference in the name, all options seem reasonable to me.
4 participants
What changes are you introducing?
Restructuring the Managing content views chapter in Managing content
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into: