WordPress.org

Theme Review Team

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • Jose Castaneda 8:07 pm on September 20, 2016 Permalink |  

    Meeting notes 2016-09-20 

    Items discussed

    Our usual meeting time 1800UTC on Slack #themereview channel the following items were discussed.

     
  • Ulrich 7:42 pm on September 12, 2016 Permalink |  

    Agenda for 2016 September 13 

    The Theme Review Team holds a meeting weekly and we encourage all members to attend.

    Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

    Topics:

    • Review shindig/session on 1st/2nd October

    Related Information from other teams

    • A New Experience for Discovering, Installing, and Previewing Themes in the Customizer ( Core ticket #37661 )
    • There is a new parameter item_spacing for wp_nav_menu() and wp_list_pages() to control white space between menu items. ( Core ticket #35206 )
    • Add multi-panel feature to pages through add_theme_support ( Core ticket #37974 )
    • Standardize API for info links to customizer ( Core ticket #37335 )
    • Theme Developer Handbook

    New Functions, Hooks, and Behaviour for Theme Developers in WordPress 4.7

    Say Hello to Twenty Seventeen 👋🏽

    The meetings typically last 30 minutes.

    If time permits, additional topics may be discussed.

    If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

     
  • Justin Tadlock 7:22 pm on September 6, 2016 Permalink |  

    Meeting Summary: 2016-09-06 

    We had a solid meeting and covered a good bit of ground this week. You can view the full meeting notes in the Slack archive. A Slack account is required.

    Primarily, we focused on 2 big items with additional announcements as noted in the agenda post.

    Monthly theme review gatherings

    After the success of this past weekend’s gathering, we’re going to continue having monthly shindigs/hootenannies for the team.

    Next month’s shindig: Weekend of Oct. 1-2

    Ambassador: @cristiano.zanca

    We still need to decide on a focus for next month’s meeting. The following 2 ideas have been proposed:

    • Compile a list of common theme issues from shindig and follow up on the Make Themes blog.
    • Live Slack mentoring from admins.

    Subject tag limit

    Because we’re seeing more and more themes adding upwards of all 9 subject tags, we decided on a limit of 3 subject tags per theme. This goes into effect immediately.

    This is a temporary solution until we revisit tags in our big tags meeting in January where we might want to bring in new tags like multipurpose for themes not suited to 1-3 tags.

     
  • Ulrich 2:06 pm on September 5, 2016 Permalink |  

    Agenda for 2016 September 6 

    The Theme Review Team holds a meeting weekly and we encourage all members to attend.

    Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

    Topics:

    • Monthly Review Shindigs/Hootenannies
      • We had our last monthly Review Session on Saturday 3rd.
      • Define a date for the next one.
      • Define what we will focus on.
      • Assign someone who is in charge of spreading the word
    • @rinkuyadav999 has a proposal to only allow themes to use only one subject tag.
    • As part the Theme Automation we need some extra documentation
      • For each sniff that we add a requirement should be noted to back it. I have copied the current requirements to a separate page and will move/update any requirements to the Automated requirements section.
      • We need to have a more detailed explanation with links to documentation for every error message. This will need a separate page too but we can work on this once the tests are all ready.

    Related Information from other teams

    • Standardize API for info links to customizer ( Core ticket #37335 )
    • Theme Developer Handbook
    • @helen mentioned in the core dev meeting there needs to be a dedicated theming API/support team because there will be a Twenty Seventeen; actual details on that next week. There will need to be really robust teams on both the theme and theme support pieces, likely with subteams even.
    • A New Experience for Discovering, Installing, and Previewing Themes in the Customizer ( Core ticket #37661 )

    The meetings typically last 30 minutes. If time permits, additional topics may be discussed.

    If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

     
  • Jose Castaneda 6:46 pm on August 30, 2016 Permalink |  

    Meeting Summary 2016-08-30 

    Items discussed

    Slack link to meeting  [Slack account needed]

    • Core ticket #37335
      • currently using JS ( recommend against )
      • document better examples using core API
    • Monthly Review Shindigs/Hootenannies
      • We are going to attempt having theme review sessions once a month. This coming weekend September 3 will be the first.
    • Theme Developer Handbook

    Thanks to those who attended and participated.

     
    • Shaped Pixels 10:28 pm on September 1, 2016 Permalink | Log in to Reply

      I wasn’t able to join in on the meeting yesterday and only read part of the results in reference to the customizer and theme upsell links being added, as some themes have the buttons added. In mine, I have 1 button for a pro version, then a few more (1 for theme support at .org, 1 for reviews at .org, and 1 for theme documentation).

      If I understand correctly, this method of adding buttons to the top of the customizer is currently being discussed as to whether it will be allowed or if an alternate method can be added by the theme author either as buttons or links or not allowed at all? I have 3 themes in the queue for the last 5 months and awaiting review, so my question is, can I still leave the buttons in there until a final decision is made on this subject?

      I’ve set mine up with multiple buttons for the benefit of the end-user. Aside from the upsell button, the others for a user review, but most importantly, the one for theme documentation is very important. As it stands right now, text files like Changelog and the Readme files are in with the rest of the theme files, but most if not all users are not aware these exist or do not know how to access them. So having a visible button(s) helps by giving easy access to setup tutorials and other theme documentation….something to consider when the team is deciding on how to standardize it.

    • Shaped Pixels 10:29 pm on September 1, 2016 Permalink | Log in to Reply

      By the way… this September 3rd theme review day event….is this in reference to the Admin queue or New theme queue?

    • Carolina Nymark 12:32 pm on September 2, 2016 Permalink | Log in to Reply

      A side note – you are allowed a full page in the admin. This page can be used for documentation.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar