WordPress 3.3 Proposed Scope

This document will not be finalized until the conclusion of the IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. meeting today. Per last week’s IRC meeting, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team has reviewed the potential features/projects for 3.3. Only features that are assigned to someone by the end of today’s will be included in the official scope. Note: Assigning everything to Nacin does not count.

User Feature: Media Uploader (azaozz)

  • Definitely v1: Integrate Plupload into dashboard. (GSoC project)
  • Probably v2: Improve our image manipulation and gallery management.
  • Nice to have: Kill all thickbox usage, move everything inline.

User Feature/UIUI User interface: New User Experience (jane, koop)

♫ Feels Like the First Time ♫

  • 1st time install welcome screen – intro text and checklist of “steps” to get going.
  • 1st time post-update welcome screen a la Mozilla.
  • 1st time exposure popup for new features a la facebook, twitter, etc.

Note: Matt says WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ is working on similar features there. Will connect with them and see if/where there is overlap and work with them when possible to free up some of Koop’s time.

UI: Responsive Adminadmin (and super admin) (saracannon with azaozz, koop)

Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the admin dynamically display nicely on devices of various screen sizes (including wider screens) and human interface mechanisms, such as touch. Plotting and specifics to happen on UI blog and in weekly UI meetings.

  • Performance: CSSCSS Cascading Style Sheets. files merge (especially RTL) / remove duplicate styles.

UI: Improve Admin Bar (koop, jane)

Continue the admin UI work started in 3.2 and work toward combining admin bar (in dashboard) with admin headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. to reduce duplication and save vertical space.

Internal: Performance Improvements (markjaquith, jon)

  • Permalinks
    • #17177, #15915, #16687, others
    • The permalink structure is highly desirable, but it doesn’t scale beyond 50 pages or so.
    • /%postname%/ permalinks without performance penalty
    • /static-slug/%postname%/ permalinks without performance penalty
    • Consider retiring verbose rewrite rules all together in favor of queries.
    • Finally fix the issues relating to special characters in permalinks using an upgrade routine (#16036 and others)
  • Nav Menus
    • #14134, #16799, possibly others
    • Fix the issues around saving menu items.

APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Improvements (ryan, koop, others)

  • register_meta, new caps, *_metadata_by_mid() (nearly done)
  • Nice to have: WP_Meta_Box (proof of concept posted)

API: Settings API Improvements (ryan, petemall, scribu, markjaquith)

  • Convert table markup to CSS
  • Nice to have:
    • Make settings fields/forms/errors construction less painful
    • Use the settings API in the Networknetwork (versus site, blog) Admin
    • Kill options.php as a POST handler

Internal: Language Packs (nacin with SergeyBiryukov)

Merge in GSoC project. Will require quite a bit of development across GlotPress, api.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, and core. (As in, needs additional owners.) In the next week we should come up with a plan of action for how it should all work, as there are currently many questions. (#18200)

Updates/Upgrades (nacin, dion, otto)

  • Internal:Â Partial build updates, version 2 – md5 verifications of files – nacin, dion
  • Feature: Ability to install child themes (in the theme directory) via the theme installer – otto
  • Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.: Core changelogs via the update check, to entice updates

Secondary Items

Deprecate IE7 in the Admin for 3.4

Everyone hates IE7. It’s insecure. Let’s make it go away. Also, dropping IE6 didn’t give us much beyond goodwill, because most of the hacks we needed for IE6, we also need for IE7. So we could actually clean up our CSS a bit if we dropped IE7.

Not happening for 3.3, will target 3.4. Once we hit freeze or RC someone could start working on this to have it ready to go in the minute we open 3.4, to provide the maximum testing time.

API: Editor API improvement (azaozz)

Update/refactor Quicktags (mostly done) and combine all supporting functions.

User Feature: Press This

PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party now, target 3.4 for core.

  • Make Press This better in a nebulous and undefined way.
  • Browser extensions? (mitcho?)Â See also

Mixed Bag

These are things we really want, but no one is assigned to them. This is a great opportunity to earn some core cred by taking a greater role and spearheading development of a feature.

  • UXUX User experience: Dismissible admin notices – sorich87
  • UX: better management of workflow in editor (joe is currently editing this post any changes etc) – markjaquith
  • Design: HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. E-Mails – Leverage Wojtek’s GSoC work – westi
  • Death: remove (finally) compat functions from the widgets API and cleanup converting of old settings (will require copious unit tests first) – azaozz
  • UX: Don’t lose widgets on theme switch (#17979) – AaronCampbell