4 types of primary content; activities, events, publications, blog posts

other objects; static pages, people, 'supported by', studios, etc

an activity can be singular entity or grouping entity. one activity can be a part of another activity. an event, publication, static page or blog post can be part of more than one activity. each activity/event/publication/etc should be able to be presented with related material (or links to it). each activity has 'support' and 'people' that need to be credited.

activity should include text (summary and body copy), slug (named url), a main image, an image gallery, 'supported by' line (including relevant logos) summary of people involved, summary of related stuff (events,publications,other activities)

requirements pre-launch

1. chronological overview of events
2. titles/links for main menu and way to update main menu (add/edit/relink entries)
3. blog (i.e. chronologically ordered blog entries)
4. overview of publications (ordered by type)
5. people objects, linkable to activities, publications and events
6. import existing drupal nodes (details required)
7. consistent urls from previous site
8. relevant data for studio objects
9. 'supported by' objects
10. 'view full project [+]' → 'view more [+]'
11. comments fr blog posts (at least for now) using disqus
12. static archive of existing drupal site
13. way of presenting home page content that doesn't have an image
14. include flickr images as 'main' image for a page
15. current and inactive distinction (for activities and events)

critical pre-launch

1. all (or most) of above

critical post-launch

1. relevant graphics for as many activities as possible
2. documentation on workflow/editing/updates
3. how to add new material.
4. how material is organised and can be reorganised if needed.
5. how images are organised, e.g. links flickr sets and project images
6. workflow examples (e.g. adding new event, starting new project, adding pics from events)