WordPress.org

Support

Support » Requests and Feedback » Version 3.0 Features

Version 3.0 Features

  • Jen

    @jenmylo

    Community Organizer

    Per the post at http://wordpress.org/development/2009/12/setting-scope/ we will be attempting to set a defined scope for version 3.0, and stick to it. Use this thread to discuss features for inclusion, and which features you think are most important to have in core vs. a plugin. Bear in mind that version 3.0 is when MU functionality will come into core, so WordPress will support running multiple blogs/sites from one installation, and that merge is in itself a big project. If you could only pick *one* other feature, what would it be?

    Here are some of the ideas that have been discussed for 3.0 before… the list is clearly too long, but it will give you an idea of what’s been proposed or pushed before:

    Easy blog menu management, dynamic image resize/crop, media upload UI redesign (begun in 2.9 but postponed for implementation due to technical issues), photo albums, custom content type UI and API, supercharging queries (cross-taxonomies), categories/tags for pages, auto-taxonomy UI, custom fields UI (possibly to be registered by themes or plugins for something to be displayed), settings UI redesign, improve the upgrade process (inc. distros for specific use types), SVN awareness, canonical plugins and a UI for displaying them, plugin page redesign, themes UI redesign, comments UI touchup, decouple language updates and files, new default theme, choose your own start page, caps lock detection, accessibility admin theme, mobile admin theme, synching custom fields > taxonomies, exif refresh, role management simplification, credits page in app, default custom types (microblog, galleries, asides), admin bar, front end comment moderation, front end posting (a la P2), better importers, widget installer, importer installer, more inline documentation, built-in “Welcome to WordPress” guide for 1st time admin use/checklist (set settings, add profiles, set up comment options, dashboard modules, add widgets, pick a theme, etc) with ability to dismiss as you move through, better help tab, more template tags, better zone selector, new code editor, XSL for RSS feeds (pretty feeds), bulk user creation (lazy load importer?), below post widgets, image importing, HTML validation, customizable comment form, Twitter and Flickr importers, WordPress capitalization catcher, configurable QuickPress configurable (add categories), more dashboard modules, easy linking to internal content when writing new content in editor, audit of error messages and updating them to be clearer revisions for custom fields and taxonomies… the list is endless, really, because there are so many cool things we could do. But which ones *should* we do? And specifically, which should we do in 3.0? Discuss!

Viewing 15 replies - 91 through 105 (of 185 total)
  • Wow that’s definitely way too much for a single release. I would like to see a focus on the WordPress/WPMU merge since that will bring tons of features to users of the single user, and multi user wordpress platforms.
    Also I think a focus on mobile (so the mobile admin page) and ease of use (so the admin bar, the welcome to wordpress guide, and the image editing) is important.
    I would like to see the install process for WordPress MU made much easier, since that’s not really something a ‘normal person can do – but I hope that will come with the merge…

    Picking your user name and password during the install process, #10396 would be a nice feature to add.

    How To Do Project Development:
    I think each version of WordPress could include more improvements if development was more organized. I would like it if the core team asked for feature requests and for feature developers before planning, then created all necessary tickets, assigned developers accordingly, and blessed the tickets. Then at feature freeze, any blessed tickets that have not made it to core due to lack of development get unblessed and all waiting tickets that are blessed get taken care of by committers within a day or two.

    I think more developers would pitch in with smaller tasks if things were more organized and more concrete. It seams that key features, major bugs, and insignificant details dominate over medium and small features and improvements, leading the later to get pushed back for years. By letting everyone know where every ticket sits in a particular release features, improvements, and bugs can be put in parallel (separate tracks) and “line cutting” will stop being an issue. Which, getting back to the first sentence of this paragraph, will attract more developers.

    The amount each developer contributes looks like the “long tail” if it were graphed. The core developers are given too much work and the outer circle of developers have to take their own initiative if they want to contribute anything. Hopefully the next release will have improved development.

    It’d be nice if someone with authority went through tickets and requested features and selected some for development, then asked developers outside the inner ring to develop them. This would be a lot more inviting than a free-for-all in trac, because it’s hard to know where to start.

    p.s. Thanks Jane for getting the development organized for 3.0.

    > free-for-all in trac

    Second only to patch punting, I would say the Trac workflow is definitely the next biggest ongoing problem with WordPress.

    like many others here, I always customize wordpress because I use it as my base CMS. So I’m interested in everything to do with custom post types. Things which I think would be useful are:
    – media upload UI redesign and photo albums
    – custom content type UI and API
    – canonical plugins! and a UI for displaying them
    – better help tab and better online documentation
    – more template tags
    – easy linking to internal content when writing new content
    – separate cms distro with canonical CMS plugins installed by default
    – better excerpt and thumbnail features
    – custom default image sizes (for page headers and magazine style layouts)

    I also think these features would make the WP experience better:
    – built-in “Welcome to WordPress” guide for 1st time admin use
    – front end comment moderation
    – new default theme
    – widget installer
    – below post widgets
    – better home template (easily allow page and posts together)
    – default custom types (microblog, galleries, asides)

    I’ll add a vote to getting the bug list squashed into oblivion.

    Add or change as many features as you want; if WP becomes slower and/or demands more cpu time and ram for it to run properly, then all the “glitter” amounts to a hill of beans.

    v3.0 Suggestions:
    *****************
    – Error log reporting service, also known as a “bug feedback service.” When you guys release an update or new code, it looks for errors caused by the introduction of the update or new code and reports results back to you.
    – Submission of the mySQL slow queries log & Submission of the mySQL slow queries log parsed with mysqlsla. — So you guys know which queries are slow and need optimization.

    Only a certain percentage of people report errors to you; imagine all the information you’d have if “wordpress log reports” were sent to some information parsing site on a daily basis? You’d have semi-instant feedback on your changes to the code without user intervention.

    This would help everyone, I believe.

    As someone who works with dozens of WordPress blogs & websites for my clients, I’d say the #1 feature from your list that would make *their* lives much easier is better menu management. Teaching non-technical users how to use sort order is a bit challenging, but moreover it’s a feature that they use all the time and that’s wildly inefficient at the moment. A drag-and-drop interface on the page management screen would be fabulous.

    Other menu-related features that I often hear requests for from my clients include:

    • Being able to link to a single page from two different sections of the site;
    • Having the option to specify a navigation title that’s different from the page title (e.g. for creating shorter menu links); and
    • Hiding pages from the navigation from the back-end (i.e. without messing with template files — we currently use a plugin for this).

    Beyond menu management, image editing/cropping would make a lot of my clients really happy, as would easy linking to internal content. As a developer, I see a lot of proposed features in your list that make *me* really excited, but I know if I sent the list to my clients, they’d prioritize these basic functionality pieces.

    Hope this is helpful. Thanks for opening this up for discussion!

    The two main features I’d like to see is:

    1) Canonical Plugins
    2) A much more robust Custom Fields system

    Canonical Plugins for me makes it to number one since I imagine it will allow for a lot more functionality that we can rely upon from upgrade to upgrade. It is extremely frustrating to have a new upgrade with old plugins that aren’t yet upgraded. Particularly when we are building sites for clients.

    In terms of Custom Fields – what I want is the ability to assign different field types for different types of content so that my clients can easily add the appropriate content without having to worry about messing up the code.

    Along with this I would like to see as easy a possible a system for including those custom fields into our html/css/javascript code. Perhaps some sort of shortcode integration with html which is built into the backend.

    Keep up the good work.

    All the best,

    Moshe

    I would like to add that number three for me is improving the media center section – which means better and easier organization of media (let’s say categories and tags) – as well as the ability to have galleries inside of albums.

    With that said, the two choices I mentioned in the previous post take priority for me – but I really would like to see all three :).

    Be well,

    Moshe

    This is probably beyond obvious, but the developers should definitely take a look at the Most Popular Ideas and in particular to the Trust me when I edit HTML idea. A lot of people are asking for a better HTML editor!

    Personally I would like WordPress to move more in the direction of a general CMS. The creation of custom pages with or without dynamic content should become easier and better manageable with WordPress.

    in addition to my first comment
    (http://wordpress.org/support/topic/345127/page/2?replies=97#post-1327952)

    * no more PHP4 support
    * folder mu-plugins ?
    * which repository for WP 3.0 ? mu ? wp ?

    The current image uploading process is painful. I’d like to see something like the Faster Image Insert plugin built into the core.

    Also, the ability to use Slimbox or Lightbox without having to resort to a plugin. (or manually adding the code!)

    I am super excited about merging MU!

    Better support for failed photo uploads would be nice. For example if I’m uploading 50+ photos to a post (to great a photo album) and a few photos aren’t uploaded properly I need to upload those few photos again, but then they appear at the end of the album – out of order.

    It would be cool if I could retry uploading a particular photo (attachment). Or maybe there is another solution to solve this problem.

    I really love the speed at which useful relatively bug free features are added to WP. For 3.0 my preference would be a focus on the WPMU merge. I look forward to the possibilities it might bring and would encourage you to look at the additional domains issue others have mentioned.

    But if the dev team are looking for core blog features my vote is for, easier internal linking to posts and pages from the post editor (and page editor too I guess). As this would greatly encourage internal linking (which is good practice for user interaction and SEO). I would suggest also adding an option to ignore *internal* pingbacks.

    This is one feature I think would make blogging easier and quicker. I think WP dev should not forget this even if we move to more CMS type functionalty.

    I think it’s pretty sad that realtime comments is still a theme/pluging realm thing. It seems like it should be well supported and documented in to core along with useful theming tools. People expect it- even facebook does it.
    All comment posting should be AJAX. The core should support both polling intervals and long http (“comet” style) on any page with comments.
    The core should also support multiple comment forms on the same page without ID conflicts.
    Generally wordpress should be writing fewer ids and classes into the page
    Cheers for a great release!

Viewing 15 replies - 91 through 105 (of 185 total)
  • The topic ‘Version 3.0 Features’ is closed to new replies.