I have the following relations between the entities:
- a user can have multiple projects
- a user can have multiple scripts
- a project can have multiple scripts
So, a script can belong to a user or belong to a project. My idea is to consider the script a separate entity regardless the "parent" entity (user or project). I have several questions
Clicking the edit button (first mockup) will redirect the user to the script page (second mockup). Is it acceptable to "lose" the project header/context?
- I could prepend the script name with the project title to give the user more context (
Project Title > Script Name
) - I don't know why, but I have a feeling that only the content below the tabs should change when I click the edit button but this will lead to unwanted behaviour. For example, if the user is editing a project script he will get two sets of tabs.
- I could remove the tabs from the script page and have everything in a long list but the question still remains: is it acceptable to lose the project header/context?
- I could prepend the script name with the project title to give the user more context (
In the second mockup I have two buttons on the bottom of the page. Even if the tabs change (general, configuration, dependencies) the buttons will stay there. Those tabs are there just to avoid having too many fields one below the other. Will the user see this as a form with multiple sections? Users might think that the save button is only for the current tab.
My main issue is that the "script" is a primary entity (for the user) and a nested entity (for the project) at the same time. How would you improve the UX in this case?
user > script
, second one isuser > project > script
. Is if ok if I use the same edit page in both cases? – Andrei Oct 28 '16 at 21:51