• Per the post at https://www.ads-software.com/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 - 166 through 180 (of 185 total)
  • +1 for custom post types with the ability to theme the admin gui for it so that my customers don’t have to see the admin area as it is

    +1 for built in domain mapping

    +1 for more granular control of user rolls —love Justins plugin

    It’s very hard to read 167 posts at work. So, I’m sorry if this has been already suggested. What about:

    1. a tool to move comments (among posts and threads) – there are a few plugins to move comments among posts, but AFAIK, none can move comments among threads;
    2. include Viper007Bond’s plugin hability to regenerate thumbnails, into core;
    3. an alternative naming convention to resized images – small, half and big, for example. To use dimensions may break links upon a thumbnail regeneration.

    Thanks!

    One feature that WPMU has been lacking for a while is the ability to track site-wide activity in addition to the activity on one of the independent silo blogs.

    As a publisher working with WPMU now, I’ve found the ability to have lots of blogs running simultaneously great, but I often wish there was a way to use all that information more easily for a site-wide portal page (similar to how Lyceum, another WP derivative, allowed).

    Among the things that this would allow for is tracking site-wide most popular posts and recent comments (instead of just over a single blog).

    Just a thought.

    @sguzik there are plugins for that ??

    With the integration of MU into the core, I would like to see a simple import tool to allow people with multiple WP installs across multiple domains to consolidate everything into one installation. I am currently running three domains with WP installed, and will be installing it on *at least* four more before the end of the year, so I would love the ability to seamlessly move from separate installs to one.

    @chimericdream – I would like this too, but I think that it could be achieved through a plugin. In fact, we will probably write a plugin to do that for a new wordpress hosting service we are working on.

    Since this release is going to integrate WPMU which is more community focused, I think the other major feature should be built in Twitter, OAuth and Twitter connect login support.

    For WPMU installs upgrading to WP 3.0:

    = Requesting for List of Changes in WPMU functions and the lot when WP 3.0 comes out so it would be easier to check/revise plugins and theme customizations before upgrading.

    To start off:
    Deprecated: is_site_admin
    Replaced with: is_super_admin
    Deprecated: ‘multiblog’
    Replaced with: ‘multisite’

    Thanks.

    Blocks/regions like Drupal does. Widget sidebars are a little bit in that direction, but need to take it the next step where you can create and define all your block in the admin, and optionally define their content. Then in the theme design (via css, html) it’s simply a matter of saying where each block goes and (if not defined in the backend), what each’s content is.

    Not only image gallery but also podcast and video gallery. Every author should only see his galleries.
    Support for custom fields within registration.
    Support for international blogs. Mainblog https://www.foo.com and several blogs llike https://www.foo.uk, https://www.foo.fr etc. If you register at https://www.foo.uk you allways get the dashboard of https://www.foo.uk but you can write on all other blogs. This makes sense if you use custom fields for registration. Also it’s better for SEO.
    Standard TinyMCE for comments (without upload and html buttons).
    Integration of BuddyPress as a standard option.
    Possibility to upload local avatar at user profile. If missing then display gravatar for comments.
    More CMS functionality. Better rightsmanagement/rolemanagement.
    Fix problems with sites having more than 1000 pages.
    Service to help developers to test plugins for correct behavior (performance, bad code etc.).
    AJAX included. When showing pages/post only comments should be loaded while stepping through.
    Subcribe to comments and newsletter with double-opt-in possibility.
    Better SEO/SEM support.
    Better support for big sites – using multiple machines for big blogs.
    Very important: including a shortener service.

    I’d like to see sections (channels) where you can have say a blog section and a portfolio section and then add pages, categories, and posts to them. That way you could have more control over your content and have categories and pages relative. Example: domain.com/blog/archive or domain.com/blog/category/wordpress

    I’d also like to see a better Permalink system where you can create series of rules instead of just one rule for all areas. So if you wanted your blog to have dates like /blog/2009/01/01/post-name/ but wanted your portfolio to have just category and name like /portfolio/web-design/wordpress-org/

    Would love to hear some thoughts on these?

    I admit I haven’t read all 177 posts here above (let’s say I read about 20). But I don’t think anybody mentioned the lack of granular user management. If you really want to use WP as a large-scale CMS, used by multiple editors, publishers, reviewers etc, you need Workflow. Right now this can be implemented via a bunch of plugins, but it should be included in the Core, IMHO. I mean, something like “user X can only edit posts in category Y, or user Z cannot read posts in category W”. This could be easily implemented using a Unix-like approach, where each single object (post, category, comment, etc) is associated with owner, group and rest of the world. And then have permission for each of them. For example, post X would be rwr-r- (you don’t need ‘executability’, as far as I can see), meaning that the owner can read and write it, while his/her group can only read it, and same thing for the rest of the world. I know this could be a HUGE revolution in the source code, but I really think it’s totally worth it. And if you need help, count me in ??

    “Media” library enhancement like it is done with “Posts”
    1. Uploading
    a. Create/Select Category (like the “Categories” metabox from “Posts/Add New”);
    *Category Name = Folder Name (in wp-content/uploads);
    b. Ability to add thumbs to Media Categories;
    c. Create/Choose Tag (like a “Post Tags” metabox from “Posts/Add New”);

    2. Editing Media Categories (like in “Post/Categories”);
    a. Ability to add thumbs to Media Categories;

    3. Filters (Media/Library)
    a. Filtering by Categories;
    b. Filtering by Tags;

    Custom Taxonomies: a massively powerful feature which enhances WP’s CMS capabilities – but they’re only accessible if you can write some WP code or if you use a plugin such as Yoast. How about making the custom taxonomies as accessible as tags, so their use can be standardised eg

    • they can be accessed by other plugins (such as all-in-one-SEO, which could then include the taxonomy terms in the SEO meta data)
    • theme developers can set up taxonomy archives in the same way as tag archives
    • taxonomy terms can be updated via the “quick edit” view

    Custom Taxonomies for posts and pages.

    If not, pages should also be tagged and categorized.

    Menu manager – maybe of the kind we find in the administrative panel of the Display theme (see it here).

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