[theme-reviewers] Removing core features
Bryan Hadaway
bhadaway at gmail.com
Thu May 23 00:16:34 UTC 2013
Agreed. My personal philosophy is everything off by default so they have a
palette to work with, then they can simply check a box to turn a feature on
as needed. I also agree that making things as simple as possible is key,
which is why a companion plugin is most definitely a bad idea in those
terms.
I have exhaustive customer support experience (years and thousands of
customers now from all around the world in every imaginable demographic and
plenty of war wounds to account for it) and can always predict the
pitfalls. I can already guarantee this would lead to this scenario over and
over and over again (regardless of how much documentation is written):
*Customer*: "*Umm, this theme doesn't have any of the options you promised,
I feel a little mislead...*"
*Me*: "*Did you make sure to install the companion plugin as instructed?
This is what houses all the features, please read... [providing doc link]*"
*Customer*: "*I have to install a plugin?*"
I want my themes to be as self-contained, easy to use and friendly as
possible because that's what the customer wants, and expects. Too many
steps, too many moving parts is bad business. And considering that most
free users are just as demanding as paying customers, they pretty much have
the exact same expectations and attitudes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130522/b1db45f6/attachment.html>
More information about the theme-reviewers
mailing list