This week’s meeting:
Today we had our weekly meeting. You can find the archive here: https://wordpress.slack.com/archives/themereview/p1416938377003366
There are some good posts to catch up on this make.blog:
Understanding the APIs Related to Theme Options
Design challenge weekend
Handbook version one refresh goes live tomorrow. This focuses on guidelines (required, recommended) and restructuring. We need to focus and not edit all at once, lets collect feedback in comments. I will be making blog post about this when happens.
There is a mentoring update too: https://make.wordpress.org/themes/2014/11/24/mentoring-update-2/. We’re looking for mentors so if you fit let us know!
There is an issue with the guideline dropping having to have comments.php. @frank-klein brought this up.
This lead into a general topic about hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and what we should or shouldn’t support. This then grew as a discussion.
@greenshady brought up the shortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. issue as to either fix the theme check or show an info notice. As a result we decided a new requirement:
“No shortcodes are allowed”
Next week we shall have a meeting on hooks and what ones should even be required. This will be kicked off by a post from @chipbennett on this blog. You are free to add your voice to that opinion post. We’re keen to get a discussion and work through this.