Database:

• Consolidate queries. A lot of queries can be rewritten and consolidated.
• Profile queries using slow-query mysql logging, and ADODB profiling tools.
• Optimize queries for speed.
• Possibly write some classes so all SQL queries could be in one file and be much easier to optimize.
• Allow user table sharing so same users are on related sites.
  • Related to Tiki Cloud item below?
  • See note at end of DatabasePrefixing

Blogs:
- Add check boxes for pings to major directories like Technocrati, and weblogs.com
- Add Atom API support
- Be able to promote blog enteries to the front page.

Newsletter:
- Newsletter\'s content should be database driven.
- Integrate PHPList?

Tiki Cloud:
- Create tiki cloud similar to Drupals to keep track of all the different TP sites.
- Could keep track of stats of different sites.
- Related to Database issue above about sharing info between sites in same DB?

Testing:
- Implement phpUnit for testing of core and packages
- Relies on all coding to be in classes, possibly a nice-to-have for Clyde

Enhancements:
- implement FeaturePackages and/or PackageVisionBtodoroff
- consider implementing phpGACL
- browser specific css import
- implement cascading icon themes

• implement TikiProShortcutIcon as part of IconThemes ?

- remove duplicate and extra queries during page views
- remove kernel dependencies of packages
- auto-generate Admin panel/Menus/Feature list
- centralisation of pagination (<div class="pagination"> occurs about 115 times (bonnie 29-04-2004)) - this is underway and is now function_pagination
- some sort of systematic and consise menu standard

Optimizations:
- Trim down TikiLib as much as possible by moving relevant functions into package classes
- Update or Remove QuickTags so data base access is not required for every page load to draw tool bar
- Move all third party code such as AdoDB, Smarty, PEAR, etc - to sit under utils/ - this will ensure code separation and modularity.