Post Closed as "not constructive" by Rarst
    Tweeted twitter.com/#!/StackWordPress/status/154161774155931649
6 Capitalized the title again
| link

What featuresFeatures would you most likeMost Like to see addedSee Added to WordPress?

5 deleted 10 characters in body; edited title
source | link

What Features Would You Most Likefeatures would you most like to See Addedsee added to WordPress?

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from its outcome.

-Mike

What Features Would You Most Like to See Added to WordPress?

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from its outcome.

-Mike

What features would you most like to see added to WordPress?

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from its outcome.

4 typo
source | link

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from of its outcome.

-Mike

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from of its outcome.

-Mike

I'm creating a community wiki to ask the following question:

  • What features would you most like to see added to WordPress?

This Question Implies a Few Things:

  • It should surface the features enthusiasts want most, not just drive bys from people who can't be bothered to know that the "P" needs to be capitalized (inside joke. Of course...)

  • Favor features that benefit the more advanced users and especially the theme and/or plugin developers.

  • Also favor APIs and other enablers vs. just yet another new UI widget. Examples of this might be a Backup API that many developers could build on top of, or a Twitter API that themers could build on.

  • Focus on only the few things you really want most, not everything you can think of. Don't let this be a dumping ground for everything you can think of or have ever thought of. When adding a wanted feature ask yourself if you'd prefer to have it or your top 3 features; if not maybe you shouldn't add it.

  • Give some great details including, if appropriate:

    A. Wireframes (maybe using Balsamiq?),

    B. API Interfaces

    C. Suggested Hooks

    D. URL Structures

    E. And more.

    F. Even Source code

  • Significant Features Only, please. Don't add something like "I want the admin console to be purple" or "I really want the admin menu to be on the right."

  • Avoid things that only Automattic can control like things on WordPress.com!! (not that enthusiasts would care, but...) Better to stick with the things that contributors to an open-source project can affect like code and collaboration.

Rules of This Wiki

  • Do not duplicate suggestions. It's okay if you do but a moderator may down-vote it and/or delete if possible. In the case a significant duplicate exists but with some good additions we should edit the answer that's duplicating it to include the additions.

  • More rules will come as needed, as we realize they are needed.

If you have concerns about this related to WordPress Ideas, Core Team buy-in or relationship with WordPress/Automattic, please see the comments in one of my own "answers" posted to this question, below. My hope is that this effort will be entirely positive and that everyone including Automattic and the WordPress core team will get huge value from its outcome.

-Mike

3 grammar and spelling
source | link
2 Removed the concerns to make the question shorter.
source | link
1 Post Made Community Wiki
source | link