Loading...
Roll Your Own Content Management System
Roll Your Own CMS
Evolution of a Content Management System
- June 2000……….Inherited static site at ist.psu.edu
maintained in NetObjects Fusion.
- Converted to Dreamweaver.
- Wrote proposal to set up
ColdFusion.
- September 2000
to January 2001..Set up ColdFusion Environment:
- Converted all display pages to
.cfm,
- Moved all information into
database.
- Created Add/Update Forms for
Own Use in populating site.
Roll Your Own CMS
Evolution of a Content Management System
user id
password
Forms
Database
- June 2001….Turned over first set of forms to
primary author: ist.psu.edu/news.
News editor was happy. I was happy.
- Summer
2001…..……Set up content management forms for
Web
all areas of site.
Began distributing forms to primary
authors. Trained them.
- Fall 2001……CMS fully functional and expanding to
ColdFusion
manage other office record-keeping
on Web Server
functions.
- Never looked back.
Roll Your Own CMS
Today
- 25 Primary Authors & Assistants Manage Content.
- Site has grown to about 2,000 records.
- Other office functions integrating with CMS.
- No longer “Webmaster –Typist.”
- Saved a lot of $$$$ & have gotten a lot of buy-in.
- CMS undergoes continuous improvement.
- I spend my time:
Refining Programming & Database
Setting Up New Dynamic Features
Documenting System & Processes
Training Staff, Students on ColdFusion, Databases, CMS
Learning New Stuff
Roll Your Own CMS
Advantages of Rolling Your Own
Can integrate more smoothly into current architecture
- Platform
- Security
- Software
- Database
- Network
Roll Your Own CMS
Advantages of Rolling Your Own
Possible to build incrementally, on as-needed basis
- Begin with high-need, high-return information
- Expand according to priorities
- Develop standards and employ code reuse, replication of forms,
templates, data structures…
Roll Your Own CMS
Advantages of Rolling Your Own
An Example of Building Incrementally
portal.psu.edu
News
Events Student
News
Alumni Home Custom
News Page News
Pages
events.psu.edu
Roll Your Own CMS
Advantages of Rolling Your Own
Can be more easily customized to organization’s needs
- data management needs: employee information, contacts…
- primary authors’ need/desire to maintain own content
- custom features: newsletters, calendars, news services
- integrate programming, technologies to populate other
services (e.g. XML)
- your Web site’s design, needs of different audiences
Roll Your Own CMS
Advantages of Rolling Your Own
Can be far less expensive
- In the Short-run
Creation
- In the Long-run
Maintenance
Expansion
Upgrades
Customization
Roll Your Own CMS
Advantages of Rolling Your Own
Can use existing resources
- Developers
- Database Administrators
- Designers
- Writer/Editors
- Software
- Programming
- Site managment
- Database
Roll Your Own CMS
Advantages of Rolling Your Own
You may already have the beginnings of one
- Current dynamic Web & data-management tools
- Sections of Web site already dynamic
- Database(s)
- Web site management tools such as Dreamweaver
Roll Your Own CMS
Advantages of Rolling Your Own
Maintenance and support can be less of a hassle
- No proprietary product shrouded in mystery
- No ephemeral vendor of prepackaged product
- If you built it; you can program for it
- Known site and database architecture
Roll Your Own CMS
Advantages of Rolling Your Own
You can enjoy low overhead
- can use open-source languages and server technologies
- online developer resources
- well-supported products (e.g. Macromedia)
- other programmers in your organization
- shared resources in your organization
Roll Your Own CMS
Advantages of Rolling Your Own
And finally, you can make it very scalable
- modularity
- code reuse
- uniformity, standardization of data storage, data display
Roll Your Own CMS
Challenges
- “Need it Yesterday” culture can lead to fast-paced development.
- Endless customizing and expanding becomes a maintenance & resource issue.
- Requires ongoing dedicated time of programmer(s). Job’s never done.
- Data may need to be rounded up and placed in unified environment.
- End-users must be brought on board – including the high-maintenance ones.
- Maintenance & support: You built it; you’re gonna maintain it.
- Need support and buy-in from many factions: administration, network/server
administrators, end-users, developers…
- No matter how you slice it, it’s a lot of work.
Roll Your Own CMS
Ask these Questions
- How complex are the requirements for this CMS?
- Will requirements change and grow over time? (Likely)
- Will the CMS end up integrating with a larger information architecture? (Likely)
- Who exactly will maintain the system?
- How will resources be managed as demands on the system grow?
- If your organization’s needs are hideously complex, do you really have the
resources to build and maintain? Or should you buy, instead?
Roll Your Own CMS
Some Advice
- Get buy-in at the start and support as you go.
- Develop Incrementally if possible.
- Use multiple products and tools if needed.
- Use skilled, full-time programmers, not part-time, temporary, or
inexperienced help.
- Manage expectations.
- Manage expectations.
- Manage expectations.
Roll Your Own Content Management System
Rose Pruyne
rpruyne@ist.psu.edu