Hey there, I’m a theme dev who tried all the frameowrks out there. NHP, SMOF, Option Tree, etc. None of them matched what I needed/wanted.
So, I forked NHP and SMOF, and worked with another dev to make Redux Framework 3.0. You might actually find it fits your needs better than any out there.
I made it to comply completely with ThemeForest rules and runs as a plugin.http://wordpress.org/plugins/redux-framework/
So ya, let me know your thoughts.
Here’s the online demo: http://demo.reduxframework.com/wp-admin
I’d have to agree. Time to fill out my demo.
Now with being rejected, can I resubmit?
It’s so funny, but to me each of the top themes look exactly the same. The only items differentiating them is shortcodes, which we have just been told to remove and place in plugins.
As such we built a theme but submitted it without the shortcodes as per the requirements. Shortly thereafter we received a hard rejection without any further details.
My frustration is our theme uses a lot of advanced items underneath. Unlike most themes, it comes with a full LESS compiler, bootstrap 3 (that’s right), and so much customization the user can do most anything they want. Yet, it was rejected.
I see now why many developers aim for the moving hovers and such to “diversify.” I’m fine that my theme may not be unique enough at first glance, but couldn’t the reviewers be more specific? Did they even look at the detailed reviewer notes I sent them?
Still, this was my first try and I’m not giving up. I just wish there were a lot more input. I feel like there’s going to be less room in the marketplace now given the new guidelines.
Oh, what if we kept those things not permisible in a plugin, but then craft our extra things or alterations within our theme? Basically we override the hooks and add the features we want, while having the core shortcode framework in a repo. Is that permissible?
Love the standards, have a few questions:
- I am designing a theme that utilizes some core code from the Roots theme, which utilizes a theme wrapper. Is that an issue? https://github.com/retlehs/roots/blob/master/doc/wrapper.md
- Along those lines, my theme even goes more into depth to utilize modules which override hooks in the roots wrapper. So are you telling me I have to rip all that out and make static template files instead?
- By limiting shortcodes so much you basically put companies like Kriesi and ThemeFusion in a world of hurt because their premium offering IS shortcodes. Come on…
- It seems like the shortcode option not only is to force developers to be more modular, but submit more to GraphicRiver
- With our shortcodes being a plugin, now more people can copy them as they’ll be in the WP directory? Is that the point?
- TimThumb is out, but what about something better like https://github.com/MatthewRuddy/Wordpress-Timthumb-alternative – Main features are Retina ready image preparation. Is that now off limits? (bad bad bad)
- What about features like multiple plugins on the widget page? Enfold has a great box class that does that. Is that now something he must release to all for the same functionality?
That’s all. The rest is good. Clean out the bad!
P.S. The limit, is that for themes being submitted, or themes already in? I’d love to release my theme this next week but if not… it’s going to be quite a bit longer to finish this.