1 / 9

LCD CMS

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

janaya
Download Presentation

LCD CMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LCD CMS Team Zombie Mongooses

  2. 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?

  3. 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

  4. 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

  5. System/Software Architecture • LAMP • Perl? Ruby on Rails? • AJAX to simulate desktop app environment Version Control Admin. Backend User/Page Database CMS Front End Page Editor Client Side Web Site

  6. Lifecycle Plan • User management system 1 week • Page management system 2 weeks • Page editor • Version control • Integration of users and pages 2 weeks • Final UI touchups 1 week • Documentation compilation <1 week

  7. 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

  8. 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

  9. Any Questions?

More Related