#30: Make better theme test data for display in the theme directory.
--------------------------+------------------------------
Reporter: whyisjake | Owner:
Type: enhancement | Status: new
Priority: low | Component: Themes Directory
Resolution: | Keywords: needs-patch
--------------------------+------------------------------
Comment (by Anderton):
Here is my thoughts in. Personally, I would like to see the themes were
classified by default ”categories”. It should not be confused with the
theme tags, but rather be a marker for what kind test data to be used
(read on).
(Screenshots at the end of the post)
'''Example:'''
- '''1.''' New recommendation for theme developers: Add theme data
classification when submitting a theme. This is used for what type of data
test the theme defaults to.
- '''1.1''' Themes submitted before this, is classified ”Standard” in the
backend (using the ”Standard” test data).
- '''2.''' Theme Classifications is a fixed set of theme data categories.
- '''Standard v1'''
Description: The standard classification (!)
Theme data: The theme units test and all post formats (also sliders as
this will be a standard feature in Twenty Fourteen). *In addition to this,
a ”Data Test chooser” should be accessible for the user with all the other
data tests selectable.
-------
- '''Standard v2'''
Description: The standard classification (!) part 2 (what!?)
Theme data: Same as v1, but with data more like real world use.
-------
- '''Accessibility''' (Note. Themes choosing this classification
should be presented to a secondary theme classification as fallback. This
because it only should be themes allowed to use the ”accessibility-ready”
tag to be classified with this. When the accessibility-ready review is
done and passes, the secondary (used when the theme passed the regular
theme review) classification is disabled.
Description: ”Special” Classification (special as in don’t yet know how,
or if you can set a classification for this subject).
Theme data: Don't yet know what type of test data that should be included,
or if this is even valid).
This is a question that could raised over at Make WordPress Accessible.
But the main purpose here is to the test the theme accessibility. This
EVEN if the theme is not labeled as ”accessibility-ready”. This could
utilize tests (such as WCAG 2.0, things like:
http://www.accesskeys.org/tools/color-contrast.html etc) or simply show a
Accessibility score based on WCAG 2.0 criterias). Also, the user should
have the option to turn all CSS and JavaScript off.
-------
- ”'''Visual/gallery/media”''' (Don’t know what to call it yet).
Description: Themes using ”alternate” post display, such as some photo
themes and Masonry-style themes.
Examples (all in the themes directory): Snaps, Visual, Snapshot
Theme data: Even if most of this type of themes uses the post-thumbnail we
use a set of more ”real world use” like data (skipping stuff like very
long titles, 40 menu items and so on) as the user could check everything
else with the ”Standard” Theme Data. Also higher resolution on original
post image data (covering some themes with full screen views and wide
content width)
-------
- '''RTL'''
Description: A Right to Left classification
Theme Data: Uses the ”Standard” data with RTL enabled. Could be a option
in the ”top menu” also (more about this a bit below)
-------
- '''”P2/front end posting”''' (Don’t know what to call it yet).
Description: Themes with P2 functionality.
Theme Data: As this is a type of theme using ”live” content, we use test
data showcasing the special functionality of this type of theme. It could
have the front end posting forms displayed, but without posting
functionality (this should also be stated).
-------
- '''Minimal'''
Description: Minimal content
Theme Data: No post formats, post-thumb functionality, galleries, photos
or any other feature. Just text content (ipsum no. Project Guteberg,
yes.).
-------
- '''Others:''' BuddyPress, WooCommerce, WP E-commerce etc.
As these type of themes uses plugins, or the plugin just adds
functionality to themes we do not add special theme data for this.
However, when a user is testing a theme tagged with i.e. BuddyPress or
stating in the theme description it’s a WooCommerce (or other) theme, the
user will in some way ”warned” about this when pressing ”preview theme”.
-------
''' 3.''' Add a button/link below ”Preview” or in the description (styled)
with ”Preview on Theme Author Site” (or something like that, but shorter).
When clicking that button, the user will be taken to a static page stating
that the user is leaving WordPress org and *input legal stuff about 3rd
party links* nor can WordPress org not protect against scary mutant
kittens that may or may not be on other sites. Sites like Deviantart does
this what i can recall. Also (not on topic) a more ”plugin”-like theme
page. I know that some personal branding ala premium theme sites gonna
increase the popularity amongst theme developers and users alike.
[[Image(https://dl.dropboxusercontent.com/u/17959832/screenshot-1.jpg)]]
[[Image(https://dl.dropboxusercontent.com/u/17959832/screenshot-3.jpg)]]
'''4.''' *Instead of show the theme preview in a modal (that one does not
always work optimal), we just link to the preview and using a top menu bar
like most ”premium” theme sites do, but better. This top bar could be
include the menu for the data tests, download link, link to the theme
author homepage and a ”back to the theme info” link (and a disable
button). It should’t be in the way or conflict with the theme
functionality.
[[Image(https://dl.dropboxusercontent.com/u/17959832/screenshot-2.jpg)]]
'''5.''' Theme Classifications should not increase the workload for
reviewers or theme authors.
I believe this could really set the standard. Also, it should also ”lure”
more people looking for free WordPress themes. I know people (not fact,
just observation) that don’t use WordPress org for themes because ”the
themes sucks!” solely based on the theme preview.
Note that the ”classifications” (or whatever it should be called) listed
is just examples. It could be less, or it could be more (Video, audio
etc).
I haven’t thought about the actual technical implementation, just the
ideas.
Cheers! And keep up with all the good work everyone!
Screenshot 1 is here
(https://dl.dropboxusercontent.com/u/17959832/screenshot-2.jpg).
Screenshot 2 here
(https://dl.dropboxusercontent.com/u/17959832/screenshot-1.jpg).
And at last Screenshot 3 (nevermind the styling, it’s just concept)
(https://dl.dropboxusercontent.com/u/17959832/screenshot-3.jpg)
--
Ticket URL: <http://meta.trac.wordpress.org/ticket/30#comment:18>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software