Notes for the new tasultimate.com website

The following things should be finished before starting on Stage 2

• Mostly DONE: A new TUA theme
  • Maz is making good progress on this
  • The following steps for implementing a new theme have been suggested:
    1. General layout of the page/banner/etc
    2. Theme up the main page ('story' nodes)
    3. Use the look from the main page to theme up other general pages ('page' nodes)
    4. Finally apply the theme to any outstanding pages ('league' nodes, etc.)

• A proper development site
  • Find a nice way of migrating changes from development/testing to the live site
  • Something like the Deployment Module might work

• DONE: WYSIWYG
  • Maz is keen on TinyMCE
    • there seem to be 2 version TinyMCE2/3 -JK
  • The WYSIWYG API Module has been installed
    • using TinyMCE 3
    • the CSS for the editor seems a bit stuff. I have added a tinymce.ccs file to the TUA theme, and suggest relevant changes be made there so that it give a good approximation of what the page will look like when saved/previewed) -JK
      • http://gerardmcgarry.com/blog/drupal-how-increase-default-font-size-tinymce
    • the default buttons look a bit crap as well. Might be worth looking at making them look nicer
      • http://www.ideasunleashed.org/ishmael/2008/08/improving-tinymce-interface-for-drupal-gets-a-facelift/
    • Fixed: Generates HTML on 1 long line, which isn't so desirable for the use of the Diff module
      • Selecting “Apply source formatting” in the WYSIWYG options makes the HTML code a bit more readable

• DONE: Page revisions
  • There is support for page/node revisions. A revisions tab appears if there are any revisions available for the page/node -JK
  • Not sure if revisions are turned on by default. They probably should be -JK
    • revisions can be turned on be default when configuring the content type
  • Doesn't seem to be a nice way to view differences between revisions. Need to look into this
    • The Diff module provides a nice comparison view
    • Fixed: TinyMCE might make this redundant as is generates HTML 1 line, making diffs less user friendly (differences are still in bold though)
      • Selecting “Apply source formatting” in the WYSIWYG options makes the HTML code a bit more readable

• DONE: Sort out the workflow of the site for authors/editors/approvals/etc.
  • Have a look at the Workflow module
    • seems to work OK for initial construction of the site
    • doesn't have support for unpublished revisions
      • something like Revision Moderation might be worth a look (though it is still incomplete)
  • Screencast: http://www.youtube.com/watch?v=J8RuQEbV_zU
  • Found: The Revisioning Module seems to do what I'm after - JK
    • It looks like the Workflow module can also be used to better control over revisions (ie. have a draft node that appears as not yet being ready for approval).

• DONE: A look at how Taxonomy can be used.
  • Classify different news items
  • Classify different Leagues/Tournaments (?)

• DONE: A review of the current TUA website
  • Have a look to see what should be kept - keep as much as possible
  • Look at how to restructure the information. The site map should be a fairly good guide.
    • Notes of what should go where at Meetings Notes - XX/05/2009
  • Also probably worth archiving off a few key things (news items), or the entire site (wayback machine?)

The following things should be completed before making the site live

• Populating the live site with information from the current TUA website
• Finalise how Leagues will be handled (should be their own node type)
  • Leagues
• PARTIAL: Slightly updated rego system
  • Unlikely that the new rego system will be ready
  • A modified/better-fied version of the Two-Hat system might work well for the time being -JK
    • USEABLE: TURS (TasUltimate Registration System) can be re-jigged a bit, with a new theme, to integrate with the website, until a proper replacement can be done.

The following things can be added after the site has gone live

• DONE: Calander
  • Information about upcoming meetings, pickup games, leagues, tournament, social events, etc.
  • Should be as automated as possible
  • Make use of google calendar?
    • would prefer not to -JK
• League Ladders
  • Automation would most likely require the new league management system
  • Look at alternative options in the mean time

The following things to be looked at, and would generally be nice to have. Can be added at any stage

• A favicon.ico
  • should be able to scale down the TUA logo
• DONE: Random banner image on page loads
  • would be nice to have before making the site live.
  • implemented with 'Banner Image' node and views
• Team/Player Blogs?
• Blog/News aggregation of other sites (ie. AFDA Trash Talk)
• DONE: Ability to easily upload new banner pictures
  • see above

• Site Map
• Meeting Notes - 04/12/2008