Support » Requests and Feedback » Version 3.0 Features

Version 3.0 Features

  • Jen


    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 - 76 through 90 (of 185 total)
  • I would love to see a photo-gallery-flickr-look-alike thing built into 3.0. I mean, seriously, if I host all my written content on my own blog why can’t have the same power with photos?

    Yall do a great job. Keep it up. I’m looking forward to the MU/Buddypress merge.


    I think the most important three items for me are items that plugins don’t do or don’t do well:

    1. Merge with WordPress ยต and support for multiple blogs on subdomains/domains (like @donnacha proposed)
    2. Easier linking to internal content so that the links will update if permalinks change and will be disabled if the content is deleted
    3. For new installations, a built-in Welcome Guide that displays a checklist like configuring settings and setting up categories.

    Generally, though, I would agree that it’s better not to make WordPress too bloated. There’s a lot of plugins for some of these features, like an admin bar.

    Alternatively, a lot of these features could be plugins that are bundled with the distribution (canonical plugins?) so that users who don’t want them can turn them off. Kind of like Akismet.

    I know that it has been said that 3.0 is ‘just’ the release number that follows 2.9, but many look at it is a Major release.

    With the MU merge, it is hard to justify that it is just the next release.

    I would like to see 3.0 focus on the MU merge and add (as @donnacha has suggested) the support for multiple domain management. This is no small task, but I think it is important to do it right and not fast.

    I would like to see a new default theme, and I think it will be necessary with the MU merge.

    Beyond that, I would prefer new features to be pushed to the 3.1 and later releases. The MU merge and a new default theme should be enough for 3.0.

    I know that it has been said that 3.0 is ‘just’ the release number that follows 2.9, but many look at it is a Major release.

    Would it be possible to release a 2.A ?

    Really fix the 2.1 problems that have occurred. Make the WP/WPMU integration WORK right and be easy to use. Work on new theme for both front-end and back-end. Update and increase documentation – in the installed files, here and at the codex.

    Then start working on the other major set of adding and changing things around.

    I have new idea. When Akismet marked a comment to spam, just little text Your comment is marked as spam. Contact to webmaster.

    First of all I consider myself to be an advanced user of wordpress. I am not a coder and therefore do rely on developers heavily. Theme hacking is fun though!… usually with a lot of errors along the way.
    I use wordpress as a CMS for clients and groups and non-profits. I have about 20 sites that use wordpress now.

    -So I have two requests-
    1: I would really like to see Widgets made into something more. The multiple instances of widgets is really good.

    With all my wordpress setups I always install
    Advanced Text Widget
    Display widgets

    I need to be able to control where the widgets get displayed, and what is in those widgets. Personally I think if this was in core, then plugin developers could take it further.

    2: More options on how content can get input (and modified) on the site by the end-user.

    I am totally fine inputing text with WP2.9 text editor. My clients are generally not OK with it. My clients mangle msword documents nevermind an online text editor with so many finicky buttons, it is daunting for them. Some of my clients have 5 pages of instructions on how to input text (yes grandpa instructions)… and then I still have to go back and clean it up. Yes I use custom fields and all that stuff.

    My dream is where
    I can build a form which interacts with content in the wp database. (categories are selectable by a dropdown menu etc)
    My clients can input OR modify data via these forms. (change store hours. etc.)
    -These forms could become pieces of code like widgets-

    I know there are a couple of plugins like TDMOF
    This plugin looks perfect, but, I am a wordpress user, not a coder.
    This is an extremely complicated plugin when you look at all the options it provides. I also think all these options are needed because it is not in core.

    I’ll be glad to respond to any questions or issues or hear about how this is not a good way forward for wordpress core. Take care, and I thank the wordpress development team for all the work you have done over the years.

    Complete support for Custom Post Types would make me smile sooooo much that my head would explode thus spreading joy through out the world ๐Ÿ™‚

    custom content type UI and API

    the few things about that done in WP 2.9 have to be finished, because they are not useful as they are now

    custom content type UI and API would allow to use WordPress as a real CMS, and it would open a new world for this great tool

    Thanks for the initiative to postulate concrete features to be in concrete versions.

    I’d like to see WPMU integrated and I think that’s enough for the new version. That will help to reduce the overall codebase (from two to one project) and then let’s see.

    I’d like to see the release cycle more compact than it was with the last versions. With the new updater, we can pretty easily fire out more versions quickier.

    Given that the prime motivation of bloggers is to get their posts noticed, and that the prime mechanism for this is the search engine, then I’m wondering why a Permalink system based on this logic is not the NORM. My thinking suggests that a URL structure of site/index/category/postname would be the most rational approach to using keyword identification of content for fast, accurate reference. In this context, ‘date’ or numerical ID is meaningless.

    My Blogs rank in the top 10 in their SERPs because I use a url/category/postname/ keyword structure. Seems Wikipedia agrees with me: “The basic conclusion from studies of the structure of blogs is that while it takes time for a blog to become popular through blogrolls, permalinks can boost popularity more quickly, and are perhaps more indicative of popularity and authority than blogrolls,…

    Maybe focus more on code optimization. Many use things such as /%postname%/ is widely used but causes huge lags and there are workarounds to make such things more efficient so.. why not work on that instead of the next unneeded feature?

    Only catering to new features all the time will make WordPress quite useless and bloated in the end. Making WordPress an app that caters all needs will make it fail miserably.

    How about better ‘inline’ user-registration for guests.

    By ‘inline’ I mean that users can save login info (register) whilst making their first comment if they so desire. Usually having people register before commenting makes everything more controllable for a solo-admin but directing people to the wp-login.php page to register (which is not in any way linked to the theme of your blog, another new feature, perhaps?) is not very user-friendly and I think discourages many from wanting to write a comment/question.

    Can we please have automatic thumbnails for post excerpts? It’s really quite difficult adding thumbnails to post excerpts at the moment, unless I’m missing something.

    Dear god, please work on a UI for custom fields that’s more friendly to the end-user (like Flutter)! Oh benevolent WP gods… Take a hint from Flutter, as buggy as it is, and integrate something like it into core. Make a simple admin settings page that lets us create custom post types and display them for the end user as write panels. That’s all WP needs to make it a CMS.

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