Last modified 4 years ago

Website development tasks

The following defines what needs to be done -- please add to this if I'm missing anything.

I'm not too sure about the timeline that will be required. My exam is on the 8th, so I won't be able to work much until the 9th. I will work to finish up as much as possible on the weekend (10-11), so ideally all of the decisions about products/prices/requirements, and the text content will be done by around the 12th/13th. At that point, I can work to include the content, change around the ePresence store to reflect all of the changes, and do general finishing touches/testing/cleanup to hopefully finish up by the 15th.

As things are completed, they can be entered on this page (ie: decisions about product lineup, text content, etc) or on a separate document, then emailed. I'll cross stuff out as it's implemented on the test site.

Test site is located at:  http://128.100.195.31

General

Rhys:

  • Overall site tightening
  • Code to handle menu
  • Testing in IE7/IE6/Safari
  • Site search? (probably not enough time)

Peter/Rhys?:

  • Integration of member page.

Solutions

Overview

Rhys:

  • Layout/design/images
  • Convert old flash news banner to use new images
  • Make all buttons/links work

Jonas:

  • Major ePresence description text, currently "The world's first open source..."
  • *Maybe* some sub-description text, currently "ePresence is designed to support conferences... etc"
  • ~60-75 words about webcasting/conferencing
  • ~60-75 words about solutions
  • ~60-75 words about products
  • ~60-75 words about community

Jonas or Peter:

  • Get proper sales telephone number

Education

Rhys:

  • Layout/design/images (mockup done, not yet on test site)

Jonas:

  • Overview text (15-20 words) about ePresence in Education
  • 2 paragraphs about a case study (ie: SickKids? ...)
  • ~25 words for quote about case study

Jonas or Rhys or both:

  • Find good logos to represent the organization in case study

Healthcare

  • Same as education

Government

  • Same as education

Industry

  • Same as education

Products

Overview

Rhys:

  • Layout/design/images

Jonas:

  • 15-20 words OR a *very* short blurb (like 5 words, as in current site) that will show up on the header image of the page
  • ~60-75 words about supported software
  • ~60-75 words about capture stations
  • ~60-75 words about media servers and hosting
  • ~60-75 words about open source

Supported Software

Rhys:

  • Layout/design/images

Jonas:

  • 15-20 words OR a *very* short blurb (like 5 words, as in current site) that will show up on the header image of the page
  • Descriptions about our packages (? MUST DISCUSS)

Capture Stations

  • Same as supported software

Media Servers & Hosting

  • Same as supported software

Open Source

Rhys:

  • Layout/design/images

Jonas:

  • Not sure yet, will fill in later.

Community

Overview

Rhys:

  • Layout/design/images

Jonas:

  • 15-20 words OR a *very* short blurb (like 5 words, as in current site) that will show up on the header image of the page
  • 60-75 words about documentation
  • 60-75 words about our trac site
  • 60-75 words about our blog
  • 60-75 words about research

Documentation

Rhys:

  • Layout/design/images

Code

Rhys:

  • Layout/design/images

Blog

Rhys:

  • Layout/design/images

Research

Rhys:

  • Will use current research papers page, with a few tweaks

People

Rhys:

  • Will use current people page, with a few tweaks, updates to who is involved

Presentations

Rhys:

  • Update to work with new type of menu
  • Fix problems with popularity (at least a day needed?)
  • Make sure everything looks right with new width of site
  • Make sure search still works
  • Update submenu to new style? (maybe automatic)

Store

Jonas:

  • Get Moneris account information

Jonas/Rhys?:

  • Set Moneris account up to receive sales

Jonas/Peter?:

  • We need to clearly define all of the products we sell (all supported software packages, all capture stations, all media servers/hosting packages).
  • Define what categories these products fit into (are we categorizing by webcasting/conferencing solutions, or by the actual product type... ie: supported software, etc?)
  • Define prices.
  • Write descriptions for all products that we sell (for new products, or for products we currently offer if description should be ddifferent from what's there currently)
  • Clearly define categories and all products we are selling.
  • Determine all prices.
  • Define what additional information should appear on product information page, along with description (requirements, specs, etc?)

Peter:

  • Define system requirements for all products we are selling. This includes requirements for support packages. Hosting packages?

Rhys:

  • Once all products/categories are defined, enter into database.
  • Maybe will need to make changes if we're categorizing by webcasting/conferencing rather than actual product type
  • Fix bug when pressing back button on checkout page (forgets province?)