Thoughts on potential Child Theme metrics

Published June 21st, 2012 in Thoughts by George Ortiz 0

With the new Auto Tracking function, themes are automagically detected within sites. At first, this was a problem because the detection came from capturing the theme name within the style.css file and in some cases, the name was changed or a child theme was created. This created “duplicates” of themes.

We’ve since launched a new merge feature that allows you to combine the data and manage duplicates. This has worked great since it launched and it got us thinking. There is actually a lot of value in seeing those instances, specifically when it comes to child themes.

While you can still merge the data to combine those instances, we’re thinking of adding another metric concerning child themes or cases where your theme is used as base and the end-user builds on top of your foundation.

This would you allow to see what additional features or design characteristics your themes are eventually developed into and you can use these insights in future development. Also, from a theme options perspective, you can fine-tune your options to exclude or include based off of these insights. It also sheds light on your customer base. Are they designers or site owners? By taking a look at those instances, you can have a much deeper grasp of your products and your customers.

I would love to get your feedback and additional thoughts, so drop a message below.

Share the Love on Twitter Tweet

About the Author