Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
drupal_notes [2008-03-25 00:28] – 81.188.78.24 | drupal_notes [2008-03-30 18:40] – 81.188.78.24 | ||
---|---|---|---|
Line 96: | Line 96: | ||
* http:// | * http:// | ||
* http:// | * http:// | ||
+ | * http:// | ||
+ | |||
+ | |||
+ | |||
==== tutorials etc ==== | ==== tutorials etc ==== | ||
Line 105: | Line 109: | ||
* node_example.module: | * node_example.module: | ||
* node_example.install: | * node_example.install: | ||
+ | * embedding two views in one view (by putting php in the header.. good trick) | ||
+ | * http:// | ||
+ | * with paging: http:// | ||
+ | * documentation for contributed modules... if something is listed here it's probably a good sign of support. | ||
+ | * http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 144: | Line 158: | ||
* nicer: < | * nicer: < | ||
* how do breadcrumbs work? are they like a back button, or is there some other hierarchy? how is it defined? | * how do breadcrumbs work? are they like a back button, or is there some other hierarchy? how is it defined? | ||
+ | * seems that they are set by modules. there are a few different ways of doing it. | ||
+ | * it looks like the menu defines breadcrumbs by default..? | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * manually setting the teaser breakpoint: http:// | ||
+ | * what happens when you upload two images with the same name? | ||
+ | * the clash gets resolved automatically _0 (etc) is appended. | ||
+ | * where do you set the front page? | ||
+ | * admin/ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== delta specific ==== | ||
+ | |||
+ | === questions === | ||
+ | * should there be a name_of_activity: | ||
+ | * there should be some tag to differentiate between internal events (workshops) and other events. where internal events are not displayed in upcoming events (eg, residencies). | ||
+ | * overview images: should all of the images take you to a gallery, where images are viewed with lightbox? | ||
+ | * eg, images shouldn' | ||
+ | * what type will " | ||
+ | * maybe most things should be overview nodes? | ||
+ | * but don't show striking/ | ||
+ | * how to link to non-overview images in that case? | ||
+ | * where have all of the links for authenticated users come from? it looks like some module breaks something. | ||
+ | * a special node type for section pages or do them manually? | ||
+ | * the query is mentioned in the first factoid below. | ||
+ | |||
+ | === factoids === | ||
+ | * " | ||
+ | * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term. | ||
+ | * A workshop is an Event node with type_of_activity: | ||
+ | * an "Event Series" | ||
+ | * There exists both a Event node type and an type_of_activity: | ||
+ | * an Image node, for example may be tagged with type_of_activity: | ||
+ | * Overview nodes should only have one name_of_activity tag. | ||
+ | * Section nodes should only have one type_of_activity tag. | ||
+ | * there should be no two Overview nodes with the same name_of_activity tag. | ||
+ | * there should be no two Section nodes with the same type_of_activity tag. | ||
+ | |||
+ | === todo === | ||
+ | * logos on overview pages | ||
+ | * add the image galleries to correspond to name_of_activity tags (nik) | ||
+ | |||
+ | == 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. | ||
+ | |||