HALF DONE : Allow modules to provide pages in the backend, that substitue for ones in the forms and listings directories, as well as ones in actions, queries, somehow (and also sub forms for cms_page) - Still need actions and sub forms
Build modules like comment with installer files that can set up their tables for them
Write a core component that turns table definitions into SQL statements, so that it can do a compare to find rows that have been added since the previous version and create ALTER statements to add them.
Integrate front_end_user_types with the permissions pane in cms_page (using the mechanism above?)
Make installer spit out table definition files rather than SQL? Maybe 1 file for tables, and a SQL file for Data? Problems with serialized data in content files?
Make cms_browser deal with previews / summaries / whole page content to do blog style listings
Extend categories to allow auto-naming of new pages in that category (again for blogs) and 'New Page Here' stuff