Jose Castaneda 10:36 pm on April 29, 2015

A revised readme

In our meeting we talked about the addition of a changelog. The consensus was including it in the readme.txt file like plugins do. To quote Otto:

If we had it in the readme.txt, we’d expose the data to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. via the 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., same as we already do with plugins

In order to make this happen we need to determine what – from the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party’s readme – we can use, create a sample file and have all theme authors adopt it. @greenshady provided a sample one and @grapplerulrich even added in about a dedicated license section – which I think we can do.

Below is a revised version of Justin’s and includes Ulrich’s idea of the bundled resources section.

=== Theme Name ===
Contributors: (this should be a list of wordpress.org userid's)
Tags: left-sidebar, fixed-width, custom-background
Requires at least: 4.0
Tested up to: 4.3-alpha
Stable tag: 1.0.3
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Short description. No more than 150 chars.

== Description ==
Theme desc.

== Frequently Asked Questions ==

= A question that someone might have =

An answer to that question.

== Changelog ==

= 1.0 =
* Added new option

= 0.5 =
* Security bug addressed
* Changed thumbnail size

== Upgrade Notice ==

= 1.0 =
* Upgrade notices describe the reason a user should upgrade.  No more than 300 characters.

= 0.5 =

* This version fixes a security related bug.  Upgrade immediately.

== Resources ==
* magnify.jpg © 2014 Jane Doe, CC0
* supermenu.js © 2013-2015 James Today, MIT

Chime in and discuss!

NateWr 10:40 pm on April 29, 2015

It would be terrific if the specification encouraged (required?) dates for each release in the Changelog. A lot of plugins don’t include them, but it’s a great way to get a sense of a product’s maintenance record over time.
- Justin Tadlock 11:05 pm on April 29, 2015
  
  +1 to recommending a change log format with the date included. I’m not sure I’d want to require a specific format though.
- Jose Castaneda 8:54 pm on April 30, 2015
  I thought about that as well. Something like
```
= 0.5 YYYY/DD/MM =
```
  - usability.idealist 11:41 am on May 5, 2015
    
    Maybe not only North-america centric. Make it “YYYY-MM-DD”, then it’s international and everbody should understand it 😉
    
    cu, w0lf.
    - Daedalon 5:09 pm on May 6, 2015
      
      +1 for the most international format, YYYY-MM-DD. This format is also the easiest one for seeing at a glance whether updates had a short or long time in between them.
    - Jose Castaneda 5:12 pm on May 6, 2015
      
      I’m fine with that.
- Samuel Wood (Otto) 1:21 am on May 7, 2015
  
  -1 to dates. We can get that via other means, and it duplicates data and introduces sync problems. Version is more than enough for us to expose dates as well.
  - Aaron Jorbin 3:12 am on May 7, 2015
    
    I agree with Otto. Also, this date is ideally the public release date and since themes need to go through an approval process, this date isn’t known in advance.
Justin Tadlock 11:03 pm on April 29, 2015

The only issue I see with a “License/Resources” section is if a theme author normally puts those licenses in a LICENSE file. I’d even argue that the license file should be the preferred method of adding license + copyright declarations. Nevertheless, I think it’s a good idea to account for it in the readme.txt standard format.

It’s something to consider anyway.
- Samuel Wood (Otto) 1:27 am on May 7, 2015
  
  I agree, a separate license file is better. It can be an optional “other”section if you like though. Dunno. Licenses matter, but not enough to expose this to end users like that.
  - Chip Bennett 3:18 pm on May 7, 2015
    
    I don’t agree that a separate license file is *better*. I don’t think either approach is better or worse than the other. If there are infrastructure/implementation reasons to favor one over the other, then I understand. Otherwise, I see it as a bikeshed question, and have no reason to argue strongly for one or the other.
    - usability.idealist 9:37 pm on May 15, 2015
      
      A separate LICENSE file is BETTER, because it’s lessening the overall structocalypse. The user doesnt give a lot about what’s underneath, and in most cases, no developer will care much about the LICENSE of the resources, as long as they work.
      
      So, putting up to 30 different license items into the README file would clutter it up tremendiously.
      
      TL;DR: +1 for licenses listed in the file of the same name, to enforce structure and reduce clutter.
      
      cu, w0lf.
Justin Tadlock 11:10 pm on April 29, 2015
Some more ideas to ponder. Some things to consider dropping from the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.:
- Contributors – Is this useful with only one theme author allowed?
- Tags – Already defined in style.css
- Stable tag – Theme repo always uses latest version
- License – Defined in style.css
- License URI – Defined in style.css
I also dislike the “Tested up to” header because it can give users a bad impression if you’re not updating your theme once every couple of months (most themes don’t need this much updating).
- Ulrich 11:19 pm on April 29, 2015
  
  Contributors may be possible sometime in the future. Otto said he has some similar code which he could use. https://meta.trac.wordpress.org/ticket/27
  - Justin Tadlock 11:23 pm on April 29, 2015
    
    I figured that might be the case. We should keep that one if there are possible plans to allow multiple contributors.
- Tammie 9:38 am on April 30, 2015
  
  I actually think contributors is important. I have in the past worked on a multiple authored theme that ended up with an account having to be made we all accessed – not awesome. We then still couldn’t credit everyone. It was a bit sad as a community project for BuddyPress.
- Tammie 9:39 am on April 30, 2015
  
  Tested up to is important from a ‘what does it work with’. I actually think you could say supported versions and be less dramatic.
  - Chip Bennett 3:26 pm on May 2, 2015
    
    “Tested up to” and “Requires” are important in combination, and could be used very powerfully by the WP Admin, by hiding (or requiring a confirmation before installing) Themes that do not support the user’s current WordPress version.
    
    For example, I provide no intentional backward compatibility in my Theme. So, my “Requires” is almost always the same as, or perhaps one version prior to, the current WordPress version. So, if someone running an older version tries to install my Theme, the Admin could compare the user’s version (e.g. 3.9) to my Theme’s “Requires” and “Tested up to” (e.g. 4.0), and either not show my Theme, or display an “are you sure?” dialogue or something.
    - usability.idealist 9:50 pm on May 15, 2015
      
      Maybe just a big fat notice.
      
      Hiding things is nasty (it’s basically censorship, but that’s another topic).
      Just take a look at Firefox Extension directory. LOTS of the stuff in there hasn’t been “updated” to work with current versions .. but about 70% of them do so.
      
      Now, Mozilla is hiding them from view, and you have to explicitely UN-select the automatically claimed FF version. Of corpse, you have to know that in the first place. So for un-experienced users, who just want to get their site roling quickly (and I’d say they’re making up the majority of the WP users), even such an option would be .. well, I’d guess most of them wouldn’t even recognize it.
      
      And: Although I’d consider myself a professional with the web and its UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. shenannigans in general, but sometimes it still happens that I oversee this option, coursing and cruising WTF the extensions I wanted are not being displayed .. starting to fume again when finaily remembering that option.
      
      TL;DR: Annoying your users in the first place is not the best.
      
      So +1 for a big fat notice.
      
      -1 for a “click something” prompt. Thanks to Windows, the current “we use cookies, did you know” thingy and the recent data security apocalypse, most users are potty-trained to automatically click on the “okay” button.
      
      cu, w0lf.
- Jose Castaneda 8:28 pm on April 30, 2015
  - tags/license/license uri – I agree, a little redundant.
  - stable tag – I only consider this because there are some that link to a githubGitHub 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/ repo
- Chip Bennett 3:23 pm on May 2, 2015
  
  I like “Tested up to”, but perhaps for Themes, we could keep it at major versions only. There is almost no reason for a Theme to break due to a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
  
  Plugins are potentially different, but for a Theme that properly differentiates between presentation and functionality, keeping “Tested up to” current for major releases should suffice.
Tomas Mackevicius 11:15 pm on April 29, 2015

Is it required to use format:

== Resources ==

or I could use:

Resources
=========

?
- Samuel Wood (Otto) 1:25 am on May 7, 2015
  
  The first would be required. It fits the current mardown parsing scheme.
Tomas Mackevicius 11:18 pm on April 29, 2015

Also I used to think that Stable TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. was about WP version, but in this example it doesn’t look like.
- Justin Tadlock 11:22 pm on April 29, 2015
  
  Stable TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. refers to which version is the stable version of the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party in the SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. repo. For example, you could be developing version 2.0 but the stable version is 1.5. Users would be shown version 1.5 as opposed to 2.0.
  
  Because theme authors don’t have access to SVN, the stable version is always the latest version.
  - Tomas Mackevicius 11:44 pm on April 29, 2015
    
    Thank you!
- Samuel Wood (Otto) 1:23 am on May 7, 2015
  
  Stable TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. makes no sense here. Dump it.
Emil Uzelac 12:58 am on April 30, 2015

Contributors! Will that work?
- Jose Castaneda 8:23 pm on April 30, 2015
  
  It should down the road. https://meta.trac.wordpress.org/ticket/27
Edward Caissie 1:10 am on April 30, 2015
As offered in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. … I go with this currently (from my Opus Primus them):

=== Opus Primus readme.txt ===
- Last revised April 28, 2015
== Contents ==
- Copyright
- Licenses
- Screenshots
- Basic FAQ
- Notes
- Changelog
- Review Tickets
== Copyright ==
Copyright (c) 2012-2015, Opus Primus

This file is part of Opus Primus.

Opus Primus is free software; you can redistribute it and/or modify it under the
terms of the GNU General Public License version 2, as published by the Free
Software Foundation.

You may NOT assume that you can use any other version of the GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples..

This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with
this program; if not, write to:

Free Software Foundation, Inc.
51 Franklin St, Fifth Floor
Boston, MA 02110-1301 USA

The license for this software can also likely be found here:
http://www.gnu.org/licenses/gpl-2.0.html

Note: All Opus Primus file Copyright years start with the first year of use and
are amended with subsequent years based on theme publication regardless of any
change or modification to the actual file.

== Licenses ==
All items are licensed under the GNU General Public License v2; or, as the case
may be, individually noted below.
- Normalize.css is a project by Nicolas Gallagher and Jonathan Neal. A minimized
version is used. Licensed as Public Domain
- for more information see http://necolas.github.com/normalize.css/
- Font: Merienda One
Copyright (c) 2011, Eduardo Tunni (http://www.tipo.net.ar), with Reserved Font Name “Merienda”
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: http://scripts.sil.org/OFL
- Font: Underwood Champion
Copyright (c) 2009, Vic Fieger (http://www.vicfieger.com/)
The Vic Fieger fonts are freeware, to be downloaded and used by anyone who wants them for free.
This license can also be found at this permalink: http://www.fontsquirrel.com/license/Underwood-Champion
- Theme Hook Alliance
Licensed as GNU General Public License, v2 (or newer)
The details of the copyright and license of this work may be found internal to
the relevant files found under ..\stanzas\tha\ or at this website: https://github.com/zamoose/themehookalliance
- SlickNav – Responsive Mobile Menu jQuery PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party – Version 1.0.1
Copyright (c) 2014, Josh Cope (http://slicknav.com)
Opus Primus uses an adaptation of the plugin which is under a MIT License
The details of the license can be found under ../js/SlickNav/MIT-LICENSE.txt
Only the relevant files have been included, a complete download can be found at https://github.com/ComputerWolf/SlickNav
- FitVids – built by Chris Coyier and Paravel – Version 1.1
Copyright (c) 2013, Chris Coyier – http://css-tricks.com + Dave Rupert – http://daverupert.com
Released under the WTFPL license – http://sam.zoy.org/wtfpl/
Only the plugin file has been included, the complete project can be found at https://github.com/davatron5000/FitVids.js

This above may not be construed as overriding any item with a previously written
and applied license, stated or not, which will take precedence over anything
written here.

== Screenshots ==

== Basic FAQ ==
Q: I just updated to version 1.3, what could be causing these child-theme errors?
With version 1.3 of Opus Primus the calls to the classes were changed from using
`require_once` to `locate_template`. This then followed files being updated from
calling the class global variable to creating a “new” class instance as needed.
This is expected to provide better child-theme compatibility going forward and
only be a one-time correction for existing child-themes.

Q: What are Stanzas?
Stanzas are meant to add additional functionality specifically to Opus Primus by
either using specific Opus Primus assets, such as a particular font face; or, by
hooking into specific action and/or filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/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. hooksHooks 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. only found in Opus Primus.

Q: What is the difference between how the “Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts.” is used on a post and
how it is used on a page?
The “Featured Image” on a page is set to ideally be used as a “banner” on pages;
and, to add emphasis for posts when they are viewed as part of a list, such as
the index view or in archives.

Q: How do the breadcrumb trails work?
There are two different breadcrumb trails used in Opus Primus. One type is used
on pages and shows the page hierarchy from the highest level to the lowest. The
second trail is used on single views of posts and shows the first categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and
Post-Format of the post, both linked to their respective archive.

Q: Where are the menu locations, and how are they used?
There are three menu locations defined in Opus Primus.
- The Primary Menu, located at the top of the page above the main content area.
- The Secondary Menu, no location is set by default; the menu has been pre-
defined for uses as the case may be, for example, page templates or Child-Themes
- The Search Results Menu, located at the bottom of the content area when there
are no search results returned, especially in the case of a “404” error be sent.

Q: Is Opus Primus designed to be responsive to multiple screen sizes?
In a word, no. Although the theme does include some minimal CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. specifically
geared towards being responsive to multiple screen sizes the ideal method we
recommend at this time is to take advantage of one of the many quality plugins
available from the WordPress Extend Plugins repository to handle these requests.
Please note, we intend to continue in our efforts to provide an inclusive method
of managing these requests in future versions.

Q: How do I modify an existing function from one of the classes?
Most WordPress functions included with the theme will have their own filter,
otherwise it would be recommended to extend the class and overload the theme
function you are trying to modify.

Q: How does Opus Primus automatically handle multiple column layouts?
Through some CSS trickery and code logic Opus Primus will display by default
one, two, or three columns depending on which sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. widgetWidget 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 active.
There are four(4) widget areas built into two sidebar areas.

The following will show how, if active, they affect the layout:
- Full Page (one-column): no active sidebar widget areas
- Two-Column: widget areas active in only one sidebar area
- Three-Column: at least one widget area active in each sidebar area
Q: What happened to the LESS components of the theme?
The LESS components of the theme were effectively removed at version 1.2 as a
means to improve load time. The styles that were generated by the LESS script
and related file were compiled and merged into the main theme stylesheet.

== Notes ==
1. $content_width is set based on how many columns being used and the common
display size of 1024px * 768px.

This being the case, the following widths will be used:
- one-column: 990px
- two-column: 700px
- three-column: 450px
2. Default Menu depth levels may be of concern in some cases. As it stands, the
default menus are not restricted to any specific depth except the Search Results
Menu which is restricted to a single level only when a custom menu is not used.

3. Future revisionsRevisions 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. of the ‘theme-version-guidelines.txt’ file may not
necessarily be recorded in the changelog. The “Theme Version Guidelines” page
found at http://opusprimus.com/under-the-page/theme-version-guidelines/ will
be considered the most current at all times. The version of the guidelines
included with the theme will simply be a copy of the noted page.

== Changelog ==
=== Opus Primus changelog.txt ===
Last revised April 18, 2015
Please note, the Opus Primus copyright can be found at the end of this file.

= Version 1.4 =
- Released …
= Code =
- Added `widgets` to the HTML5 theme supported items
- Added `number_format_i18n` to better accommodate locale based values
- Added two classes for use in rendering the comments link text displayed … or not
- Added `Share the Author Wealth` method, not implemented as a display element, yet
- Change all classes to a singleton style
- Ensure `$pagination` has been initialized in `OpusPrimusNavigation::pagination` method
- Moved the `support_comment` method back into the `OpusPrimusStructures` class
- Moved the `before_comment_form` and `comments_form_closed` methods back into the `OpusPrimusComments` class
- Refactored `OpusPrimusComments::comments_link` to use the WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. more effectively
- Removed `$screen` parameter as not necessary in Taglines Stanza
- Renamed file `class.OpusPrimusHeaders.php` to `class.OpusPrimusHeader.php` for consistency
= CSS =
- Added class definition to hide comment link text when comments are closed and there are no comments
- Adjusted CSS to not reference `li` elements in default widget styles
= Miscellaneous =
- i18n: Added base `.po` file as well as English (Canadian) `.pomo` files
- i18n: `null` does not need to be translated
- i18n: Symbolic characters do not need to be translated
- Added `opus_authors_list` filter hook
- Continue removal of extraneous end of structure comments …
/** ————————————————————————- */
= Version 1.3.4 =
- Released March 2015
= Code =
- Used a more specific element identifier for the SlickNav `prependTo` parameter
= Miscellaneous =
- Continue removal of extraneous end of structure comments …
/** ————————————————————————- */
= Version 1.3.3 =
- Released March 2015
- Added sanity checks to ensure there is actually an image in use when returning the featured image view.
/** ————————————————————————- */
= Version 1.3.2 =
- Released March 2015
- Added support for the `title` tag via `add_theme_support` function
/** ————————————————————————- */
= Version 1.3.1 =
- Released March 2015
= Code =
- Added `get_the_posts_pagination` for navigation between pages of posts
- Added `hide_category_widget_list_items` method and related hook
- Added some escaping sanitization and linked Featured Image to post via the post ID
- Changed method to return the Featured Thumbnail versus outputting it
- Changed from using `get_the_time` to `date_i18n` for `OpusPrimusImages::exif_timestamp` method
- Extracted code from `featured_thumbnail` method to create `featured_thumbnail_single_view` method
- Improved look of navigation links in `OpusPrimusNavigation::multiple_pages_link` method
= CSS =
- Added `=== Screen Reader Text ===` section
- Added `h5.comments-link` definition to provide a better aesthetic location
- Added styling to navigation for moving within a single post’s pages
- Incorporated WordPress recommended styles for `.screen-reader-text` class
= Miscellaneous =
- Added `opus_featured_thumbnail_single_view_portrait` filter hook and updated `hooks-filters.txt`
- Begin removal of extraneous end of structure comments …
- Inline documentation clean-up and re-organization
- Updated `hooks-filters.txt` file
/** ————————————————————————- */
== Version 1.3 ==
- Released November 2014
= Code =
- Added `post-title-link` wrapper class to better manage Post Title output
- Added WordPress HTML5 markup support for search form, comment form, comment list, and caption
- Added sanity checks to ensure constants are not already defined
- Added `OpusPrimusRouter` class to replace path and URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org CONSTANTS
- Added Child-Theme “slug” for easier customizations
- Added empty hooks before and after showing the breadcrumbs
- Added OpusPrimusComments class methods to `functions.php` to work-around duplicate output issue
- Added checks for Child-Theme and relevant references to `opus_primus_support_comment`
- Better code organization to only load classes when needed
- Changed post breadcrumb link to the WordPress shortlink
- Create `/lib/` folder to store bundled libraries and ancillary files
- Enqueue JavaScripts and CSS for SlickNav JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. plugin integration to handle mobile menus
- Extracted the Opus Primus PullQuotes Stanza (see https://github.com/Cais/opus-primus-pullquotes)
- Moved `support_comment` method to `functions.php` to eliminate duplicate output
- Replaced the majority of `require_once` calls with `locate_template` calls
- Replaced `global` variable calls with `new` class instances
- Update to use `preg_match_all` in OpusPrimusGallery featured and secondary id methods
= CSS =
- Added new typography styles for better reading
- Added styles for the “BNS Login” plugin
- Added `clear: both` to `footer`
- Added `width: auto;` for `th` and `td` elements
- Added `#headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.-widgets` to the “Clearance” section of `opus-primus.css`
- Added minor `attachment` related styles
- Added better search form aesthetics in the sidebar
- Change default `ul` list-style property to `none inside`
- Hide the post/page breadcrumbs in mobile displays
- Hide “Search” button for search form
- Removed duplicate definitions from media queries stylesheet
- Removed unused `div#top-navigation-menu` definition
- Removed unused `nav div.nav ul li` definition
- Updated `editor-style.css` to match new typography of theme
- Updated galleries styles to use HTML5 markup
- Updated font-size of excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. more link symbol to 35px from 200%
= JavaScript =
- Integrated “SlickNav” (Created by Josh Cope – @computerwolf) for mobile menu support
- Integrated “FitVids” built by Chris Coyier (http://chriscoyier.net/) and Paravel (http://paravelinc.com/)
= Miscellaneous
- Added Contact Form 7 compatibility
- Added BNS Login compatibility to use `dashicons` display
- Added Gravity Forms compatibility (for reCaptcha form)
- Added to `readme.txt` FAQ “I just updated to version 1.3, what could be causing these child-theme errors?”
- Removed `works-in-progress` folder from theme
- Updated `readme.txt` to note the use and license of SlickNav by Josh Cope
- Updated `readme.txt` to note the use and license of FitVids by Chris Coyier and Paravel
- Updated `readme.txt` to remove FAQ item related to blank menu items; resolved in WordPress core tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #23254
- Updated `style.css` description to emphasize the addition of the SlickNav and FitVids libraries
- Updated `screenshot.png` to better reflect latest release
- Updated `hooks-actions.txt` with new additions
/** ————————————————————————- */
== Version 1.2.5 ==
- Released July 2014
= Code =
- Added new method `OpusPrimusNavigation::pagination` for moving between pages of posts
- Added new method `OpusPrimusNavigation::pagination_wrapped` to provide actions hooks before and after the `pagination` method
- Added `antispambot` email protection to author biography email addresses
- Added sanity checks to ensure widgets are active before rendering sidebars
- Added `opus_primus_defaults.php` to replace `$opus_defaults` class
- Added `opus-primus-ignite.php` to reduce clutter in `functions.php`
- Added `opus_image_link_navigation_output` filter hook to provide access to navigation output
- Added `opus_tagline` to default hidden screen options array
- Adjusted the `OpusPrimusStructures::the_loop` and `OpusPrimusStructures::the_loop_archives` to use the `pagination_wrapped` method
- Changed navigation method from `posts_link` to `pagination`
- Changed single view first year of copyright to published year of post/page in `OpusPrimusStructures::copyright` method
- Deprecated `OpusPrimusDefaults` class (file may be removed in a future release)
- Enqueue custom stylesheet in an update safe location `/wp-content/opus-primus-customs/`
- Enqueue custom JavaScript in an update safe location `/wp-content/opus-primus-customs/`
- Refactored all defaults using true/false to use filtered define statements
- Refactored `OpusPrimusTaglines::tagline_create_boxes` to clarify the parameter usage
- Remove conditional customization enqueue using internal theme folder
- Renamed `opus-ignite.php` to `opus-primus-ignite.php` and moved to theme root
- Renamed `OpusPrimusNavigation::image_nav` to `OpusPrimusNavigation::image_link_navigation`
- Replaced `OpusPrimusStructures::replace_spaces` with `sanitize_html_class`
- Set Customization path and URL CONSTANTS
= CSS =
- Added `Navigation` section and `Pagination Method` sub-section
- Complete refactoring of the `@media` query styles for better responsiveness
- Corrected `select` element to use “max-width” rather than “width”
- Fixed white space on right side of iPhone displays
- Minor adjustments to `img` tag related items
- Monster be gone!? – addressed special case many level menu in sidebar
= Miscellaneous =
- Updated `hooks-filter.txt` documentation to note eight (8) new filters
- Updated `hooks-actions.txt` documentation to note two (2) new actions
- Updated `screenshot.png` to show a bit more of the theme display
/** ————————————————————————- */
== Version 1.2.4 ==
- Released May 2014
= Code =
- Added sanity check to only display comments_link when not in single view or in an archive view
- Added Featured Image Thumbnails to post-format single and archive view templates (except Post-Formats: Image and Gallery)
- Added `opus_primus_theme_version()` call as an accessible text string
- Added new default `number_of_secondary_images` method under Gallery parameters
- Bring the Featured Image Thumbnail back into the index view … can you say “waffle”?
- Change `$output = null` to `$output = ”` in `OpusPrimusPosts::sticky_flag` method
- Corrected typo in `’opus_links_pages_after’` hook
- Corrected modified date/time output to account for scheduled posts being modified earlier than they are posted
- Refactored conditional comments and featured thumbnail checks into the `comments_link` and `show_featured_thumbnail` methods
- Removed `extract` function, escaped attributes, and refactored conditional checks in PullQuotes Stanza
- Use `opus_primus_theme_version` in place of `wp_get_theme` calls
- Use transients to improve performance impact of the `OpusPrimusStructures::copyright` method
= CSS =
- Added Format-Aside Dashicons to Post-Format: Aside posts
- Added Flag Dashicons to Sticky Posts
- Changed Password Protected Dashicons to use the Lock
- Separated the Tagline output class into two different classes
- Updated normalize.css to 3.0.1 (copy and pasted from git.io/normalize)
= Miscellaneous =
- Added filter `opus_primus_theme_version_text`
- Change text domain to match theme slug
- Updated `hooks-actions.txt`
- Updated `hooks-filters.txt` (corrected reference to `opus_first_author_details_text`)
- Updated Opus Primus PullQuotes `readme.txt`
/** ————————————————————————- */
== Version 1.2.3 ==
- Released February 2014
= Code =
- Added more tests
- Added Featured Image thumbnail to standard post-format archive views
- Moved `featured_image` wrapper into OpusPrimusGallery::featured_image method
- Moved `secondary_images` wrapper into OpusPrimusGallery::secondary_images method
- Moved the ellipsis out of the read more link
- Refactored `$output` to use `button` class versus the button element in metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. byline flags
- Removed unused parameter `$more` from `OpusPrimusPosts::excerpt_more_link` method
- Removed `$sep_location` parameter as it was not used in `browser_title` method
- Removed Featured Image thumbnail from index view
- Renamed `OpusPrimusDefaults` methods from `show_*` to `display_*`
- Set `display_page_byline` to true as theme author aesthetic choice
= CSS =
- Added post coda post format classes
- Added `dashicons` dependency to main `Opus-Primus` stylesheet
- Added `button` class to replace the button element styles
- Change to only append to the `cite` tag when it is inside the `blockquote` tag
- Center align Calendar Day table header cells
- Fixed really long Post Titles and Words not wrapping as expected
- General clean-up and removal of excess/over-writing properties
- Prepended Post Byline with matching Post-Format dashicons
- Re-Adjust `ul.nav-menu` and `.nav-menu` to `z-index: 3` for main menu
- Reduced the citation font-size for better aesthetics
= JavaScript =
- Re-format code structures
- Removed `table-stripe` class from specific Calendar elements
= Miscellaneous =
- Updated tags used in `style.css` header blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. to include responsive-layout and fluid-layout
- Updated `readme.txt` to note existence and location of `changelog.txt`
- Updated `readme.txt` copyright notice to clarify copyright years used by individual files.
- Updated Required WordPress version to 3.8 for `dashicons` dependency
/** ————————————————————————- */
== Version 1.2.2 ==
- Released October 2013
= Code =
- Added conditional test rather than print both breadcrumbs (one empty)
- Additional i18n code corrections and enhancements
- Corrected i18n code for EXIF data
- Extracted $post_title management from `post_breadcrumb` method into the `breadcrumb_post_title` method
- Fixed issue with Gallery Post-Format being used when the `gallery` shortcodeShortcode 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. is not used.
- Fixed undefined offset when there is no image found in post
- Reformatted to be closer to (modified) WordPress Coding StandardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.
  May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. – see https://gist.github.com/Cais/8023722
= CSS =
- Reduced all menu related elements with `z-index` property to a value of 1
- Removed `z-index` property from breadcrumb related elements
- Set the breadcrumbs background color to `#ffffff` (white)
= Miscellaneous
- Add documentation to the `first_linked_image` function
- Removed `table-stripe` class from Post-Format: Image tables
- Tested up to WordPress version 3.7
/** ————————————————————————- */
== Version 1.2.1 ==
- Released August 2013
- Removed `translation-ready` tag
/** ————————————————————————- */
== Version 1.2 ==
- Released August 2013
= Code =
- Added display of featured image centered at full size in single standard post format view
- Added full `featured_image` method call to single view of post formats audio, chat, quote, and status
- Added `get_author_description` method in Authors class
- Added filtered `comment_form_required_field_glyph` method in Comments class
- Added many new filters – see http://opusprimus.com/under-the-page/hooks-filters/ or `hooks-filters.txt` for a current list
- Added sanity conditional check to eliminate potential duplicate body classes
- Added `is_single` conditional test before enqueue of Comment Tabs script
- Added post to post navigation in single view
- Added conditional check if not post password required when displaying comments
- Added conditional for showing the page byline details
- Added `display_page_byline` default and set as false
- Changed `the_post_thumbnail` to use parameters which are set in the call to `OpusPrimusImage::featured_image`
- Changed post thumbnail on pages to full size image and align to the center
- Changed comment fields into an unordered list
- Changed `meta-tags` container from `p` to `div` (adjusted CSS as needed)
- Changed `opus_post_byline_details` filter to `opus_post_byline_phrase`
- Check for long post titles in breadcrumbs and trim as needed
- Display comment count in meta details if comments exist and comments are closed
- Fixed call to wrong post navigation function in single view
- Merge `opus-ignite.php` into `functions.php`
- Moved `featured_image` method call into `is_single` conditional in post-format loops
- Removed `featured_image` method call from post-formats link and video loops
- Removed global `$opus_image_meta`; replaced with call to `exif_data` method
- Removed `style.less` related function and action calls
- Removed `restore_image_title`
= CSS =
- Added styles for comment form fields
- Added more specific selector used with `.post.format-link`
- Added more BNS Plugin Integration (BPI) adjustments
- Added styles from compiled `style.less` file (file removed)
- Added `img` elements for captioned images and `wp-smiley` images
- Address both class and id usage for the sidebar search form
- Adjusted widths of comment form elements
- Adjusted CSS to better handle large images with captions in large full-width displays
- Adjusted `table` elements from `max-width: 100%` to `width: 100%` and other minor changes
- Minor tweaks and adjustments
- Sorted out the adaptive layout for screens less than 480px wide
= JavaScript =
- Added more specific selector used with `.post.format-link` when adding `.link-symbol` class
- Added script to create class to display tables with striped rows
- Removed LESS JavaScript library
= Stanzas =
- PullQuotes – Added `pullquotes-readme.txt` file
- PullQuotes – Added left-side placement with new `to` parameter
- Taglines – Added `taglines-readme.txt` file
- THA – Added `tha-readme.txt` file
= Miscellaneous =
- Documentation Updates
- Minor changes to text tense used in `changelog.txt`
- Removed `style.less` file (compiled and merged into `opus-primus.css` file)
- Removed license references related to LESS as all components were removed
- Updated `hooks-actions.txt`
- Updated `hooks-filters.txt`
- Updated `readme.txt` FAQ – What is the difference between how the “Featured Image” is used on a post and how it is used on a page?
- Updated `readme.txt` FAQ – What are Stanzas?
- Updated `readme.txt` FAQ – What happened to the LESS components of the theme?
/** ————————————————————————- */
== Version 1.1.1 ==
- Released March 2013
= Code =
- Added `all_comments_count` and `show_all_comments_count` methods to Comments class to be used in the ‘comments.php’ template when displaying total comments
- General minor code refactorings and improvements
- Moved `comments only tab`, `pingbacks only tab` and `trackbacks only tab` functionality into Comments class methods
- Moved `comments only panel`, `pingbacks only panel` and `trackbacks only panel` functionality into Comments class methods
= CSS =
- Added rounded corners for the comment type tabs and the comments panel
- Added `#d3d3d3` color as default tab background color; active is transparent
- Removed unused element for non-existent ‘comments-toggle’ script
= Miscellaneous =
- Remove $content_width set values from Structures class method `layout_open` and set in ‘functions.php’
- Updated ‘hooks-actions.txt’
/** ————————————————————————- */
== Version 1.1 ==
- Released March 2013
= Code =
- Added `excerpt_more_link` and attached to `excerpt_more` filter
- Added `anchor_title_text` for use with `excerpt_more_link` and permalink in the post meta details
- Added additional list wrapper around each comment type
- Added Breadcrumbs trails to pages and posts
- Added Comment Tabs for each type (Comment, PingbackPingback A pingback is a special type of comment that's created when you link to another blog post, as long as the other blog is set to accept pingbacks. Pingback allows you to notify other bloggers that you have linked to their article on your website. Although there are some minor technical differences, a trackback is basically the same thing as a pingback., and Trackback)
- Created and enqueued ‘opus-primus-comment-tabs.js’
- Created Header class
- Dropped `restore_image_title` filter hook into `media_send_to_editor` as potentially blocking insertion of media
- Fixed comments (only) count output
- Limit width generated by “Full Size Video” JavaScript to a maximum of 1000px
- Refactored Structures class to put `site_title`, `site_description`, and `custom_header_image` into Header class
- Refactored `opus-primus-header` to reflect class/method changes of Structures and Header
= CSS =
- Added classes to `h2`, `ul`, and `li` elements in `OpusPrimusAuthors::author_details`
- Add minor comments styles
- Centered content of Post Format: Video posts.
= Miscellaneous =
- Removed unused style sheet ‘opus-primus-responsive-layout.css’
/** ————————————————————————- */
== Version 1.0.4 ==
- Released March 2013
= Code =
- Added ‘Breadcrumbs’ class
- Fixed problem with wrong loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. method call in ‘archive.php’
- Moved `breadcrumbs` method from ‘Structures’ class to ‘Breadcrumbs’ class
- Removed `hgroup` container from ‘opus-primus-header’
= CSS =
- Added Breadcrumbs section
- Code formatting
/** ————————————————————————- */
== Version 1.0.3 ==
- Released February 2013
= Code =
- Changed the MetaBoxes class to TagLines
- Moved TagLines into its own Stanza as another example of the theme extensibility
- Added `breadcrumbs` method to Structures as a precursor to new features in version 1.1
/** ————————————————————————- */
== Version 1.0.2 ==
- Released February 2013
= Code =
- Fixed ‘search’ template bug when a page is returned in the results
= CSS =
- Started “BNS Plugin Integrations” (aka BPI) – BNS Inline Asides
/** ————————————————————————- */
== Version 1.0.1 ==
- Released February 2013
= Code =
- Added ‘opus_footer_after’ action hook
- Change classes in ‘404.php’ from using underscores to using hyphens
- Created new methods `the_loop_wrapped` and `the_loop_archives_wrapped`
- Modified action hooks to more semantic naming convention: `opus_
  
  _`
- Moved ‘opus_body_bottom’ action hook to immediately before closing body tag
- Replaced `the_loop` method and surrounding code with `the_loop_wrapped`
- Replaced `the_loop_archives` method and surrounding code with `the_loop_archives_wrapped`
- Wrapped ‘opus_modified_post_after’ action hook in conditional making it consistent with ‘opus_modified_post_before’
= CSS =
- Centered top level menu items only – better aesthetics with short page titles
- Added `clear: both;` to ‘img.aligncenter, img.center’ to address Firefox issue when when a Featured Image and a large in post image are too close together.
- Added post coda post format classes
- Fixed really long Post Titles and Words not wrapping as expected
= Miscellaneous =
- Fixed no comments message
- Minor code formatting
- Refactored the ‘hooks-actions.txt’ listing
- Updated ‘theme-version-guidelines.txt’ as taken from http://opusprimus.com/under-the-page/theme-version-guidelines/
- Updated ‘hooks-actions.txt’ as taken from http://opusprimus.com/under-the-page/hooks-actions/
/** ————————————————————————- */
== Version 1.0 ==
- Initial release – February 2013
== Review Tickets ==
- https://themes.trac.wordpress.org/ticket/11106 – Version 1.0 – February 2013
- https://themes.trac.wordpress.org/ticket/11325 – Version 1.0.1 – February 2013
- https://themes.trac.wordpress.org/ticket/11367 – Version 1.0.2 – February 2013
- https://themes.trac.wordpress.org/ticket/11386 – Version 1.0.3 – February 2013
- https://themes.trac.wordpress.org/ticket/11417 – Version 1.0.4 – March 2013
- https://themes.trac.wordpress.org/ticket/11738 – Version 1.1 – March 2013
- https://themes.trac.wordpress.org/ticket/11803 – Version 1.1.1 – March 2013
- https://themes.trac.wordpress.org/ticket/13740 – Version 1.2 – August 2013
- https://themes.trac.wordpress.org/ticket/13740 – Version 1.2.1 – August 2013
- https://themes.trac.wordpress.org/ticket/15017 – Version 1.2.2 – October 2013
- https://themes.trac.wordpress.org/ticket/16874 – Version 1.2.3 – February 2014
- https://themes.trac.wordpress.org/ticket/18889 – Version 1.2.4 – May 2014
- https://themes.trac.wordpress.org/ticket/19955 – Version 1.2.5 – July 2014
- https://themes.trac.wordpress.org/ticket/21772 – Version 1.3 – November 2014
- https://themes.trac.wordpress.org/ticket/23510 – Version 1.3.3 – March 2015
- https://themes.trac.wordpress.org/ticket/23681 – Version 1.3.4 – March 2015
—-

I based the overall layout on the premises put forward in plugin readme files with a couple of optional items such as the expanded licenses section and a list of all past trac tickets for the theme.

I’d be agreeable to adding a header section of sorts (along the lines of the OP example), obviously inserted before my “Copyright” section as noted in the readme contents area.

Excuse the excessive length but linking to the file really doesn’t give the same impact of what a readme.txt file could look like after several versions if/when the changelog is added into it.
- Daedalon 5:21 pm on May 6, 2015
  
  I’d be all for showcasing only a few items of each type in similar future comments, just as many as is enough to illustrate the approach, with the optional link to the full file for those who want to dive deeper.
Tammie 9:42 am on April 30, 2015
This is what we do at Automattic and to me feels the right format: https://themes.trac.wordpress.org/browser/resonar/1.0.3/readme.txt.

A few points:
- Tags are great to have in one place here too. It means you end up with one doc that has all the essential information. Easier to parse and easier for users.
- The change I’d probably make is tested up to. I’d probably say supported.
- Credits could be resources, I don’t mind what you call it.
Dion Hulse 12:55 am on May 4, 2015
I’d suggest dropping the ‘Tested Up to’ or ‘Supported’ fields, but retaining the ‘Requires’.

My reasoning is:
- Themes often keep working (and don’t become obsolete like plugins), there’s no good reason for a theme to break with a WP upgrade
- Updating that metadata will require a new theme release, plugins can just make a quick unreviewed commit, themes are not that simple
- The fields haven’t really been great in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party directory IMHO, Lots of things continue working, but people avoid them as the theme isn’t specifically marked as supported (or you get support requests every month asking “Does this work with 4.2? I don’t think it does because it’s not listed as such”
- If a theme isn’t compatible with a new version of WordPress, or fatals/etc, it should be pulled from the listing, so “tested up to” should really be inferred as being the latest version
I understand that many theme authors who release a new update every month and constantly update the theme to be up to date with WordPress’s features, would love a Tested field to make them stand out from the crowd, but it feels like it’ll just be at a detriment to other not-as-frequently-updated themes which are not necessarily of lesser quality and ultimately provide little benefit to an end-user.

As for other comments about keeping the fields to major releases only, +1, but that kind of happens for plugins already, we have an internal list in the APIs that says “4.1 compatible means 4.1.1 & 4.1.2 too”, there’s never been a requirement nor need to update it to “Tested up to 4.1.2” if you had it listed as 4.1.
- Chip Bennett 7:32 pm on May 4, 2015
  
  If a theme isn’t compatible with a new version of WordPress, or fatals/etc, it should be pulled from the listing, so “tested up to” should really be inferred as being the latest version
  
  How would Themes be “pulled from the listing” without some way of knowing that it isn’t compatible with the current version of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? The best we can hope to do, currently, is hide from the listing any Theme that hasn’t been updated in the past X period of time (currently two years, IIRC).
  
  The biggest roadblock, as you mentioned, is the need for a simple compat-verification documentation (e.g. “Tested up to” in the readme) to go through the entire review process – though updates for approved Themes happen almost immediately.
  
  Perhaps we need some mechanism for Theme developers to update readme.txt in the Theme repo directly?
  - Justin Tadlock 11:11 pm on May 4, 2015
    
    One thing I’ve always wanted to see was a simple select box on the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ site itself for theme/pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party authors to say that something is compatible. The readme file is a poor way of handling this to me.
  - Dion Hulse 11:37 pm on May 4, 2015
    
    How would Themes be “pulled from the listing” without some way of knowing that it isn’t compatible with the current version of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.?
    
    Having a readme line, checkbox, widgetWidget 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., or whatever that says “Hey, my theme is still compatible with WordPress” is silly, that was my whole point.
    Themes remain compatible with WordPress (although not always with the TRT guidelines) for long enough that having to proactively update something seems a waste of time for all involved.
    
    How often do you see a theme that is no longer compatible with WordPress? When that number becomes more than a handful a year, maybe we could consider a compatibility widget for themes (like we have for plugins)..
    
    Otherwise, I’d just prefer to see proactive removals when someone knows somethings wrong with it – “Hey this theme no longer works, can someone suspend it for me?” or “Hey, this theme isn’t compatible with 4.5, can someone suspend it until I’ve got time to fix it next month?”
    
    For reference – I already suspend themes from the directory when I see them start to cause fatals on wp-themes.com, the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ devs get notified about them – It’s rare, but there’s been a few recently that were from 2008. I always shoot the author a friendly email to let them know though.
    
    Perhaps we need some mechanism for Theme developers to update readme.txt in the Theme repo directly?
    
    I’d also say that’s not needed, if the tested-up-to version is the only thing that would require it.. it oughta just be dropped.
    - Chip Bennett 12:26 pm on May 5, 2015
      
      Having a readme line, checkbox, widgetWidget 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., or whatever that says “Hey, my theme is still compatible with WordPress” is silly, that was my whole point.
      
      You’re right. This is a pretty big “win” for the Themes directory, and we should recognize it as such. Sometimes I forget just how far we’ve come in just a few short years.
      
      The biggest potential issue is functions being newly deprecated in a new version of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. – but even that will almost never cause breakage.
      
      I do think that Theme developers will complain (and rightly so, given the user perception that “recently updated” == “better”) if they are unable to highlight that they have tested/verified their Theme against the latest version of core. It is also seen as a sign of a Theme being actively updated/supported by the developer. So, I do think there’s some value in that information.
      
      I like Justin’s idea, though – provide some way for the developer to indicate core support in the Admin area of the Theme’s listing on the directory. A simple checkbox or dropdown select would probably suffice.
Emil Uzelac 8:24 pm on May 10, 2015

@jcastaneda just noticed == Resources == in your original post, while it should be == Credits == instead 🙂
Pingback: WordPress › Theme Review Update for May 11, 2015 « Make.WordPress.Org Updates
Tomas Mackevicius 4:44 pm on May 19, 2015

Is it possible to get validator like there is one for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party readme:

https://wordpress.org/plugins/about/validator/
cavalierlife 3:34 am on June 10, 2016

Though this thread is over a year old, and the ticket https://core.trac.wordpress.org/ticket/22810 began 4 years ago, I hope this is still in the works. I always click the Changelog link in the View Details popup before upgrading any plugins. If changelogs are ever really implemented for themes (I hope so), I hope there will also be a link to the changelog in the View Details popup. Consistency between pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party updates and theme updates would be wonderful.
- Ulrich 3:07 pm on June 10, 2016
  
  At the moment there is unfortunately not much activity as there is no one to lead it. The biggest challange in this project is the coordination between WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. It might get looked at again once the new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party directory has been released.
Pingback: WordPress Theme Standards ⋆ Afzal Multani
Pingback: Upcoming directory changes | World of WordPress
Pingback: Review WordPress Theme – Redy
Pingback: Release note for the Hueman theme v3.4.6 – Press Customizr
Andy Fragen 4:39 pm on November 5, 2018

To have parity with the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party readme.txt file a ‘Requires PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php.’ headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. should also be present. It will be needed to bring themes into the ServeHappy project.
Pingback: Mythic: Version 1.1.0 – Theme Hybrid
Pingback: WordPress Theme Standards - Kafle G

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication