Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
delta_notes [2008-04-01 17:11] 81.188.78.24delta_notes [2008-09-07 12:13] (current) 81.188.78.24
Line 13: Line 13:
   * a special node type for section pages or do them manually?   * a special node type for section pages or do them manually?
     * the query is mentioned in the first factoid below.     * the query is mentioned in the first factoid below.
 +  * how to associate images with an individual node (eg, an event) without needing to make a new tag? 
 +  * where do attachemnts for biblio nodes end up, and is it possible to have a URL alias defined for the attachment. 
 +  * what type of node should 'fieldwork' be, and how to provide an overview (ie. 'Overview' vs. 'Section')? should a 'Seciton' node include related 'Article' nodes based on type_of_activity? 
  
 ==== factoids ==== ==== factoids ====
 +  * Most pages should be 'Overview' nodes. The content type 'Overview' is used to make pages that include, or reference other content (eg. images/related projects,etc+)
   * "Productions" page will list all Overview nodes with type_of_activity:Productions tagged with a root term from the name_of_activity vocab.   * "Productions" page will list all Overview nodes with type_of_activity:Productions tagged with a root term from the name_of_activity vocab.
   * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term.   * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term.
Line 31: Line 34:
     * upcoming and past events     * upcoming and past events
     * i did this with a node-specific theme.. the events node is node 114. the theme is in node-114.tpl.php.     * i did this with a node-specific theme.. the events node is node 114. the theme is in node-114.tpl.php.
 +  * publications overview text is implemented as a block. http://delta.fo.am/admin/build/block/configure/block/4
  
  
 ==== todo ==== ==== todo ====
 +  * decide what to do about forums & comments
 +  * check 404 & 403 templates
 +  * url redirections from old site
 +  * add link to subscribe to update list
 +  * display 'related events' on events pages, as seen on the 'overview' pages.
 +  * sort 'related events' by most recent -> most ancient
 +  * positioning of teaser images in 'related' section
 +  * teaser images for events in 'related' section
 +  * address field in event (needs CSS improvement)
 +  * prosaic tag block (providing context for a node in terms of how it relates to other overviews, or types of activity)
 +    * look at the phptest block... you can determine the nid of the current node by inspecting the url path via the arg(x) values
 +  * improve layout of publication pages
 +  * when selecting images from a $tid (eg. using 'get_images' in foam.php) check if the gallery has subgalleries, and include their images also. (possibly: http://api.drupal.org/api/function/taxonomy_get_children/5)
 +
 +=== done (as of 2008-05-20)===
 +  * (probably just for section pages) find out the image gallery that an image is in and add that as the lightbox link.
 +    * in ''node-section.tpl.php''
 +  * events should pull in images.. but from where?
 +    * there is now a node-event.tpl.php
 +    * events can be tagged with an image gallery, a selection of images from that gallery will appear at the bottom of the node
 +  * don't show "upcoming" unless there are actually upcoming events.
 +    * changed in node-114.tpl.php
 +  * timezone in event (check named div & default tz)
 +    * this change made in ''modules/event/event.theme:theme_event_nodeapi''
   * logos on overview pages   * logos on overview pages
-  * add the image galleries to correspond to name_of_activity tags (nik) 
-    * by the way, the heirarchy doesn't have to match, just the text of the names. 
-  * events should pull in images too? 
-  * prosaic tag block 
   * images in teaser block   * images in teaser block
-  * address field in event 
-  * timezone in event 
- 
-=== done === 
   * section overview images?   * section overview images?
     * working in theory but nothing is tagged appropriately?     * working in theory but nothing is tagged appropriately?
   * the problem with tags like "None", is that they appear quite high in the tag cloud. I think any tag that has a "none" option should just not be set required.   * the problem with tags like "None", is that they appear quite high in the tag cloud. I think any tag that has a "none" option should just not be set required.
 +
  
 === would be nice... === === would be nice... ===
-  * (probably just for section pages) find out the image gallery that an image is in and add that as the lightbox link. 
   * end date on event should get set to the start date? or maybe only when opening the calendar to allow leaving the second date blank.   * end date on event should get set to the start date? or maybe only when opening the calendar to allow leaving the second date blank.
- +    * the end date doesn't get displayed if it's the same as the start date
  
  
Line 63: Line 81:
  
 Each Overview page needs to be tagged with exactly one tag from the "name_of_activity" vocabulary. This tag determines where it will appear on the website. If the tag you choose is a child of another tag, the Overview page will appear in the list of "related projects" in the overview page with the parent tag. Each Overview page needs to be tagged with exactly one tag from the "name_of_activity" vocabulary. This tag determines where it will appear on the website. If the tag you choose is a child of another tag, the Overview page will appear in the list of "related projects" in the overview page with the parent tag.
 +
 +If the Overview page has no parents, it will appear in the relevant Section page based on its "type_of_activity" tag.
  
 Before creating an Overview page with a particular tag, you should do a search to check there isn't already a page with the same tag. If there is, you should edit that one instead, or delete it. Before creating an Overview page with a particular tag, you should do a search to check there isn't already a page with the same tag. If there is, you should edit that one instead, or delete it.
  
-... 
  
-=== where do the images comes from? ===+ 
 +=== where do the images come from? ===
  
 == on an overview page == == on an overview page ==
Line 86: Line 106:
 == on a section page == == on a section page ==
  
-//good question. possibly we should determine the gallery that each image belongs to.. in both cases.// +the images link to the image gallery that the image comes from.
  
  
  
  • delta_notes.1207069898.txt.gz
  • Last modified: 2008-04-01 17:11
  • by 81.188.78.24