Website
From Pyropopedia
Welcome to the home on the wiki for all things related to the Burning Flipside website!
Contents |
General Info
Current Web Lead: Benji Bradley (2011) ( webmaster at burningflipside.com )
Mailing List: [1]
Forums/Calendar, etc: [2]
Volunteer Team
| Who | Current Project(s) | Skills/Interests | Past contributions |
| !Bob | theme camp/art registration; volunteer registration | LAMP development, Drupal, Plone, Joomla | |
| Benji | Web Lead / Sysadmin / Coordination | Professional Drupal dev, Sysadmin & web/email hosting, etc. ; Web Admin '10 | |
| Chainsaw | |||
| Rob Grona | (available) | web app development | |
| Treg | Ticket Lead | newbie php/drupal | coder v1.0 of tickets & themecamp registration, coder v3.0 ticket registration |
| (Justin) Lee Billington | (available) | web/email design, marketing, deliverability | |
| Keegan Watkins | (available) | front-end: jQuery,JS,flash,html/css | |
| Logan Lowell | (available) | ||
| Ryan James | (available) | sysadmin, info/content presentation | |
| Sam Clayton | Drupal upgrades (?) | Drupal | |
| Tom Carlile | fixing bugs in ticket system for 2011 | PHP/mysql | |
| Patrick Boyd | deputy sherrif wiki admin |
Website Assets
What does the "Flipside Website" actually consist of?
- drupal site
- main pyropedia wiki (server directory: MediaWiki)
- other wikis (Ops, Rangers, PVC-defunct?)
- theme camp registration sub-app
- ticket registration sub-app
- volunteer registration/database (added by Ghost, 2/8/11)
- moop map (??)
- ...
- MOVED into Drupal fall 2010: lead nominations sub-app
Here's a brief functionality overview for the current Drupal site (August 2010, updated August 2011):
- custom visual theme / layout
- custom menus
- static pages
- downloadable documents
- feeds
- discussion forums
- custom content type: Art Registrations & Theme Camp Art Registrations
- custom content type: Flipside Flame
- custom content type: Flipside Theme Suggestions
- custom content type: Lead Nomination
- custom content type: Lead Nomination Feedback
- custom content type: Volunteer Profile
- role-based permissions to allow/restrict: creating/modifying/deleting records, viewing submitted records (some public info, some private). We currently have roles for administering: art, events, flame, groups, pages, website, tickets, volunteers
- polls/surveys
- user profiles
- user blogs
- events calendar, including countdown timer & repeating events
- can attach meeting minutes to some events
- private group w/ own events calendar, forums, polls, etc.
- captcha to prevent spam
Flipside Timeline
Important Dates for Flipside 2011:
- October - Lead Nominations, Lead Nomination Feedback
- December to January - Ticket Registration
- April 1st - Theme Camp Registration opens
- May - Flipside!
TODO list (unassigned)
drupal updates:
- do a module review & identify 6.x modules to switch to
- upgrade unsupported/revoked 5.x modules to stable versions
- update drupal to 6.x, and 7.x when it is appropriate
new stuff:
- update robots.txt to disallow search engine indexing
- make it easy for leads to publish announcements to the homepage
- add one-click volunteer buttons. recipient address is specified when creating button. sends email w/ logged-in user's info (maybe with webform? -BB)
- add ability for Flame to have accompanying podcast, create podcast feed
- re-create theme camp registration as a drupal content type
- create dmv registrations as a drupal content type
- install a per-node access module so that access can be granted for specific leads to maintain their own specific web pages (e.g. /email-lists maintained by list admin)
wiki:
- integrate login for mediawiki & drupal (possible MediaWiki plugin)
- it would be great to integrate the "other" wikis into the main wiki - possibly using alternate namespaces? - if we can figure out the proper access restrictions.
- enable file uploads by role for the wiki
misc:
- clean up old/unused stuff - lead noms, other?
- put the flipside website under source control so we can track changes & backtrack easily when necessary
contact form:
- move contact links to separate "Contact" link, add links to wiki areas; in the format: _Areaname/LeadRole_: _About_ - _Contact_
DONE:
- sooner: update drupal to latest 5.x (5.23 as of 11/01/10)
- update mediawiki for main pyropolis wiki (and others?) to latest version
Annual Tasks
Things that need to happen every year.
- Lead Nominations and Selection:
- update volunteer profile as needed (add new volunteer opportunities, remove old ones)
- update the website header & theme colors for the new year's theme (2010 was art from stickets, 2011 created by ryan james)
- get new leads list from volunteer wrangler, grant appropriate access as needed, remove access for old admins
- Art Admin
- Volunteer Admin
- Website Content
- Flame Editor
- Ticket Admin
- Area Facilitators
- Warehouse leads (and other Event Admins)
- theme camp registration enabling / disabling edit the pages at [3] and [4]
- update "art directory" view and art registration content type - updating text as necessary for the new land, rotate to the new year
- post new survival guide to website, update links
- post the new map & update link as appropriate
- update dates to reflect upcoming event and distinguish old events
- create stand-by information for registration assets to clarify when registration will open for the upcoming event and when it is/will be closed
- facilitate street name polls (sometimes: 2008 and 2009, skipped 2010, then again in 2011)
- give 'pollster' role to street signage lead, possibly related views, links, etc.
Volunteer Profile
The volunteer profile is a combination of CCK content type + custom module. The custom module provides the admin interface and exporting to CSV.
When updating the volunteer profile (to add or remove fields/options):
- update content type
- update database manually (is this needed? CCK should update above should take care of it-BB)
- update drupal's volunteer_profile.module:
- update SQL for counts
- update headers
Guidelines / Best Practices
- E-mail Addresses: Use the @burningflipside.com alias rather than the person's real e-mail
That way if the person receiving the email needs to change, we can simply change the alias in one place [staying DRY]
