[closed] What Should 2011 Hold for WordPress? (159 posts)

  1. Jen
    Community Organizer
    Posted 5 years ago #

    The core leadership team will be meeting up in person in early January to put together a vision/plan for WordPress in 2011. We're working on an agenda for the meetup, and when that's made, we'll post it. We're also hoping to do a live town hall via streaming video. Use this thread to make suggestions for WordPress in 2011 (software improvements, community initiatives, etc) and/or to post questions you'd like to see answered in a town hall.

    Please try to make helpful suggestions rather than accusatory complaints. Please do not use this thread to post rants, political diatribes, or novel-length expositions on all the things that you think are wrong with WordPress and the world. Try to keep posts to a paragraph and/or a bulleted list so that it doesn't become unwieldy to review everyone's posts. Thanks!

    This thread will be closed on January 4, 2011 to ensure all posts can be reviewed before the meetup/town hall.

  2. Jen
    Community Organizer
    Posted 5 years ago #

    I have an entire huge list of things I want to cover during the meetup, but in the spirit of keeping posts short, I'll just list a few things that we didn't accomplish/finish in 2010 that I'd like us to prioritize for 2011:

    • Make media features better
    • Settings UI improvements
    • UI cleanup
    • Core plugins
    • Standardize how plugins deal with settings and navigation
    • New contributor mentorship program
    • Documentation/handbooks/training materials
    • Make WordPress.org/WordCamp.org better re organizing local groups
  3. mrmist
    Forum Janitor
    Posted 5 years ago #

    Code cleanup where things have been achieved in roundabout ways to support PHP4? There must be cruft that can be purged out of the code base from the next release.

  4. eddihughes
    Posted 5 years ago #

    Improving the Menu system. It's great, but their is a lot of automation that can reduce building out the menus. For example, adding a parent page with children. Their should be an option to have the children to automatically fill out below the item.

    It would be nice to have User Photo and Gravatar integrated. For example, the user could have a Gravatar, but also overwrite it with a User photo that's uploaded locally on their blog. ACTUALLY, maybe a way to allow the user to register/upload their Gravatar through their local Dashboard? Whenever I explain gravatar.com they don't see a purpose. Wouldn't it be nice if they goto: Your Profile -> Gravatar, click Facebook Connect -or- Twitter OSAuth to register; then upload their Gravatar picture in their Dashboard? :D

  5. Mark Jaquith
    WordPress Lead Dev
    Posted 5 years ago #

    • Make one-click updates work for more people. Interactive setup guide instead of just an error message.
    • Drop PHP 4 compat.
    • Simplify taxonomy table structure by merging term and term taxonomy tables.
    • Improve the taxonomy API.
    • Media: faster, simpler, obvious.
    • Unit tests: they're a mess. We need reliable ones, that run in some hosted environment so that every WordPress contributor can test their patches and see the result.
    • Move Akismet and Hello Dolly out of the core package.
  6. Michael Fields
    Posted 5 years ago #

    Better support for Local Meetups on WordPress.org/WordCamp.org is definitely something that I think is worthwhile and would serve the community as a whole. I am interested in hearing more about your ideas here and am willing to volunteer hours if you need me to do something to further this idea.

  7. Alex Blackie
    Posted 5 years ago #

    I agree with dropping PHP 4 and Hello Dolly, though Akismet could stay in core.

    I think speed should be another thing to work on; SQL efficiency. Try to limit the number of database requests per page load. We shouldn't need caching plugins to make our sites fast.

    Maybe an option to turn off code formatting (automatic paragraphs and such)? There are plugins that do this, but I think it should be a core feature.

    Maybe a "lite" version of WordPress; one that just does a blog with basic taxonomies. Basically posts, comments, categories, tags, media, and custom fields (and obviously plugins and themes). Sometimes I just want a lightweight blog engine.

  8. Guga Alves
    Posted 5 years ago #

    • Built-in Pagination
    • Built-in SEO options
    • More user contact fields, like Facebook and Twitter, in profile options
    • Better support for Local Meetups on WordPress.org/WordCamp.org
    • Simplify taxonomy table structure by merging term and term taxonomy tables.
  9. Dominik Schilling
    WordPress Dev
    Posted 5 years ago #

    • UI cleanup

    => Drop IE 6 support
    => Use more CSS3 instead of background images

  10. McGarityDotMe
    Posted 5 years ago #

    Fun! Thanks for asking us for our ideas, Jane & gang.

    • Improve the Import/Export functions
    • Brainstorm new ways to follow comments (ex: integrating Subscribe to Comments into core, push notifications, etc.)
    • Focus on mobile application development (quality issues have taken away from WordPress brand)

    Some I am +1ing from other people's posts:

    • Improve consistency of one-click updates (Mark Jaquith)
    • Built-in SEO options (gugaalves)

    More as I think of it.

  11. alhitary
    Posted 5 years ago #

    Make gallery better and fix problems that mentioned already and not fixed till now.

  12. Jeroen G
    Posted 5 years ago #

    • Better Media handling
    • Gallery
    • Documentation etc.
    • Standard pagination
    • BBpress integration, as a plugin or like the Network/MultiSites.
  13. Austin Matzko
    Posted 5 years ago #

    • Make PHP 5.2 the minimum required version.
    • Decorate all kinds of objects--posts, terms, etc.--with similar methods and properties, so they can all be Looped over.
    • Make the admin more easily themable.
    • Reduce the admin's dependency on third-party JS, when it's used globally throughout the admin (as opposed to discrete components like TinyMCE)
    • Establish a consistent API for front-end and admin Ajax interactions.
    • Build a better API for plugins to extend the nav menus.
    • Make the uploader more versatile and flexible.
    • Offer an API for sending messages to users (error messages, upgrade nags, etc., more robust than the transient hack).
    • User capability handling that doesn't rely on serialized data.
  14. Lance Willett
    Posted 5 years ago #

    • Better handling of widgets when switching themes
    • Media improvements
    • Support for child themes in the W.org directory
    • Front-page posting support for any theme
  15. Rutger Groot
    Posted 5 years ago #

    • Page speed optimization
    • Better caching, minifying and options for CDN build in
    • Mobile support build in
    • Better search
    • Newsletter system build it

    Many thanks, keep up the good work!

  16. Milan Dinić
    Posted 5 years ago #

    Better support for international users:

    • Centralized system for localization of plugins and themes
    • Support for changes of hard coded English URL slugs (page, author, feed, etc)
    • Support for non ASCII characters in usernames
    • Localized versions of akismet.com (if it stays in core)
  17. Daniel Mount
    Posted 5 years ago #

    As a follow-up to the general "improve photo gallery" suggestions, one specific thing I'd love to see would be a way to use the gallery shortcode to construct a gallery page, which has a thumbnail/link for each post/page with associated galleries displayed with the gallery shortcode. It would probably help to have a built-in function call "except for [post id], [post id]."

    Other than the gallery improvement, a big +1 to several ideas already mentioned:

      More intuitive menu system
      Integrated user photo/gravatar - either local override or nice Gravatar integration
      SQL efficiency/page speed optimization
      Integrating Subscribe to Comments into core
      Built in mobile support
  18. csladdin
    Posted 5 years ago #

    • Allowing posts and pages to be updated at a specific time would be a fantastic feature. At the moment of course, one has to login to the system at the time you want it to go live to update which is a bit of a pain.
    • Easier setup for WordPress Networks. Could we try to eliminate the need to add code, etc?

    These are a couple of ideas I'd like to see to make WordPress easier to use.

  19. jamesakadamingo
    Posted 5 years ago #

    As a end user (although one who is also a programmer) I would be upset to see akismet leave the core, but do agree that Hello Dolly should be removed.

    Dropping IE6 Support seams like a sensible move, the more streamlined the end product can be the better and IE6 support prevents the use of CSS3.

    I would love to see some meetups in the southern UK, just to meet some more WP devs.

  20. Frank Bueltge
    Posted 5 years ago #

    • Exclude functions (example: revisons) to Core plugins
    • Standardize how plugins deal with settings and navigation
    • Drop PHP4 Support
    • Better localization support, to many memory and use php-standard functions for localization (this reduce the memory with PHP5)
    • Page speed optimizaton (filter rewrite rules)
    • n to n relationship for attachments
    • Make the admin more easily themable
    • Move Akismet and Hello Dolly out of the core package
    • Kill all inline-css-styles
  21. Eric Mann
    Posted 5 years ago #

    • Grandchild Themes - A lot of theme frameworks offer child themes already. Adding personal customizations to these can be problematic if they're ever updated by the original author, returning us to the same problem we had when hacking standard themes. Adding advanced (iterative) theme inheritance would allow for child-child themes (parent theme is the framework, child theme defines the general styling/behavior, grandchild theme adds unique customizations).
    • Plug-in Framework Support - As it stands, loading a plug-in framework requires include()ing an external class file and hoping that no other developer is using a different version of the framework. But installing a framework as a separate plug-in is a hassle for end users. I'd like to see a separate system within WordPress for loading, activating, and managing common frameworks that plug-ins can hook into. This would make 3rd party code more collaborative without lots of class my_Framework and class my_other_Framework and class my_Framework_2 floating around when upgrading one instance can/should upgrade them all.
  22. Jonathan Dingman
    Posted 5 years ago #

    I'd really love to see an overhaul for WordPress.org as a whole.

    Specifically within WordPress.org, I'd like to see:

    • Better moderation and possibly even quality testing around plugins and/or themes

    The reason for this is that it's a great resource to begin with, but it could be so much better if there were some more guidelines around it.

    Specifically involving commercial plugins, SEO link spammming, and ensuring that each plugin won't harm a user's installation.

    Keep up the great work everyone!
    Goooo team WordPress! #rock #2011

  23. Digital Raindrops
    Posted 5 years ago #

    I would add a 1 to adding a child theme directory, rather than adding to the existing directory, there are a number of frameworks supporting child themes, so a catogorized directory.

    Working with twenty ten and promoting child themes there are some things that cannot be switched off, custom backgrounds and headers need a remove call.

    The post meta it would be good if different parts could be easy switched off, like tags.

    Last on the theme, instead of hard coding the headers a function that looks in the folder and adds the headers to the selection, this will save people from messing with the code.

    Not sure if this is what you mean, but these are just observations working with the themes, and not complaints.



  24. asgeirhoem
    Posted 5 years ago #

    Allow easier customisation the WYSIWYG-editor.

    One solution is to define a stylesheet from which all classes are pulled into the paragraph styles dropdown? (Some plugins do this already.)

    It would also be great if the editor reflects the styles, or clearly indicates which class is assigned to any particular paragraph.

  25. Jon Cave
    WordPress Dev
    Posted 5 years ago #

    • Core plugins
    • Unit-tests cleanups and improvements
    • More progressive enhancement with CSS3/JS/HTML5 where possible
    • Media
    • Documentation (API reference) + handbooks
  26. asgeirhoem
    Posted 5 years ago #

    The admin page list view also needs a cleanup, so that parent/child relationships are more clear, and page hierarchies are easier to manage.

    The alternating row colours create more confusion than clarity, when they work independently of the hierarchy.

  27. theWebalyst
    Posted 5 years ago #

    The usability for content editing on WordPress is very poor. Not surprising for a blogging platform, but my interest is in websites where blogging is an option, so CMS is primary and I'm coming from that direction.

    WordPress needs an in depth review of usability for content management. But to be honest, even very basic things are in my opinion dismal. I don't have time to put together a list right now, but getting to pages for editing, and the editing UI itself is terrible.

    There isn't undo. The allocation of screen real estate makes editing a page feel like I'm using an iPhone. Scrolling doesn't work (page up/down frequently scrolls the page instead of the edit window). Accessing pages on even a small site is horrendously longwinded (again exacerbated by poor use of screen real estate - i.e. not showing many pages in the page list). These are just a few things that spring to mind, and are very basic.

    I am committed to WordPress. Its a great platform and I will work with you guys when I have time to compile a more constructive review and suggestions for usability improvements, but right now don't have the time.

    The purpose of this post is to highlight this weakest of all aspects of WordPress. It is where other systems will gain an advantage if it is not addressed rapidly enough so I hope I'm not alone in identifying the issue, and that there are folks who understand usability a lot better than seems to have been the case so far. Its normal.

    Usability is generally very poorly understood and implemented. So this does also present an opportunity for WordPress. This system has many killer features in other areas. Get it to the leading edge on usability and it will be untouchable!

    With WordPress love,

    Mark (in London)

  28. ZATZAi
    Posted 5 years ago #

    For years I have wanted a way to have a post template drop down menu. So when you start a new post you can click on a drop down menu to have the post filled with text, images, etc from a template you set up in advance. This would be a god send for those of us who make regular posts based on a format every week. An option to save a post as a template, and the ability to either delete and/or edit post templates would also be needed.

  29. Jen
    Community Organizer
    Posted 5 years ago #

    @theWebalyst: I would suggest you join the UI group at make.wordpress.org/ui to provide specific UI feedback. A couple of notes, though:
    - In the visual editor, there is an undo button.
    - You can re-allocate the screen real estate using drag and drop and/or the screen options tab.
    - You can change how many pages are listed by changing the number in the screen options tab.

  30. Jen
    Community Organizer
    Posted 5 years ago #

    Related to Lance's comment about widgets, I would be over the moon if we made it so widgets were easier for people to use for stored content, like from a specific category/post type that stays out of the regular post loop.


Topic Closed

This topic has been closed to new replies.

About this Topic