To Do

• help clarify webs vs. topics
  • breadcrumbs: either start with Ahat/AhatTWiki.WebHome (actually name of home topic) or set color of first link to web link color
  • flip sides of top bar so that contextual info about the current web is on the right (with the web palettes) while info about the current topic is on the left (with the topic palettes?)
  • or maybe:
    • have left of top bar be general entry for Ahat Twiki overall logo/entry, right side for contextual info, shrink top bar further, middle for web contextual tip of the day, broadcast message
    • topic tool palette (oh, I like that - heck, we're already calling the WebComponent Ahat/AhatTWiki.WebTools, so call the palette web tools dummy. geesh. not like I have to hit myself over the head much) in with topic area (name styles ahatTopic, goes in what is currently called natMain having eliminated all the natMiddle* and natMainLeft/Right/Both stuff). nice. let's try that.
  • meanwhile, login/logout and TWikiGuest get merged with the sidebar palette somehow

• color design
  • palette (was tool) links stay correct color when being edited - can achieve this through using TWikiForms

• toggle default behavior of rename script
  • currently defaults to search only current web for backlinks
  • toggle to search all webs

• a tips 'n tricks page to get people started
  • would grow to our version of TWikiTipoftheDay
  • actually, should be trivial to expand TWikiTopoftheDay - it just cycles through a named set of topics
    • gather them into a subweb, so they don't clutter an index, and cycle/random whatever away...

• Start A Topic
  • add words to the page similar to the perl stuff about how to find existing material on a topic, to encourage people to, at the very least, cross link with existing material). End this page, too, by on ing the sitemap.

• go back and add list of issues that led to this work
  • tool-driven perspective interface
  • save and continue editing button was broken - it took you from NatEditContrib back to TinyMCE
  • no direct route to NatEditContrib, so no access to TML editor, many facilities broken.

• approach
  • explain the list lump and label process we've been going through...

• utilities area (webcomponent == webtopicactions)
  • improve contextualized versions
    • find and add info about template logic to the ID log

• personalization
  • access control tutorial - extract existing text as a starter

• some functionality we'd like to add
  • blogs - that's easy, install the BlogPlugin (name?) from TWiki
  • it would be nice to offer a WYSIWIG editor as an alternative for those times you would like to use it, but not TinyMCE because of the way it attacks NatEditContrib. So someone needs to research alternatives
  • a chat facility
  • a drawing tool (I know of at least one plugin or contrib)
  • MathModePlugin
  • better version control

• submit some bug reports
  • specifically, when done writing up the story on our TWiki, submit a report concerning TinyMCE and NatEditContrib
  • also, the tooltips tend to get 'stuck' when editing on FireFox? (and Safari) in Leopard in NatEditContrib. (Anyone else notice that?)

• misc

Done

• TWikiThink? - a higher level topic - DigitalArtsSci.OrganizingContent grew into this
  • includes the current DigitalArtsSci.OrganizingContent - needs a better name
  • also a section (page) on rich cross linking, should include implementation info w/re how to use on and %SECTION%, etc
  • add a link to (if it exists, and it must...) and expand on a discussion of where things go. So include the discussion of community pages. End that page by on ing the sitemap.

• links in upper left, under current web/subweb (webcomponent == weblinks)
  • goes with utilities, really, as things get shuffled.
  • really like this to be a topics list, like KoalaSkin, see for example, BioWiki They use KoalaSkin. Want to know why we don't? That discussion is over in AhatTWikiInteractionDesign
  • research existing options, in parallel with moving current functionality to utilities area
  • if nothing else, take KoalaSkin's topic framework as a starting place, extract functionality and move on from there

• utilities area (webcomponent == webtopicactions)
  • improve contextualized versions
    • move welcome up there - moved to mysidebar instead
    • add a link to sidebar editor to first line - moved to mysidebar instead
    • shuffle, rename tools on second line (topic utilities)
    • label third line, revisit what goes there - moved to tools palette

• personalization
  • add discussion of community webs (yup, that is now AhatTwiki Guidelines)
  • highlight theme
  • access control tutorial - made template
  • webcomponent == mysidebar
    • take my most recent code, find the source code for mysidebar and make sure my patch applies

• web/subweb info
  • move to layered band, again like KoalaSkin, e.g., BioWiki - moved to righthand column
  • existing webcomponent, webbuttons