Customize Kickoff and Weekly Meetings for 4.7

We’ll be holding weekly meetings for the Customize component during the 4.7 cycle, to discuss both larger projects and smaller tickets needed attention. Meetings will be held on Mondays at 17:00 UTC in #core-customize and will last up to one hour, with additional continuous discussion happening throughout the week in the channel and in tickets.

The first meeting, on Monday, August 29th, will also serve as a kickoff for the customize efforts in 4.7, following up on yesterday’s general 4.7 kickoff.

Agenda for 2016-08-29 Meeting

The goal of this kickoff meeting will be to identify scope for 4.7 for the customize component. Most importantly, we need to identify larger projects that shouldn’t be considered for 4.7 (such as the customize posts project), so that we can prioritize those efforts that could get into 4.7 from now until betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 hits. We will take some time to post any updates on future releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. projects each week.

Potential 4.7 Projects

  • Create page-based nav menus without leaving live preview – #34923
  • A new experience for themes in the customizerCustomizer 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.#37661
  • Code-editing gateways, via CSSCSS Cascading Style Sheets.#35395
  • Customizer browser history#28536
  • Customizer notifications center – #35210
  • Customize snapshots/transactions#30937
  • Refactoring sliding panels UIUI User interface#34391
  • Improve UI for linking preview elements to controls – #27403
  • Twenty Seventeen – the customize team should be involved with the new theme, so that we can build any new coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. that can facilitate it. Since default themes should be “state of the art”, let’s makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure that every option can be previewed instantly with postMessage, and fully supports selective refresh.

Active Future Release Project Updates

Additional Tickets Needing Attention

  • Improving contrast and UI consistency in the customizer – #29158needs-testing
  • Improve custom background properties UI – #22058 – needs additional feedback on the latest proposal, and a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.
  • Appropriate means for themes to add top-level promotional links – #37335 – needs input from theme review team

Ticketticket Created for both bug reports and feature development on the bug tracker. Scrub

  • Identify tickets ready for commit consideration, and 4.7 milestoning from future release tickets with a patch.
  • We’ll pick a different query to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. each week. For example, bugs awaiting review (need verification).

We’re looking forward to seeing you at the meeting!

#4-7, #customize