Fish Wrap Work Log

This page logs the work done by Jonah Kellman as part of his work-study position for Hampedia. Due to a handwriting error, this position is named "CS Fish Wrap Programmer."

The office hours for this position are Tuesdays and Fridays, 1-4pm in ASH.

To-Dos
Any Hampedia folks: feel free to rearrange this to prioritize, otherwise, Jonah, please assume the topmost item is the highest priority.

|"Good formatting":
 * Devise advertising techniques for Hampedia/Hampedia Project
 * Possibly use Piwik (mentioned below) or google analytics data, or other visualization data (Network-vis on the collection of hampedia pages? On history of oft-edited pages? Who knows. Lots of cool shit here)
 * Talk people into using Hampedia:
 * Especially to add content (fixing formatting is easy)
 * Generally improve formatting (do any of the below):
 * Find poorly-formatted pages and compile a list (on Hampedia or elsewhere) of pages that could use better formatting (and don't be afraid of improving user pages!)
 * Improve formatting on said pages
 * Create a template to mark poorly formatted pages (use Semantic Mediawiki (see section later on that) to autogenerate a list from pages with this template on them, perhaps). Make it unintrusive, though, wikipedia's templates for this are shitty and annoying
 * Use section breaks
 * Don't have empty sections
 * Link to other pages
 * Link to wikipedia where relevant (use Link Text -- see MediaWiki documentation on interwiki links)
 * Use templates (especially the assorted boxes)
 * All the shit I forgot, look at good pages and emulate
 * Generally improve content (do any of the below):
 * Find pages low on content and compile a list
 * Create a Template (perhaps Template:Stub) to mark low-on-content pages (see comments on Semantic MediaWiki above)
 * Write pages, especially documenting events, locations, and people (documenting history, even if current -- we're especially bad on high-resolution data on locations (i.e. specific rooms))
 * Move pages of people to their preferred names (redirects will be automagically created)
 * Create redirects for common names of buildings and events
 * Add images to pages, especially images that are uploaded but appear nowhere (https://hampedia.org/wiki/Special:UnusedFiles)
 * Add categories where relevant, and get rid of unuseful/stupid categories. Also, the category pages themselves can sometimes use some sprucing-up
 * Improve templates:
 * Make empty lines not appear in boxes (requires some familiarity with mediawiki parser functions)
 * Make sure everything's formatted/designed about the same (Alumnibox is screwy right now, I think?)
 * SEMANTIC MEDIAWIKI

There is so much improvement that could be made in this category I don't even know where to begin saying what you should do except reading the documentation at http://semantic-mediawiki.org of course Most of the improvement for this is in templates, and then later creating useful aggregation pages (or replacing current manually-created aggregations)


 * Suggestions from Fred's email (some require access to pitus, technical expertise, etc):
 * Updates for mediawiki (from svn, preferably)
 * Extension management (especially purging unuseful or obtrusive ones and updates (also, installing http://www.mediawiki.org/wiki/Extension:EasyTimeline would be cool -- I already use it, in a roundabout way, for The Omen's page))
 * Domain name/SSL management
 * Mobile CSS
 * Piwik and displaying of aggregate data
 * Security auditing
 * Make maps... better (possibly better data for Hampshire specifically, put into openlayers?)
 * Assorted bots:
 * Course/Student/etc. data (talk to IT offices to get data, then write bot to use it)
 * Update the Spotlight periodically (edit Template:Spotlight)