[closed] Version 3.0 Features (186 posts)

  1. gazouteast
    Posted 6 years ago #

    in no particular order of preference ...

    +1 = single core install serving multiple domains/sites for easier maintenance and admin
    +1 = domain mapping
    +1 = improved, faster-to-load-and-run admin theme/backend
    +1 = admin bar (cross-domain AND multi-blog in MU AND classic WP)
    +1 = admin configurable registration features (anti-spam / anti-splog / email verify / IP record / anti-bot)
    +1 = admin customisable registration screen with compulsory extra fields (e.g. state and country - can be used with IP capture/locale as anti-troll/splogger alert system, could then be referred to by Akismet for even more accurate spam identification)
    +1 = email verification at registration info change by user
    +1 = NO plain text password transmission or storage
    +1 = admin control panel setting for post revision count & empty trash period
    +1 = categories for pages

    My own wish - easy per-category themes/child-themes using the new template tags from WP 2.7-2.9 - might have to appear as a plugin first, to gain traction though.


  2. frankbhv
    Posted 6 years ago #

    I would appreciate a feature like RB internal links zu create easyly links to older posts.


  3. designodyssey
    Posted 6 years ago #

    Purpose: Improve CMS capabilities to cement WordPress as most flexible/extendible platform.

    Methodology: Focus on simplification and integration while adding 50-100 "easy fixes" to community annoyances (e.g. admin screens)


    • Ensure setting up WordPress with multiple blogs (i.e. MU) is simple and/or that any complexity is transparent to the intermediate user who will give it a try.
    • simplify the process of creating, using and managing custom content types and frankly explain why they are better to use than "post" if all the data is still in the post tables anyway.


    • Better integrate your existing projects in terms of installation, setup and configuration (WPMU, Buddypress, bbPress) as many users will be adding these "canonical" plugins.
    • Bring CMS flexibility/functionality (e.g. different "types") across projects into core of those projects and so they work together with roles/capabilities. (e.g. forum-types, blog types, group-types, member-types, friend-types, private message types)
    • Create APIs for extending the above.

    Easy Fixes:
    This is to appease the annoyed masses who want this or that.

    1. Compile the list.
    2. Create a 2x2 matrix with ease of fix and pain alleviated as the axes.
    3. Do 20+ of the high pain/easy fix type
    4. Do 1-3 of the high pain/difficult fix type, time permitting only.
    5. Don't do any others for this milestone.
    6. Do some of the low pain/easy fix ones along with tagged releases.
    7. Don't do the low pain/difficult fixes at all.

    This methodology should move WordPress and Automattic along and please those waiting masses that want to drop other platforms and use wordpress more as a CMS which is clearly happening in droves already.

    Another note: It would be wise to divert some resources to making wordpress more accessible so the community could do more of the work.

    • Clean up the codex. Take suggestions and then put someone on this. Also figure out how this will be updated after significant changes.
    • Clean up wordpress.org. Better link to all Automattic projects and probably have a page that gives an overview of all of them with example integrations from the showcase.
    • Clean up the plugins repository. Currently relevance is so much better than "recent" I end up with dead plugins that are relevant. We should be able to filter within results or something to deal with plugins from 2005.
    • Absolutely do the canonical plugin thing. I'd make this primarily for bloggers who want some cool feature that is difficult to maintain through release changes, but everybody (who blogs) wants. Give it an API to be extended. Maybe in this round, keep Buddypress and bbpress the only two unless you want to more with video/audio/images.
    • Do video tutorials. Get someone to do some good videos on coding for WordPress. Take some of the codex best practices and turn them into a video tutorial series. You can even link to community members who do this on their own.

    That's alot, but if most of this happened by Q3 2010, it would be an amazing boost for the whole community.

  4. Paolo Melchiorre
    Posted 6 years ago #

    Add CMS capabilities like Plone CMS UI:
    - default description for pages
    - template for listing sub-pages with title and description
    - thumbnails for articles in default theme
    - function to manage events, appointments in the future in the calendar
    - optimization for multilingual blog (es: zd multilingual)
    - link with hierarchical categories
    - ...

  5. dreamsburnred
    Posted 6 years ago #

    I would absolutely love built in mobile device support like wordpress.com.

    Would make ipod touch browsing much easier!

  6. dreamsburnred
    Posted 6 years ago #

    Oh and when the blog sets up it should ask if you want to make your blog do follow, or the default no follow.

  7. hpguru
    Posted 6 years ago #

    Oh and when the blog sets up it should ask if you want to make your blog do follow, or the default no follow.


  8. IckataNET
    Posted 6 years ago #

    • Let the user define his/her admin folder in the wp-config file. Better security is always a good thing. (Think that this feature won't take so much time to develop)
    • Create role-management Page in the admin (or add the Role Management plugin to the core)
    • Built-in Gallery manager
    • Multilanguage support

    I know that the last three are a lot of work to implement for version 3.0, but it would be nice to have them in future versions.

    Here are some of the ideas that have been discussed for 3.0 before... categories/tags for pages...

    Don't think this is a good idea. A Page is a page, why you want to make it similar to Post?

  9. DaveZ
    Posted 6 years ago #

    Native caching/cached modes and more database call optimization if possible. I'd like to cut my hosting bill in half. Thank you.

  10. hpguru
    Posted 6 years ago #

    IckataNET, i agree you. Page is page and article is article. So why category and tags to pages.

  11. JohnMyr
    Posted 6 years ago #

    Its hard to pick one feature cause there are some features that will take WP to the next level if they are incorporated together:

    Custom content types enhancements together with taxonomy enhancements and custom fields enhancements are by far the most important to put into core in my opinion, as it will make WP more usable for sites thats more than simple blogs.

  12. Pat
    Posted 6 years ago #

    Wouldn't it be

    to actually get the last version working before planning on 3.0?
    Just yesterday I started with wordpress and it really isn't working well at all. Sure I can get a theme but half of it just doesn't work. According to my host it's because there is something wrong with the script. Now if it were only 1 theme I'd say yes I understand and try another one. Well I've tried a zillion and they all won't show properly. What should have been a simple setup of maybe only 15 minutes turned into 15 hours and I'm not even including waiting for a reply from my host.

  13. Catia Kitahara
    Posted 6 years ago #

    From Jane's list I'd like to see in no order of preference:
    canonical plugins and a UI for displaying them,
    new default theme - (with some regard to non blog sites)
    better importers - (including users importer)

    My suggestions they all concern the fact WP is being recognized as not just a blog platform:
    Bulk page creation - when WP is used as a CMS for a non blog site, it's common the need to create pages without content to populate the site. I've experienced situations where I needed to create like 50 pages at once, and believe me, it's very annoying the way it's done now, creating page by page through the "add new page" option. It should be as easy as to add a new category.
    Custom images sizes - there's a patch for creating different images sizes (other than the default ones - thumbnails, medium and large) that didn't make it into 2.9. I hope it will do into 3.0, first, because it's kind of a logical improvement to the images handling 2.9 has introduced. And secondly, because it's also very usefull when using WP to manage a magazine type of site, for example. In such cases, we usually need to deal with horizontal as well as vertical images orientations. These three default sizes are very limited.

  14. hpguru
    Posted 6 years ago #

    HealthPlaza, problem may be in your theme. Please, start a new topic in Theme section with your details.

  15. moshthepitt
    Posted 6 years ago #

    I'd really like to see a photo album feature in the core, or as a 'canonical' plugin.

  16. jvclark
    Posted 6 years ago #

    I say just focus on the merger w/WPMU -- yes I've got a bunch of "pet" features that I'd like 3.0 to have but nothing so critical as the merger. As it was said in the beginning of this thread, I think it makes more sense to keep your eye on the ball and to do the merger well rather than getting sidetracked.

    In general, I think the goal here should be to make WP the best damned CMS out there, and it's already well on its way. Down the road there are going to be a lot of people adding on canonical plugins (bbpress, buddypress, etc..) so aside from the merger I would focus on making integration with these "canonical" plugins as seamless and easy as possible.

    You guys are doing well, and keep up the good work!

  17. paulhastings0
    Posted 6 years ago #

    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.


  18. Frederick D.
    Posted 6 years ago #

    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.

  19. Kevin Cristiano
    Posted 6 years ago #

    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.

  20. lokrin2000
    Posted 6 years ago #

    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.

  21. hpguru
    Posted 6 years ago #

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

  22. C0BALT
    Posted 6 years ago #

    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.

  23. Michael Fields
    Posted 6 years ago #

    Complete support for Custom Post Types would make me smile sooooo much that my head would explode thus spreading joy through out the world :)

  24. Cyrille Tuzi
    Posted 6 years ago #

    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

  25. hakre
    Posted 6 years ago #

    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.

  26. rhys
    Posted 6 years ago #

    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,..."

  27. Tommie Hansen
    Posted 6 years ago #

    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.

  28. pta
    Posted 6 years ago #

    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.

  29. Heather
    Posted 6 years ago #

  30. danwarne
    Posted 6 years ago #

    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.

Topic Closed

This topic has been closed to new replies.

About this Topic