Support » Requests and Feedback » 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 - 61 through 75 (of 185 total)
  • I would appreciate a feature like RB internal links zu create easyly links to older posts.

    Frank

    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)

    Simplification:

    • 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.

    Integration:

    • 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 2×2 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.

    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
    – …

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

    Would make ipod touch browsing much easier!

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

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

    +1

    • 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?

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

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

    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.

    Pat

    (@healthplaza)

    Wouldn’t it be

      better

    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.

    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.

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

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

    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!

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