What Should 2011 Hold for WordPress?
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.
- Including a light related posts function with thumbs that doesn’t crash cpu
- Make possible to disable revisions and other wp-config related things.
Move Akismet and Hello Dolly out of the core package.
Better gallery search in article/page edit (maybe ajax search here?).
Please add one click support to add multiple pictures to article/page.
Please improve updating system! My server auto update crashes to white page. Just update changed files, add new files and delete deleted files in updating process?
Dashboard: On Links page, add pagination and other features for example All (45) Deleted (2).
Thanks. I love WordPress!
I’d like to see some common work / standards around the frameworks now common in theme design.
I’d also like a system for the plugins that warns when plugins may interfere with each other, or are trying to use the same parts of the system
I would love to see:
- Media improvements:
- I know you can easily add a Categories option (as a text field), but maybe a way to add categories/tags meta boxes when editing media that are not associated with post categories/tags. So you can easily display them in a theme.
- Only upload one size for images (whatever size the file is), unless specified sizes are made in the Media settings.
- Search: relevant search & highlighted terms would be awesome! Especially if the search could be turned on to search site-wide for multi-site installs.
- User management: export data to csv, create different types of user roles from within the admin (not by plugin), ability to upload to gravatar within profile.
- Codex: the Codex is a great resource, but sometimes it lacks examples or exactly how certain functions really work. It would be nice if there were concrete examples for each function in WP. There is so much to learn!
Thanks to all who make WordPress so awesome!
Thanks for asking our wishes!
I would like
- Improved support for international blogs (avoid using qtranslate plugin)
- less memory usage (WP is very very expensive)
- improved media library (advanced finding of orphans on disk or DB etc)
- EASY custom field attach for post (images, files, numeric fields etc)
in few words: giving a more ‘CMS-like’ structure
I can only think about one think as a top priority, that is improving the search mechanism. WordPress search feature is quite basic and it is quite frequent not finding things that are clearly tagged.
My top wishes for WP 2011:
1. More integrated SEO options. Nothing major, but expanded control on title tags from the add post (for the people who don’t know the code).
2. WP-Multisite – more tools for customization without knowing the code.
3. More use of HTML5/CSS3
Please make wysiwyg editing actually work, instead of mangling everything.
This may not be WP’s fault, but perhaps you could find a better plugin?
– Image resizing must use ImageMagick if available. Thumbnail quaility it very poor
– Post type admin as seen in More Types plugin should be standard WP feature and permalinks for customn post types needs more flexibility
– Search includes selectable custom fields
– Mobile theme switcher built in
The (long awaited) removal of the Gallery CSS from the page body into the page header where it belongs. Although there are theme-based workarounds, they’re clunky (removal all of the CSS). Some gallery-specific CSS in the page head would be very welcome.
+1 on Media Manager improvements and simplification of Taxonomy table structures. I can’t exactly put my finger on what’s wrong with the Medial Manager, but it could definitely stand to be easier and prettier.
Meta-data for everything (taxonomies, media). I’d love to be able to tag my media with keywords, then be able to search on that (in the media manager, as well as front-end searches).
Taxonomies for users.
Generalize URL routing more, and give more control over URLs for things like authors, categories/tags, etc. Yes, resolving conflicts will require some thought and planning. But as long as rules are consistent, it should be fine. Current URL setup should be redone as a set of filterable regexp rules which can be overridden by themes/plugins.
Over time, at least for me, the Links Manager has become less and less important. Turn it into a Core Plugin, convert it to use custom post types, and ditch the old tables.
As mentioned recently on wp-hackers, an intuitive, documented method to bypass the default get_posts that happens in the normal wp initialization.
Clean up default user profile info (hard-coded services like AIM, Yahoo, Jabber/GTalk). These should probably be configurable in the backend somewhere, allowing the admin to create relevant entries? This might be Core Plugin territory.
Also, I’d like some helper functions that make it easier to add buttons to the editors (TinyMCE and Quicktags) for simple things like a ‘code’ HTML tag.
Lastly, I’d like to suggest a push in the Core Plugins area for “API-only” plugins, such as is often seen in the Drupal community. This is pretty developer-centric, but part of the notion behind Core Plugins is supposed to be to keep developers from having to reinvent the wheel over and over. Core Plugins which provide a common basis for other plugins to build upon, without providing much/anything in the way of front-end features make sense. Use-cases include things such as: OAuth; service specific APIs for Twitter, Facebook, Flickr, etc.; advanced hooks for media management…
Too lofty for a 3.2 goal, but eventually, I’d like to see more of the SQL stuff abstracted out to the point that it could be easier to use alternative database engines for some/all of WP core. Yes, it’s possible right now to create your own db.php, but that’s a bit of a sledgehammer, and there’s still some MySQL-specific features/syntax elsewhere in core. Eventually, what if a developer could choose to store user data in MongoDB? Or store posts in Redis?
- Keep doing the awesome that you all are doing! Since I started with WP around 2.1 or 2.2, the platform has grown in incredible ways that I’ve very much been in support of.
- Custom Post Types with taxonomies and custom fields. Having a UI approach to import, export or modify the fields associated with a CPT would be great.
- Data types and error messaging for custom fields / taxonomy display (date, checkbox, radio buttons, etc)
- Bilingualization of content either as a core plugin or an option-enabled core feature. As taloweb mentions above, qTranslate is one of the better ones – probably offers the least invasive approach re: impact to other plugins. It is currently re-writing for full 3.0 support of CPTs, so timing might be excellent to consider for part of core.
- Nice to Have: An ability to – during install or via options – make WP an entirely “private” site. Offering it as a feature “out-of-box” would add one more solid item on the checklist of WP-as-CMS head-to-head comparisons.
Seems a lot of sites use one of the many mobile plug-ins around to
support mobile access (wordpress.org included). However, as long as
mobile plug-ins are many and not in the core, there will be little or no
further development on top of mobile as it would be totally impossible
to test/integrate with all current mobile plug-ins.
To really kick off WP in the direction of mobile, the mobile plug-in functionality (+some more) would need to be integrated into the core. In this way all players in the ecosystem can start enhancing mobile functionality.
Benefits with having a single, core mobile extension:
– Themes could start having mobile versions as standard along with the
desktop theme, this would make mobile look and feel so much better
integrated with the desktop view.
– Plug-ins could start testing for mobile functionality. Now a lot of
plug-ins provide great value but would benefit from a mobile version to
better support small screens. Having a single mobile solution would
– Plug-in management. If the mobile solution came with some sort of nice
management if, it would be possible to have different sets of plug-ins
activated on mobile and desktop. (Ditto for menus).
There are a lot of good mobile plug-ins, but as far as I can tell, not a
single great one. Most current plug-ins have 1 or 2 unique features,
which taken together would make a great mobile solution!
Taking the mobile step would certainly help position WordPress as a
unique solution for sites that want to provide best-in-class support to
both mobile and desktop users!
I will +1 a few things that have been mentioned previously.
- Make the admin more easily themable, +2, actually
- Built-in SEO: custom titles and meta descriptions
- Easier user of CPT and custom fields, something along the line of Magic Fields
- Default site map
- Better search
I vote to keep Hello Dolly (because it serves as an simple introduction to plugin writing) and Akismet (because I hate spam).
- The topic ‘What Should 2011 Hold for WordPress?’ is closed to new replies.