UX - Using tabs instead of steps


[story] As a user, I prefer tabs over steps, so I can apply changes to an existing type/object in which the steps are not interdependent, with the least possible actions/clicks.


[required] Using steps for new objects/types and tabs for editing those would imply that (i) the current steps component must be isolated from its view(s), (ii) a similar tabs component should be created and (iii) the original views need a property that dictates how the element groups must be rendered: steps or tabs, and provide the necessary element groups and step/tab headers to the render.

[nice-to-have] Since steps are great for beginners UX, this could be an option instead of a replacement. A global config can dictate which mode is used for which action (create/edit).