Tag Archives: wishlist

Josepha 3:49 pm on July 18, 2023
Tags: , wishlist   

WordPress 6.4: What’s on your wishlist?

With WP6.3 scheduled for release on August 8th, let’s start planning for WP6.4! We always aim to fix bugs, add new tools, and make WordPress better than ever for users. Polish and refinement of Phase 2 items are high on our list as are any items in the Phase 3: Collaboration roadmap: Real-Time Collaboration, Workflows, Revisions, Media Library, Block Library, and Admin Design.

What other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in WP6.4?
  • What are the current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets of yours do you think will be ready to ship in WP6.4 and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline August 15, 2023

After the deadline passes, the release squad will discuss wishlist items and the release leadRelease Lead The community member ultimately responsible for the Release. will make final decisions based on what is aligned with the roadmap and has an owner, feasible in the time we have*, and high impact for the most users.

* This release is shorter than normal, so that’s part of the decision making criteria.

#6-4, #wishlist

Francesca Marano 7:37 pm on November 23, 2020
Tags: , wishlist   

WordPress 5.7: What’s on your wishlist?

With the 5.6 release scheduled for December 8th, let’s start planning for 5.7!

We always aim to fix bugs, add new tools, and make WordPress better than ever for users. Components of Full Site Editing are still at the top of the WordPress goals list; what other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in 5.7?
  • What are the current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets do you think will be ready to ship by late January and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline December 15, 2020

#5-7, #wishlist

Chloe Bringmann 4:05 pm on July 31, 2020
Tags: , wishlist   

WordPress 5.6: What’s on your wishlist?

With the 5.5 release scheduled for August 11th, let’s start planning for 5.6! We always aim to fix bugs, add new tools, and make WordPress better than ever for users. Components of Full Site Editing are still at the top of the WordPress goals list; what other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in 5.6?
  • What are the current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets of yours do you think will be ready to ship in 5.6 and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline August 20, 2020

#5.6

#5-6, #wishlist

Helen Hou-Sandi 7:44 pm on August 17, 2016
Tags: , wishlist   

WordPress 4.7: What’s on your mind?

Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. has been open for 4.7 commits for a couple weeks now, with 4.7 formally kicking off next week – more on that to come shortly. To help get an understanding of what people want to see in 4.7 (and beyond), chime in below with pet tickets, projects, and other wishlist items‡. If you’re able to work on your suggestion, please also indicate that. As both the release leadRelease Lead The community member ultimately responsible for the Release. and a lead developer, I have plenty of thoughts of my own, but right now I want to hear yours.

‡ Disclaimer: Comments do not constitute binding contracts. 🙂

#4-7, #wishlist

Joe Dolson 9:02 pm on April 27, 2016
Tags: , , wishlist   

Accessibility Wish List for 4.6 and beyond

(Cross-posted from Make/Accessibility)

Following the example from development on the WordPress Editor, the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team is going to start posting our goals in wish list format. If you have an accessibility goal you’d like to see the team pursue on WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., add it in a comment and let us know!

Current Accessibility Goals

  • Color Contrast: coordinate with the Design team to finish the colors. See #31713, #35659, #35596, #35622. (@afercia)
  • Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: collaborate with the team working on the Fields API to make sure they’re fabulously accessible. See #18801 for history, Fields API development (@joedolson, @afercia)
  • Uniform Search: Work to address the numerous different search interfaces within the WordPress adminadmin (and super admin) so they offer the same experience through the admin. See #31818. (@cheffheid)
  • Develop libraries for Accessible Tabs & Accessible Modals
  • Accessible Video: improve the user interface and metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data relationships for captions & subtitles to make accessible video easier to manage. See #31177. (@rianrietveld)
  • Accessible Media Grid
  • Review usage of target=”_blank” in the admin. See #23432. (@trishasalas)
  • Finish headings improvements: remove controls from headings. See #26601. (@trishasalas)
  • start accessibility work on Select2. See issue 3744 on Select2. (@afercia)
  • Finish working on an accessible Tag Cloud WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.. See #35566.

#4-6, #accessibility, #wishlist

Dominik Schilling 9:24 pm on April 14, 2016
Tags: , wishlist   

WordPress 4.6: What’s on your wish list?

In the spirit of the existing wish list posts, I’d like know what you have for WordPress 4.6.

  • What are you most interested in seeing in WordPress 4.6 — big, or small?
  • What are your or your users’ biggest pain points?
  • What do you see as the most important UXUX User experience to be solved?
  • Which existing feature should get a “version 2”?

Look forward to hearing from you in the comments! Let’s make.wordpress.org/great-again! 😉

 

The WordPress 4.6 kick-off chat will be next Wednesday, April 20, 2016 20:00 UTC.

#4-6, #wishlist

Ella Van Durpe 10:57 pm on April 12, 2016
Tags: , , wishlist   

Editor wish list for 4.6 and beyond – chat summary

This list builds on the previous wish list. You can read the full chat in the archive.

Features

  • Allow suggestions and comments to be made, similar to what ICE does. This would make a good pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and feature project first. @eric and @azaozz seem to be interested in working on something like this.

Enhancements

  • (Publish) metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. box revamp. See #36474. Feedback welcome! @michael-arestad, @melchoyce, @helen, @mapk, @hugobaeta?

    Proof of concept.

    Proof of concept.

  • More experimenting with inline toolbars (separate for formatting and inserting). We could first do this on small screens where the toolbar would be fixed at the top, later maybe on big screens. See also #29923.
  • Could editor scrolling be improved (e.g. hide on scroll down)? See #36482, and also #31751.
  • Caption placeholder. Focusing on an image would give you a placeholder for a caption. See #32175.
  • Leaving dialog. Offer WordPress UIUI User interface on leaving the page if we can with the option to save changes. See #28566.
  • Advanced panel for the inline link toolbar, so plugins can add options. See #36312.
  • More formatting shortcuts (code blocks, bold, italic…)? See #36433, and also #6331.
    Decide whether to add bold and italic shortcuts at all, how to do the triple back tick shortcut.
    Try to merge with TinyMCE’s own textpattern plugin.
    Any other things we could automatically format in the editor? Curly quotes? Thinking about wptexturize().
  • Save and update without a page reload. For this we will need to look into nonce refreshing. See #7756.
  • Autosave in the browser revamp and improvements. Add some subtle, always present UI for restoring a post from in-browser autosave. Try to better detect when a restore may be needed (and show the current notice). See #36479.
  • Handling nested shortcodes. See #30094. I’m skeptical about this one, but please do let us know what your thoughts are if this interests you.
  • Save custom colours. See #31479.

Under The Hood

  • Consider the new non-editable TinyMCE plugin for our non-editable views. See #36434.
  • Consider the TinyMCE APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for inline toolbars, see #36480.
  • Responsive images for TinyMCE. See #36475. Depends on whether we will be saving the srcset and sizes attributes in post content, @joemcgill?
  • Handle inline image blobs in TinyMCE.
  • Different placeholders for more and nextpage tags. See #29804.
  • Auto embed bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.. See #25387.

Call for Contributors

If you would like to see more of these features implemented sooner, join us. Everybody can contribute as designer, UXUX User experience expert, developer, tester, the area you feel most comfortable with. Describing your workflow, how you use the editor, and what you find difficult or easy is also a very good way to contribute.

You can also leave feedback on the relevant tickets.

Let us know if you have more suggestions or ideas to add to the list.

The next chat will be Wednesday, 13 April, 18:00 UTC in #core-editor.

Andrew and Ella

#4-6, #editor, #wishlist

Ella Van Durpe 8:46 pm on January 16, 2016
Tags: , , wishlist   

Editor wish list for 4.5

  • Inline link dialog – mock ups from @joen – #33301.
  • More formatting shortcuts (code, hr…) – #33300.
  • Use the new non-editable blocks TinyMCE APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for our wpViews.
  • Mobile: more experimenting with inline toolbars (separate for formatting and inserting) – #29923 – @rboren?
  • Handle inline image blobs in TinyMCE.
  • Respimg for TinyMCE – @joemcgill?
  • Can editor scrolling be improved (e.g. hide on scroll down)? Also, #31751.
  • Caption placeholder – #32175.
  • Leaving dialog – #28566.
  • Save and update without a page reload. For this we will need to look into nonce refreshing – #7756 – @michael-arestad, Improving Post New.
  • Publish metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. box revamp – Example. – @michael-arestad, Improving Post New.

#4-5, #editor, #wishlist

Kira Schroder 10:22 pm on December 30, 2015
Tags: , wishlist   

WordPress 4.5: What’s on your Wishlist?

A few weeks ago, I put out an initial call for volunteers for 4.5.

In the spirit of the much-commented @wonderboymusic 4.4 Wishlist post, I’d like to extend the call a bit more.

  • What are you most interested in seeing in WordPress 4.5 — big, or small?
  • What are your or your users’ biggest pain points?
  • What do you see as the most important UXUX User experience or performance low-hanging fruit to be solved?

Look forward to hearing from you in the comments!

The WordPress 4.5 kickoff chat will be next Wednesday, January 6, 2016 16:00 UTC-5.

#4-5, #wishlist

Scott Taylor 3:58 pm on August 19, 2015
Tags: , wishlist   

WordPress 4.4: What’s on your wishlist?

4.4 has unofficially kicked off, now that 4.3 is out the door. As with any release, we want to garden TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., squash bugs, add new tools for dev, and wow our users.

I have spoken to many of my fellow core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. about their own wish lists. Now, it’s your turn:

  • What do you want to see happen in 4.4?
  • What are pain points for users?
  • What features can we add or iterate upon to empower our user base?

It can be anything: big or small.

As most of you know, I am leading WordPress 4.4

If we’ve never met, hello! You can learn a lot about me here:

 

#4-4, #wishlist