Website To-Do List
This document is an effort to create a quick-and-easy centralized location to note website items that need to be addressed. They may be incorporated into the existing ticket system if desired, but often they are sufficiently minor such that creating individual tickets for each may be counterproductive. Please feel free to add any broken links, outdated statements, and the like that you may notice on the OCLUG website. ~ Lisa Lovchik, 2010-06-19
“About the Website” links to old wiki, old “further hardware details” page, old “site update process” page, old “access to the code (remote access) page, and deprecated www mailing list - fixed - Lisa
“About the Website” makes reference to and links the “Development Site” (http://devel.oclug.on.ca/
) - keep this as-is, or modify since the Wiki is essentially our “Development Site”?
“About the Website” describes Tux' hardware and software, and Tux is facing an upgrade soon. Keep and update this information, or remove it? How will we remember to come back to this and update it whenever the configuration is changed?
“About OCLUG” refers to meeting day being Tuesday, while referring reader to main page for exact room number of meeting. Remove this (to allow for atypical changes such as the recent switch to Thursdays), and refer to main page for time and day as well? See “Larger Issues” below. - fixed - Lisa
“Contacts” has broken link to deprecated mailing lists URL
- fixed - Lisa
(Lisa), we should remove as many internal links on secondary pages as possible, instead referring to the main page where the links can be found. This would eliminate broken internal links when changes are made to the website structure (e.g., switching from old wiki at http://oclug.on.ca/phpwiki
to new wiki at http://devel.oclug.on.ca
Is there a way to directly attach presentation slides to Past Meetings listings, so that below the description of a given presentation is a convenient link to the associated slides? Then, rather than creating a new Slides page every year where slides are on the Wiki and completely separated from context, the only link necessary would be where it makes the most sense - beneath the meeting date and description of the topic and speaker.