News, Events, Trends, Activities, Conferences and Notes to do with Web Culture, Development, New Media, Content Management, Mobile and PDA Access and Web Infrastructure
|
See Also: Home Links Personal Site Blogroll FriendFeed CV | |
Wiki Menu: |
Website Control PanelSome notes about requirements for a website control panel that would be aimed at site/content administrators. Ideally would result in elimination of local account creation, providing web site management in a through-the-web interface There are two distinct control-panel types or interfaces commonly available and each is aimed at different audiences. The first is more sophisticated and full-featured aimed at admins at ISPs themselves, providing low-level control over many services and systems like DNS, email accounts, generally automating many of the tasks the ISP has to perform to establish a host site for a customer. The second type is aimed at the users/customers themselves and allows them to view their site only and manage their own folders, access permissions, change error pages and view reports etc. Many of the available control-panels provide interfaces for both levels of control (i.e. admins and users) by challenging users to log in and determining their privilege. The need for this sort of tool (more site management than content) is driven by potential reduction in support load on us (W3T/ITS) to manage current sites by allowing trusted admins to manage some of their own services and parameters, and desire/demand for these distributed features/reporting by clients. There are plenty of sophisticated web based control panels (see links) and our requirements would be for a more restrictive mechanism than typically offered by ISPs but should be generic enough that's its useful to others. Many of the features will involve file-system changes, which would be carried out by some proxy user after the web admin has logged in under their own username. The proxy user might then edit .htaccess files (no direct access should be provided to .htaccess file from user) where the change involves configuring Apache's behaviour.
Typical/Possible FeaturesWhere possible integrate local existing implementations of web admin applications and skin them in the form of the control panel.
Other tools could also be integrated into a kinda admin-portal. e.g. the HTML validator, the metageta.pl script, meta data generation, quicksearch fails, and something like the MyGrater Could also allow them to manage the behaviour/style of their include files (e.g. SSI files) to change site look (example), navigation, style (see change_look.jpg)
File/Folder Management
Site Management and Reportingwould be useful to have an i/f where admins can select what they want reported on, when, and who the reports should be sent to, e.g. some of this might be extracted from CSV Analog reports and output from Jamie's log based billing script
Contact Management
User Management
Other FeaturesCommercial control panel products offer loads of low-level admin features that we are unlikely to ever need for both security reasons and due to the low demand for the functionality by clients. Following are some common control panel features we probably wouldn't provide:
Hosting SettingsMany web control panels allow an admin to control their virtual hosting settings which we'd probably not allow. Typical controls include..
Database Management
its unlikely we'd offer this when there are no dbase admins outside of W3T/ITS and there are dedicated client tools for the purpose (e.g. MySQLCC
ECommerce/shopping-cart
Mailing Lists / WebMail
|