You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideas/possible composition for the backend system.
I imagine that each brand "project" is displayed with it's primary colour in the interface, informing the thumbnail and header background for easy identification and brand distinction.
The admin UI could be fairly transparent, with minor interface differences between it and the client-side "guide" document. The top bar, for instance, would disappear, along with other "edit" buttons/widgets when a "client" views the guide.
These shots are from the "designer" point of view. Each project member would have either a "designer" or "client" role (determining their editing/viewing capabilities).
The text was updated successfully, but these errors were encountered:
This is good for later, but probably wouldn't focus too much on the application front-end until we're ready to work on it (beyond ideas etc). But yeah I think there is an important question still in these mockups:
Will a user login to see multiple accounts?
Or will they login to each brand account separately?
Can we have both - and the login to view a brand (not edit it) is just a password (for clients)?
Therefore, the early version of the app just has a single "admin" login for us to create new brands... or maybe it has no admin login at all?
Ideas/possible composition for the backend system.
I imagine that each brand "project" is displayed with it's primary colour in the interface, informing the thumbnail and header background for easy identification and brand distinction.
The admin UI could be fairly transparent, with minor interface differences between it and the client-side "guide" document. The top bar, for instance, would disappear, along with other "edit" buttons/widgets when a "client" views the guide.
These shots are from the "designer" point of view. Each project member would have either a "designer" or "client" role (determining their editing/viewing capabilities).
The text was updated successfully, but these errors were encountered: