The Customize component covers all aspects of WordPress’ framework for live-previewing any change to your site. Tickets in this component cover issues including bugs in the Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (
Customizer development was most active from WordPress versions 3.9 through 4.9. As of WordPress 5.0, Customizer development is currently focused on bug 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. fixes and smaller enhancements. Most significant feature development is ongoing as part of the Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project’s integration with the customizer. In trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and on GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, new contributors are always welcome, whether you bring code, design help, testing, or anything else. Below is a summary of our larger past and future projects, which are accompanied by countless smaller changes.
Projects for Future Releases
Several projects remain planned on the long-term wishlist. These projects are looking for contributors to build on the existing experiments to work towards potential future inclusion in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- Expose UI for revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and branching/conflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. management of customize changesets (see #21666, #31436)
- Improve loading of the Customizer from the front-end (see #28602, #28661)
- Introduce inline editing/inline controls within the preview
- Explore content-editing/front-end-editing integration (integrated with the Gutenberg project)
- Improve performance wherever possible (ongoing goal)
For details on long-term goals and visioning for the customizer, see the proposed roadmap from 2015.
These plugins container implement features that may be incorporated into core in the future, as was done previously with Widget Customizer, Menu Customizer, Customizer UI Experiments, Customize Snapshots, and more.
Completed Milestone Highlights
- Customizer sidebar width is now variable – #32296
- Add indicator when additional widget 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. areas are hidden – #39087
- Customizer Introduced in Core
Recent posts on the make/core blog (versus network, site)
View all posts tagged customize.
Recent posts on the make/test blog
- Customizer: Browse, Install, Preview Themes on Mobile (October 1, 2016)
- Customizer, Preview: Visual survey of customizer device preview (February 24, 2016)
- Customize: Site logo and icon, 33755.5.diff, iPhone 6+ (February 19, 2016)
- Customize: Site logo, 33755.3.diff, Macnchrome, iPhone 6+ (February 18, 2016)
- Customize: preview site responsiveness, Macnchrome, iPad Air, iPhone 6+ (September 2, 2015)
View all posts tagged customize.
196 open tickets in the Customize component
196 open tickets. Last 7 days: -1 ticket Created for both bug reports and feature development on the bug tracker.
12 tickets that have no replies
View list on Trac
- #38957 Customize Menus: Menu locations should be able to opt-out of menu item types that can be added to associated menus
- #40831 Customize: Further improve JS inline documentation docs
- #42191 Customize: Selectively merge settings from autosave revisions
- #42272 Customize: Use client-side templates for rendering base controls
- #42872 Customize: Improve display of theme tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) filters on mobile
- #44665 Add a "Create New Menu" button to the menu widget ui
- #51820 Make starter content for fresh sites more discoverable
- #54184 HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities get decoded in Customizer text fields ui administration coding-standards
- #55146 WP5.9 Customizer partially white-screens in Safari browser administration
- #55587 Customize preview removes URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org query parameters of the same name and keeps only the last one
- #55766 Site icon checkbox to use the site logo
- #58938 Custom permalink indexing issue
1 ticket slated for 6.4
View list in Trac
- #57170 Fix invalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. menu-item-parent
196 open tickets
Open enhancements: 73 View list on Trac
Open tasks: 3 View list on Trac
Open feature requests: 10 View list on Trac
Help maintain this component
Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of Core are always seeking to mentor others to impart their knowledge.
Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.
Contributors following this component: