Hi Ryan,
> I've run into this before - I guess I just take it for granted that
> the admin interface is easy to use, because _I_ like it. But that's
> not the case for everyone. I'm curious, what about the Admin interface
> is daunting to your scientists, and how might it be improved?
1. Too much information - we have some people producing El Nino forecasts,
some El Nino monitoring information and another set maybe
some sort of summaries.
Typically any one of these people have to access a certain
page within the tree. Since we have a variety of products
and many categories under each product, the typical
"content provider" in APCC tends to get a bit lost in
the branches and trunks of the Page tree, so to say.
o It would have been nice if the "content provider" could
chose to hide the branches and trunks not of interest to
her/im.
o This step may be done by the administrator instead.
This may help protect the integrity of the system. We
may not want all content providers to modify any of the
pages in the tree. Currently any logged in "content
provider" can modify anything s/he likes
2. Images - As you may have noticed, we need to display lots and
lots of images. It is not quite that easy to deal with
images through the admin interface.
Radiant does not have support to upload images.
But this is well-supported by extensions. However,
in my experience, it is *not* painless to use the
uploaded images. One has to use a set of tags to
incorporate the images into the pages (not too
convenient).
Adding images to suddirectories under the public directory
is an option. However for security reasons, out sysadmins
do not permit "content providers" to access the Radiant
root directory. Even if they upload to a ftp area in
the server, there is an additional step of moving those
files into the Radiant public directory
o It would be nice to have a convenient way to access
images through the Admin interface and to easily
(less typing, yet intuitive) 'markup' the images in
the associated pages.
Mainly these are the items. So what I did was to make a customized
client for each of our "content providers". Since I understand the
common-language used in this community, it was more convenient to
go this way... also a convenient way to restrict access to the
Radiant admin interface.
saji
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
