Customize the Backend/User-Experience
Permalink
Now, I'm gonna rant a little bit, but it's a pretty interesting issue I thought of.
Everyone says Wordpress is awesome because it's super-duper easy to use, but let's face it - WordPress sucks, and WordPress is really badly-coded (Says me after a more-than-5-thousand-tables installation of Multisites failing a client at the worst possible time).
Nevertheless, Wordpress blogging tools are pretty cool, and people are USED to customize it (Locking areas and such) and editing with it.
Now, I never needed to customize much of Concrete5 admin area, and there are roles and such, but sometimes I think about things that could work better for some specific projects.
One of the most important things I run into and can't get to a solution is: You need to control your user.
So how could I customize the user-experience such as to give him/her an interface with the most common editions he/she could do, preferrably designing this (or those) screen(s)? It's somewhat against the "Concrete5 Principle", but what if I just want a user to be able to update a Banner? I have to give support to people that are hired to do things like that, and sometimes I can't see C5 making their lives easier (Which is sad, because as I said, I love C5).
Should I just develop a "Backend" on a Frontend page, make it accessible only for logged-in users with "x" permissions, then design the whole said "Backend" the way I want it, and then assign a ton of fuctions/areas, such as composer etc., to specific parts of it?
Or is there an easier way to simplify that?
If there isn't, I believe this would be a major upgrade, worthy of the Core Team attention.
Everyone says Wordpress is awesome because it's super-duper easy to use, but let's face it - WordPress sucks, and WordPress is really badly-coded (Says me after a more-than-5-thousand-tables installation of Multisites failing a client at the worst possible time).
Nevertheless, Wordpress blogging tools are pretty cool, and people are USED to customize it (Locking areas and such) and editing with it.
Now, I never needed to customize much of Concrete5 admin area, and there are roles and such, but sometimes I think about things that could work better for some specific projects.
One of the most important things I run into and can't get to a solution is: You need to control your user.
So how could I customize the user-experience such as to give him/her an interface with the most common editions he/she could do, preferrably designing this (or those) screen(s)? It's somewhat against the "Concrete5 Principle", but what if I just want a user to be able to update a Banner? I have to give support to people that are hired to do things like that, and sometimes I can't see C5 making their lives easier (Which is sad, because as I said, I love C5).
Should I just develop a "Backend" on a Frontend page, make it accessible only for logged-in users with "x" permissions, then design the whole said "Backend" the way I want it, and then assign a ton of fuctions/areas, such as composer etc., to specific parts of it?
Or is there an easier way to simplify that?
If there isn't, I believe this would be a major upgrade, worthy of the Core Team attention.