Author Archives: Frumph

Frumph 6:22 pm on January 28, 2011  

Agenda for 01/29/2010 WPTRT

IRC Channel #wordpress-themes
#freenode
10am EST. Saturday

Theme Out Of Date –
1. Code the search to not include themes out of date, create new search for out of date themes – big “out of date” marker on the theme page for themes that are past a certain point.
2. Suspension for themes that haven’t updated past a certain point.

Swap out a couple of the featured themes.
Finalize Child Themes on repository guidelines for reviewing. (and recommendations to consider to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devs if any implementation is necessary)
WPTRT Base Theme
SEO Discussion Site vrs SEO Sales site, author uri, theme uri – this one is a given that a theme uri must point to a page specifically for the theme and author uri must point to a developement page for the author if the main author’s page is not a general blog site for the developer.

Anything else anyone want to toss in?

Frumph 9:10 am on January 24, 2011
Tags: , ,   

Discussion – Child Themes on the Repository – Guidelines

1) Parent themes of child themes that are developed need to be made child-theme ready; proper use of where to find files with get_template_part, get_stylesheet_ and get_template_ functions.
2) https://codex.wordpress.org/Child_Themes documentation is applied as part of the theme review process when checking child themes, all information is to be considered good practice and required, with addition to the theme review representation of license information.
3) Parent themes of child themes submitted must have passed the current theme review guidelines for the current revision of WordPress, not if they have passed before, but specifically with the current revision of WordPress.
4) Child themes are reviewed with the parent theme; must pass current theme review guidelines and associated child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/. documentation.
5) Recommendation to use the parent themes repository slug as the prefix to the child theme’s name. ex. easel-highsociety, atahualpa-wired, this is only the name of the theme & directory name of theme in the zip, not where to find the theme; even as found in the https://codex.wordpress.org/Child_Themes being part of the review process, this naming convention will stay a recommendation; however, declared best-practice.
6) Description in the style.css must clearly state that it is a child theme example: “This is a child theme for the Easel theme.” – This is for redundancy of recognition that it is a child theme, even though other things will be noted on the repository that it is a child theme, this is for the wp-admin -> themes page for the end user.

Additional For Developers:
1) It is the responsibility of the developer of child themes to keep their child themes up to date with the current revision of their theme that is updated. If a developer make changes to the parent theme, it is the developers responsibility to keep the child themes updated as well.

Changes, word usage, additional guidelines and protocols, as well as information regarding use of child-theme tag requested as part of this discussion.

#child-theme, #discussion, #guidelines

Frumph 9:10 am on January 21, 2011  

Obsolete – No longer active themes – Discussion

These themes have been processed by the Theme Review Team to be determined to be justifiable to suspend
from the repository for one of the following reasons

    • Splog links – links go to spam blogs
    • invalid license information that is not gpl compatible or font license not found (1) or non-gpl restriction with footer credits
    • not-working theme just not function with latest wordpress
    • missing completely, svn not associated to the post of the theme

Splog Links in theme/author uri or theme uri or SEO seeded or even hardcorded backlinks

https://wordpress.org/extend/themes/bluesky
https://wordpress.org/extend/themes/happy-cyclope
https://wordpress.org/extend/themes/gone-fishing
https://wordpress.org/extend/themes/yb-auto
https://wordpress.org/extend/themes/midnight-blue
https://wordpress.org/extend/themes/the-knife-wp
https://wordpress.org/extend/themes/studiopress
https://wordpress.org/extend/themes/black-on-white-serif
https://wordpress.org/extend/themes/flexi-blue
https://wordpress.org/extend/themes/yb-light
https://wordpress.org/extend/themes/nishita
https://wordpress.org/extend/themes/descartes
https://wordpress.org/extend/themes/chinese-love
https://wordpress.org/extend/themes/simple-blue
https://wordpress.org/extend/themes/styleicious
https://wordpress.org/extend/themes/jas-personal-publisher
https://wordpress.org/extend/themes/rotate-text
https://wordpress.org/extend/themes/diana
https://wordpress.org/extend/themes/citrus-mix
https://wordpress.org/extend/themes/clear-seo-blue-eng
https://wordpress.org/extend/themes/kitten-in-pink
https://wordpress.org/extend/themes/sharp-orange
https://wordpress.org/extend/themes/baltimore-phototheme
https://wordpress.org/extend/themes/citrus-mix
https://wordpress.org/extend/themes/small-business-seo
https://wordpress.org/extend/themes/deepblue
https://wordpress.org/extend/themes/wp-bats-theme
https://wordpress.org/extend/themes/simple-blog-design
https://wordpress.org/extend/themes/simple-blog-design-2
https://wordpress.org/extend/themes/blog-design-studio-newblue
https://wordpress.org/extend/themes/myblogstheme
https://wordpress.org/extend/themes/spanish-translation-us
https://wordpress.org/extend/themes/planetemo
https://wordpress.org/extend/themes/contrast-style
https://wordpress.org/extend/themes/shoot-it

Non-compatible Licenses

https://wordpress.org/extend/themes/jnb-multicolor-theme
https://wordpress.org/extend/themes/superfresh
https://wordpress.org/extend/themes/christmas-1
https://wordpress.org/extend/themes/harvest
https://wordpress.org/extend/themes/medieval
https://wordpress.org/extend/themes/the-lord-of-the-rings

Theme has no svn

https://wordpress.org/extend/themes/thistle1

Unknown – possible copyright infringement on design /maybelist

https://wordpress.org/extend/themes/facebookwb

Broken Theme – needs updating

https://wordpress.org/extend/themes/keke
https://wordpress.org/extend/themes/black-green
https://wordpress.org/extend/themes/modern-blue

The pages we chose to review were based on the furthest updated, the themes are on the last pages found in the repository. There were a total of 120 themes checked, 104 of which were originally written as recommendation of suspension, clearing up the ones that were just no license information and other minor nuances made the list above.

The themes listed above represent only a small fraction of available themes on the repository that are outdated and way out of bounds for the guidelines.

This topic is to discuss the plans as such for obsolete themes that remain in the repository that do not meet even the minimal of guidelines that go against most of our opinions of what the free available themes in the repository should be representing as well as how to handle those.

Beyond this current list of those which are to be suspended, the time allotted to do both the theme reviews and verify older themes in the repository does not make it possible to functionally do both. Some of the review team have brought it up that there should be a time limit for non-updated themes, our general consensus is 2 or 3 major 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 WordPress before suspension for not keeping themes updated. What this means that currently we’re on WordPress 3.0 previous to that was 2.9, 2.8 which is 2, 2.7 being 3 revisions previous, all themes that are prior to 2.7 (or 2.8) should be suspended as being currently obsolete.

Frumph 5:47 pm on January 5, 2011
Tags: Menu Location,   

Discussion on menu locations for theme options.

This post is to discuss the use of add_menu_page and add_submenu_page usage for theme options.

When reviewing themes, the thoughts of usage are in several different camps at the moment and we’re looking for your opinions as well.

The first thought is that the dev and theme team want to strongly push developers to utilize as much of the consistency of the 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. and 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. as possible which means when locating the options for a theme it should be found under the WP-ADMIN -> Appearance section of the menu.

Another thought is that if the theme itself is large enough to warrant using it’s own top level menu option, what would be the criterion of that, how much is enough? could those submenu pages inside the top level (add_menu_page) be necessary to be placed as a top level and not options tabs of some sort inside the theme options page itself.

What are the cons of using a top level?

  • It could be using an menu anchor # that a 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 uses to display it’s menu on, so one or the other will disappear.
  • It’s not conducive to the consistency that some people would like to see the wp-admin steer towards, the commonality of finding options in the appropriate places.

What are the pros of using a top level?

  • Can be described to end users easier? (rough one)
  • Can be used to attach theme-based plugins to, for example a plugin can create a top level submenu item *onto* that top level theme add_menu_page to keep everything nicely bundled together.

In my opinion a theme developer if they have theme options, it should indeed be found in the appearance -> section of the wp-admin; if that top level itself doesn’t have sub menu pages

  • Looking for feedback, opinion’s and idea’s towards finalizing a recommendation, requirement for the theme review process.

#menu-location, #theme-options