Meeting notes for 2016 July 26

We had a solid discussion based on this week’s agenda.

Read the meeting transcript in the Slack archives. (A Slack account is required)

Removing exception to hardcoded scripts guideline

The first item was to discuss the removal of an exception to one of our existing guidelines when WordPress 4.6 is released:

No hard coding of scripts and styles unless a browser workaround script.

We will no longer be allowing browser workaround scripts to be hardcoded. The new guideline would be rewritten to become:

No hard coding of scripts and styles.

The reason to remove the exception is because WordPress has the wp_script_add_data() function for handling this. When WP 4.6 rolls out, that’ll be more than 3 versions for back-compatibility.

So, it’s time to update your code if you have any hardcoded scripts remaining. You can find an example in the TwentySixteen theme.

UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. considerations for the feature filterFilter Filters are one of the two types of Hooks They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.

@celloexpressions brought up the idea of making the “subjects” in the feature filter a drop-down. We’d like to see user testing and give time for the new subjects list to be used first.

In our next tags iteration (next January), we want to consider overall improvements to the entire feature filter box and what can be done to make this better for users.

Adding the review baseline to the handbook

@sakinshrestha is getting his first project as a key reviewer.

He’ll begin work on adding the review baseline to the handbook. This is to make sure theme authors are aware of how our new review flow works.