Best practice for clients editing site

Events happening in the community are now at Drupal community events on www.drupal.org.
samwillc's picture

Hi everyone,

I've been giving this a lot of thought as I want to find a standard way of doing this to avoid making loads of changes in the future. I wondered what the rest of you do in the way of navigation to allow site admins/clients to edit their website.

I compiled a few ideas as so:

1) Let them use administration toolbar but with limited privileges once logged in (depending on role)
2) Add a navigation block into a sitewide region with links such as 'add content', 'view users' - depending on permissions/role
3) A new menu item that only appears when logged in (depending on permissions/role) - this would link to a whole new delta template with features like the standard 'add content' but also stuff like 'whos online' i.e. one page that does everything

Option 1 and 2 would allow users to do admin stuff from anywhere on the site. Option 3 would mean they would always have to return to that page for admin duties. Option 2 however means that you have to find somewhere on your page to stick a new menu. As an admin myself, I have 100% access so just use the admin toolbar no probs but it's quite tricky when considering all the different people that might be logged in at any one time and to find a decent way for them to easily edit/arrange content. I'm not talking about rearranging blocks or anything or layout stuff, just editing content/users/comments.

Option 1 also has the problem of a bunch of unauthorised menu options still populating the lists. Allowing 'Use the administration pages and help' permission (for 'content' link to show up in the admin toolbar - they have permissions for this) means 'structure', 'configuration' etc. all show up too, which they do not have permission for, and of course the links then go to an access denied page.

Any additions or how other people handle this situation would be most welcome :)

Thanks,

Sam.

Comments

I always wondered about the

eridolfi's picture

I always wondered about the best way to set up a site for edit by the client.

I set permissions so only a role can access certain features of the site. I found that the less the client has to look at the better.

Depending on the situation I will code some kind of administration bar into the header of a view (I use views a lot). I like to create interfaces with draggable views so the client can add a new piece of content, edit or delete existing content and drag the order of the nodes.

I am open to tips as well.

Thanks, maybe some others

samwillc's picture

Thanks, maybe some others will stick a bit more info on this thread.

I've been on this for hours trying different things and I have a bit more to add:

1) I feel a navigation (to add/edit) menu on EVERY page is unnecessary for a client
2) Admin toolbar should be OFF for clients - links to 'access denied' should not be there
3) I think a one page dashboard is the way to go and I'm going to work on one that I can implement and test to hell on my local site

Could possibly use dashboard module as the drag and drop is pretty slick. Need some blocks for them to drag and drop first, better crack open views and see what I can do.

Sam.

edit forget about dashboard, it's not as slick as I imagined. Actually doesn't work very well, drag and select all, and drop, oh, no, select all, drag and wtf?!

This may help

jjma's picture

Like you I've wondered about best practice for client hand over of completed web sites. I stumbled across this tutorial yesterday taken from the Dallas Drupal Camp called "Building a Drupal Site So a Marketing Person Can Manage It". It's quite informative, lists some of the modules they do and don't use, and gives a viewpoint based on his client experiences using their drupal 6 and 7 set-ups. Interestingly he advocates building custom views for the admin panel, dropping the use of panels and and context and using only nodes (with views attached via some listed modules). The url is below:

http://tutr.tv/t6039

Worth watching (some of the audio is a bit flaky)

Jon

Thanks for the input, will

samwillc's picture

Thanks for the input, will check out that video, it's really important to me to find a good (exportable) way of adding a generic admin area.

Sam.

Post your findings as I'm

jjma's picture

Post your findings as I'm sure the knowledge gained will be usefull.

One of the questions in the video (near the end) was which theme would he recommend. Answer: Omega.

Jon

I haven't got around to

samwillc's picture

I haven't got around to watching the video yet, but will at the weekend and report back. It's a subject that I think is very important and sometimes overlooked.

Sam.

Omega Framework

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: