Itasca

Brain dump of rough edges for Itasca:

Wiki:

• Tagging
• Autocomplete
• Define: creates a weird uex
• Better uex for finding and viewing tags (discoverability)
  
• Link dialogs
• Dump inline dialogs code?
  
• Templates
• Base
• Deuce
• Self-serve
  
• Custom HTML areas for Base and such
  
• Inline title editing
• How would new pages be handled?
  
• Double scrollbar (editor + page) is frustrating. Maybe if the editor always expanded to 100% of the page's contents (including when new content is added) we'd get a better experience. See the idea as an implementation with a normal textarea.
  
• Dual nav pane modes is crappy (e.g. loading editor disables it, but there's no visual indicator of that)
  
• Watched pages - what are we doing with this feature?
  
• Cached config values
• Some files (like _jscripts.php) need access to certain config values, and I'm loathe to run those through the index.php codepath for performance reasons - what I'm thinking is when I do a GET:config, I check last-modified header; if it's different, I take the PHP variables I know I need and write them to LocalSettings.php). In a sense, LocalSettings.php will become a cache of config values PHP knows it needs
  
• Refactoring of Title/Page objects to reduce # of calls to API (the initial implementations were all precise surgical changes since not all page-related features were expected to be completed by hayes - we need to start making architectural changes)
  
• Refactoring of User object to prevent so many friggin calls (either that it needs to do some memoization)
  

Infrastructure for hosted:

• Set up a separate server that is optimized with lighttpd or something for static files
• Set them up on a separate domain so the cookies are not transmitted
• Fragment JS across multiple domains so we can get them concurrently (already doing this with Yahoo CDN)