�ݺ�ߣ

Editor's Notes

• #19: The Module Admin panel allows you to activate and deactivate the modules you have uploaded. A word of caution: some modules are dependent on one another. Also, if you deactivate a core module (it will let you) you could crash your whole website.
• #20: This is a typical content creation screen. This is not the only possibility, as content input can be customized with additional modules. Note the pull down menus, which are driven by the “Taxonomy” feature. The “Content Tag” field is a free text field (though it does suggest words as you type from existing tags). This behaves much like the Taxonomy, but allows a lot of flexibility in sorting and defining your content. Both taxonomy terms and tags produce aggregated pages and RSS feeds.
• #21: The Permissions Management screen presents a matrix of every feature you have enabled and every type of user you have defined (including “anonymous”). You can control who can do what, and what every sort of user can see. There is no separate public and production interface. Each user just sees and can use the fraction of the whole suite of features that you have assigned to his or her group.
• #22: Themes are pre-designed formats for your website which you can activate, just like modules, by simply downloading them from the web, uploading them to your site and activating them. You are supposed to be able to define which users can see which themes, but my experience in that area has been less than satisfactory. Maybe that has been improved. You might consider, as I have done, finding a theme with an architecture that works for you, and then change the stylesheets and replace the graphics to put your own brand on it
• #23: The Whitehouse uses Drupal. The box in the lower left is a typical Drupal feature. It was created using the standard input interface, and by selecting an appropriate entry type, or taxonomy term, it appears in this particular spot. It also appears in as many other placed on the website as the designers think best. The thumbnail and summary are controlled at the point the content is created.
• #24: This is my own personal Drupal site, which I use to support historical education and history related hobbies like “vintage dance” or re-enactment in Southern California. The column on the right is pulled from the event calendar, and the entries on the home page are there because, when I created them, I checked “Appear on front page”. Note also the search box in the upper right corner, the structured HTML menu in the upper left and the dynamic “book menu” on the lower left.
• #25: This is part of a project where I have been pulling together PDF scans of historical dance manuals and presenting them online. The “View the Book” link was created by a tool that allows me to upload files, such as PDFs, onto the website. The image of the title page of the document was uploaded using a separate “image uploader” tool. Neither one required any FTP tools. On the left is a “book menu”, created by adding “child pages” to build a hierarchy. Note however that the hierarchy is not ridged. If I change my mind, it can easily be changed in the editing interface.
• #26: This is a very useful standard Drupal feature that allows you to pull together multiple RSS feeds to create a single display, which also creates a single feed from multiple sources. I use this to populate the Library’s intranet site at work, as we do not have access to any such tool internally. The graphic on the right is from a feature called “blocks” that allows you to define a website element and then specify on what pages it will, and will not, display.
• #27: This is the film calendar for the American Cinematheque – a Hollywood based organization that shows classic and independent films in a couple of historic theaters. I designed the underlying architecture. This version of the calendar creates pop up boxes that display your summary and thumbnail, and do not require you to leave the calendar page to get basic information.
• #28: This contact form allows people to send you emails without you having to put your email address up on the web to be harvested by spammers. Other features include a pull down menu that allows the user to route the message to one of a selection of choices you have defined. It also uses “Captcha” to deter spamming.
• #29: This is a particularly nice example of a module that allows you to import MARC content into Drupal, with each record becoming a “Node” (i.e. web page). You can also export back to Marc as well as Endnote and other tools.