Hi, I’ve just submitted our item:
NOISE – Onepage DJs & Band WordPress Themehttp://themeforest.net/item/noise-onepage-djs-band-wordpress-theme/7035712
We’re in with our WooCommerce theme – Glamo: http://themeforest.net/item/glamo-responsive-wordpress-ecommerce-theme/8980416
And we have same question as @KrownThemes and @tvdathemes – Is the theme eligible or should these features be visible and definitely work in the preview?
Anyway, good luck for all!
I think you can use any WordPress theme (that you feel good with) and use GravityForms for creating form for users to submit content. GF is flexible enough and quite easy to use.
I have a very similar situation when I got the 1-star rating just because the buyer didn’t know how to download the theme from ThemeForest. All I can say it’s not my fault, but ThemeForest’s, because the buyer’s area belongs to TF and they should teach them how to use the website themselves.
I tried to contact with the buyers but no luck.
I think adding rules for reviews or make them available for being reported is good. Also public reviews content + replies also good (but it won’t help with anonymous reviews).
It’s doing what buyers think they need, that’s what sells.
At point of view of buyers, they don’t know how you code the theme, how good is the color scheme, how good is the typography, etc. They just look at the theme and feel good and think it suits for their needs, that’s all. That’s what we should think “quality”. We’re not as good as Apple who made iPhone and taught people how to “tough” or something.
So, iI think we should analyze people needs, then make things that can satisfy those needs and make them good. It will take more time than “quantity”, but then we really make good products.
Smartik saidI prefer dashes for a few reasons:
@fitwp, some rules there are just ridiculous. Why shouldn’t I use underscores to define selectors? I like using underscore, because the whole selector is selectable and I will never change this. Seriously.
An interesting bit of trivia, the original CSS spec did not allow underscores: https://developer.mozilla.org/en-US/docs/Underscores_in_class_and_ID_Names
- They don’t require the shift key to type
- They match the style of the CSS specification (:first-child, text-decoration, etc)
- You can use the |=value operator to match attributes beginning with “value” or “value-”
+1, there’re some discussions about this that might help:http://stackoverflow.com/q/7560813/371240 http://programmers.stackexchange.com/q/141988
By the way, coding standards is not something that forces you to follow. You can have your own style, that’s totally ok. Just keep it consistent, that’s more important.
Stunning! Maybe good for portfolio showcase
If you’re making WordPress theme, you should follow this guide:http://make.wordpress.org/core/handbook/coding-standards/css/
Before building a theme, I built for my own a framework (theme options, meta box, shortcode generator) and that reduced time while working on theme. For my first theme, after design is done, it took me 1 month to convert design to WordPress theme. That’s a simple & clean corporation theme.
Just another note: time for setting up the demo and writing documentation is quite long, too (if you’re truly serious about this).