More detailed instructions when duplicating single pages in Schema

[kakoga]

Is your feature request related to a problem? Please describe. When single-page models are duplicated Zesty automatically creates a view and model in Schema. However, the newly duplicated model is not available in Content and is not available in Schema -> content model -> model settings -> parent. Before the newly duplicated model is available in those areas, the user needs to create a content item from the newly duplicated model by navigating to Content -> Create New -> select newly duplicated model -> fill out fields & click create. It's a confusing workflow.

My understanding is that the current behavior is the expected behavior. However, I would expect that duplicating a model would work in the same way as it does for creating a new single-page model which automatically creates an item in Content.

Describe the solution you'd like I would like further instructions in the UI that tell a user what they need to after they duplicate a single-page model. Eg. go to content, click on create new, etc. OR link to a doc (doc needs to be created).

OR

When a single-page model is duplicated pop up a dialogue box with options allowing the user to choose to automatically create a content item for the duplicated model. If the user select NO then let them know they'll need to create a content item Content.

Describe alternatives you've considered If we foresee a need for customers to be able to use model parenting in schema without a content item having been created - maybe we need to think about options around this??

Additional context here's a loom for more context https://www.loom.com/share/7a42ca983b644533a0a576e6357c4574

(related to Zendesk ticket #1871)
gz#1871

[shrunyan]

Interesting. The problem with creating an initial item is we won't necessarily know if we should, for example a headless or multi-page model it would arguably be not desirable to create an initial item. Additionally models can have required fields and so there would be the question of initial values. Potentially that could be bypassed if it made sense to do so.

Alternatively we could add an accelerator in that flow. i.e. After someone duplicates a model showing a direct link to new item creation with an explanation of why.