Transcript ppt

LCD CMS
TEAM ZOMBIE MONGOOSES
Content Management Systems
 A tool to separate web site content management
from back-end maintenance
 Features



Manage users, page hierarchies
Assign specific users to pages
Browser-based page editing
 Many existing solutions; all are too heavy/too light
to benefit those who would use CMS
 Middle ground?
Lowest Common Denominator CMS
 LCD CMS focuses on feature set & interface design:
 Restrict feature set to necessary, useful features
 Respect interface design process to ensure shallow learning
curve & ease of maintenance
 Ensure that user can express design creativity
 Appeals to business, organization, individual
What can ours do?
 Manage individual pages via browser-based text




editors & version control
Organize page structure by establishing
categories/hierarchies/etc
Control user privileges
Update content via alternative methods, a la
“blogging” semantic
Customize look and feel of web site via template/CSS
framework
System/Software Architecture
 LAMP
 Perl? Ruby on Rails?
 AJAX to simulate desktop app environment
Admin.
Backend
User/Page
Database
CMS
Front End
Version
Control
Page Editor
Client Side
Web Site
Lifecycle Plan
 User management system
 Page management system
 Page editor
 Version control
 Integration of users and pages
 Final UI touchups
 Documentation compilation
1 week
2 weeks
2 weeks
1 week
<1 week
Lifecycle Plan
 Schedule allows for flexibility – some useful features
may be added later
 Developers will at least need to learn PHP, pref. have
experience in web development and interface design
 Project can be scaled to fit 3+ developers; more
developers may mean some stages occur
simultaneously
Feasibility Plan
 Innovation in integration
 Features found separately in other CMS, wiki, blogs;
never found together
 Feature set intentionally sparse, with room for
growth as time permits
Any Questions?