-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement]: Move Site Assets in PersonaBar to "Content" section #6157
Comments
@iJungleboy I agree :-) |
Maybe I am overstating the obvious (or not seeing the reason for the exception), but this would also apply to Global Assets, right? Additional opinion: do this in v10, not 9.x. |
IMO not as Content is for the most used options for Admins? |
Global assets are assets outside of the current site, which are not usually something the content-editor should be working on. For when to do it - as soon as possible of course ;) But yeah, a v10 is probably a good moment, as we hope to get it out soon ;) |
@iJungleboy Agreed |
I (mildly) don't agree. The Global Assets (correct me if I am wrong) is only visible to the Host/Super. The Global Assets is also identical to the Site Assets, its the (newish) Resource Manager and the only difference is where the root is. These Assets are still Content. For example, it is where I would put Content shared across portals. I am being a little too semantic on the 3 PB labels: Content, Manage, and Settings, but if Site Assets belongs in Content (which I agree with), that is where I would expect Global Assets to be also. |
Is there an existing issue for this?
Description of problem
ATM the site assets appear in the Manage menu
Description of solution
For various reasons such as usability and compatibility with the new user permissions, it should be moved up to Content, ideally right after "Pages"
Description of alternatives considered
Anything else?
related to #permi
Do you be plan to contribute code for this enhancement?
Would you be interested in sponsoring this enhancement?
Code of Conduct
The text was updated successfully, but these errors were encountered: