2. In general, if you can use WordPress, then you should use WordPress
3.
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
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
22.
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