1. Introduction to CMSesWordPress, Omeka, and Drupal Patrick Murray-John & Raf Alvarado THATCamp / CHNM June 3-5 2011

2. In general, if you can use WordPress, then you should use WordPress

4. What is a Content Model? Mediates between the data model of the database and the emergent information architecture of the site. Allows site builders to represent and organize content -- e.g. source material in the form of images, text, and metadata. Content is complex -- media objects (e.g. image and detail, book and page), technical metadata, semantic metadata ...

5. Each CMS has a set of content modeling affordances based on . . . Elementary units e.g. pages, nodes Connective devices e.g. tagss, categories Display methods e.g. widgets, feeds Combined, these produce emergent patterns

6. Simple Hypertext PAGES . . . have LINKS No displaydevices per se Examples: HTML and Wikis … From Nelson’s Computer Lib/Dream Machines

7. WordPress PAGES Subpages  Fly-out menus, menu widgets POSTS Tags  Tag widgets, list pages Categories  Category widget, list pages Content is accessed by browsing, menus, and widgets

8. Results in “Dendritic Hypertext” Image taken from Shirky’s “Ontology is Overrated”

9. Content Modeling in WP WordPress – map pages, pages, categories,and tags onto content domain E.g. Courses Pages = Syllabus items Posts = Lesson resources Categories = Course Schedule Tags = Resource subject and format

10. Omeka has Items ITEMS COLLECTIONs DC metadata Keywords Tags  Browsable list pages Content is accessed by Browsing and EXHIBITS

11. Results in “Axial Hypertext” Image taken from Landow’sHypertext

12. Drupal NODES Menu paths  Menus, blocks Arbitrary fields Views Node references  Linked Views, backrefs Taxonomies  List pages, Views Outlines  Books Content is accessed by Browsing, Views, Books, Panels, and other devices

13. Drupal Content Models are like Relational Models Each link represents a “node reference”

14. Results in “Rhizomic Hypertext”

15. Detail view of a node and associated node references

16. Content Model for Lived Theology Project

17. Content Model for Nursing History Project

18. Summary before looking at examples

21. Some Salient Differences Specific vs. General content modeling WordPress is general Manual vs. Automatic site organization Omeka is manual Paradigmatic vs. Syntagmatic affordances Drupal is highly paradigmatic

23. Use Cases WordPress Course sites, personal portfolios, blogs (of course) Omeka Exhibits, simple thematic research collections Drupal Collaborative projects, complex thematic research collections, data meshing

24. Example Drupal Sites House Divided Lived Theology Nursing History Cultural Landscapes MediaBase