Restructure wp-admin

[ryan]

#2525 restructured wp-includes. Let's do the same for wp-admin.

• Move includes to wp-admin/includes
• Leave template files in wp-admin
• Break admin-functions.php into smaller files
• Organize include files along DB and template helper lines as in #2525

Possible wp-admin/includes

• schema.php
• upgrade.php
• post.php
• bookmark.php
• taxonomy.php
• comment.php
• plugin.php
• user.php
• ...

And corresponding foo-template.php as needed.

+3.5. The file structure (or lack thereof ;) ) has always irked me.

Also, would it be worth it to do pretty permalinks for the admin?

(In [5542]) Admin includes reorg. see #4334

That breaks up admin-db and admin-functions into something more sane. I'm itching to reorg the template files too since there are almost seventy something inconsistenly named files in wp-admin. Two approaches to renaming.

• post/create.php
• post/edit.php
• post/form.php
• post/manage.php
• post/update.php

Or...

• post-create.php
• post-edit.php
• post-form.php
• post-manage.php
• post-update.php

I like the directory approach. It provides a pretty permalink style via its structure. The related js and css files can also go in the directory, reducing clutter in wp-admin.

(In [5545]) Fix include path. see #4334

I like the directory approach also. Keeps things sane.

Also, for pages that add_submenu_page() for one of those now-existent pages, should there be compatibility checks? Or is it going to be fine?

[5549] fixes a typo

Oops, ignore that. Wrong ticket.

(In [5631]) Move JavaScript to js subfolder, and CSS to css subfolder. see #4334

(In [5632]) Whoops, forgot about wp-login.php. see #4334

(In [5634]) Revert some links. see #4334

(In [5635]) Ugh. We need to consolidate these headers. see #4334

(In [5665]) Update CSS paths. see #4334

Let's call this fixed for 2.3.