Make WordPress Core

Opened 4 weeks ago

Closed 3 weeks ago

Last modified 3 weeks ago

#62203 closed feature request (invalid)

Theme editor and other features... for 2025?

Reported by: lipes's profile lipes Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.6.2
Component: General Keywords: 2nd-opinion close
Focuses: ui, accessibility, javascript, css, administration, template Cc:

Description

After using Joomla, Drupal, it's still complicated to build complete layouts in WordPress, compared to what currently exists in other systems that have recently appeared and are evolving rapidly (not to mention the names).
Why do we have to be so dependent on plugins for building versatility?

For example:

  1. Make it possible to hide blocks that don't need to be shown in certain views, e.g. tablet or mobile phone.
  2. Being able to change more CSS specifications, for example the specific dimensions for different view types, controlled independently;
  3. Being able to pin sections of the header while scrolling. For example, the menu can be fixed and follow the movement of the website, with an on/off function in the administrator's backend area;
  4. Being able to choose and have, or add, a library of vector icons, On/Off in the Admin backend area;
  5. Be able to choose to easily add functions for changing colour contrast on the front-end website itself, with an on/off function in the administrator's backend area;
  6. You can choose to add a scroll up function;
  7. You can easily add more functions to the menus (mega-menu) with the possibility of adding images, divisions, among other CSS options;
  8. Allow drop-down menu functions when a certain element (image, link, etc.) is clicked on or the mouse hovers over. This would make it possible to create more menus and give more versatility.
  9. Possibility of having a popup function (without using plugins), with an on/off function in the administrator's backend area;
  10. Possibility of having an image slide function (Hero Zone) with on/off function in the administrator's backend area;
  11. It would be great (once and for all) if you liberalised the translation system for all areas of the website, without being dependent on third-party plugins, with an on/off function in the administrator's backend area;
  12. When the mouse is over a certain block, allow easy addition of zoom in, zoom out, etc. image change effects, with an on/off function in the administrator's backend area;

I'd like to ask the WP team if, please, after so many years of WP, they could make better improvements for 2025, with more options in the system (On/Off, allowing greater flexibility in editing the layout of themes and blocks? Think huge to be at top of the CMS and more people will come (don't leave the platform).
Building with greater flexibility on different platforms (computer, tablet, mobile phone) will be more user-friendly, but the WP platform should be more at the top of the CMS in terms of offering native features and specifications without depending on third parties.

Change History (4)

#1 @poena
3 weeks ago

Hi @lipes
Thank you for your thorough list of suggestions.

I would like to ask that you kindly use this ticket system for individual enhancements and bug reports.
It is not possible to manage a list of his scale in one single ticket.

The more limited and detailed an issue is, the easier it is to solve that specific problem.

Changes to blocks, the block editor, and site editor are managed in the Gutenberg GitHub repository.
Please search through the repositories before creating issues, as many of the items you bring up are already reported, in active discussion, or even under development.

Last edited 3 weeks ago by poena (previous) (diff)

#2 @poena
3 weeks ago

  • Component changed from Administration to General
  • Keywords close added; changes-requested removed

#3 @joedolson
3 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Hi, @lipes! I agree with @poena. We certainly appreciate your intentions, but as a ticket this is not actionable, as it covers far too much ground, some of which is likely to be duplicated elsewhere.

Closing as invalid, due to the unactionable scope. I highly encourage you to break your request into individual tickets and issues and distribute them between trac (for WordPress core) and Github (for the block editor and site editor) as appropriate.

This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.


3 weeks ago

Note: See TracTickets for help on using tickets.