But what’s the point in making a plugin if this is theme related plugin only (let’s say we are dealing with a niche specific theme)? If users switch to another theme they will have to:
(a) re-style it to fit the other theme design
(b) manage copyrights somehow
Not all theme users are familiar with CSS.
I’ve read Tadlock’s article relating to Custom Post Types and Custom Taxonomies belong to a plugin and kinda agree with it. I mean, everything he wrote is just correct.
However, does it mean that if certain theme is using 8 or more Custom Post Types, authors will have to provide 8+ different plugins as well? What if 3 of these already exist in WP’s public plugin’s repository? Should we build our product around existing plugins because they have been accepted by most of the people? But what if we need to modify a couple of things to make them fit the need of our product/theme?
Moreover, theme buyers expect to have an out-of-the-box solution that includes demo site too – at least that’s my experience in the past couple of years. Does it mean that from now on theme authors should split theme’s demo data? How the hell is this going to look like?!? It smell like a big confusion at both author’s and user’s side.
Just my 2 cents… It seems like there’s a lot of work put into this theme – don’t get me wrong, I think even too much. The essence of this theme is diminished. If this is a business theme – keep the focus on business. Main navigation is kinda out of importance. Should be a bit bigger and bolder. “Social icons” in page header and footer…why? Keep the header as clean as possible or at least don’t let them pop out so badly. Sticky header is OK but unless scrolled there’s no clear cut between navigation and content. Keep the layout consistent! There’s too much difference (visually) between various pages. Icons hover effect (seen on About Us page) is kinda glitchy. Other icons hover effect is not quite “representative”. Definitely find better photos. Have you seen your Search results page? Try to enter Lorem and the results are showing shortcodes instead of text. Separators should have consistency too…some of them are black (or fat) while others look more or less normal. Keep an eye on details.
What an old, grumpy and lame bag of bones I am! Yesterday I forgot to say HAPPY BIRTHDAY Envato!!! Thanks a ton for making my life (and the life of my family) great, I wish all the health and luck of this world for all the great people working at Envato! Truly and honestly you are my heroes for over 5 years, don’t ever stop doing it!
Get married and have a kid. One, two, three, four, five, etc. Kids are the biggest happiness you’ll ever feel in your life. Right after kids are your friends. And a Saturday rasta bong with them (of course after kids are asleep). I forgot to mention my wife but the fun with her usually takes another direction.
Your HTML is not quite “reliable”. I have found many of SUCH examples ... it looks like there’s some issue with the_content(). Try to use margins when separating two different font-families!
By me, “Raleway” and “Georgia” combo doesn’t get along at all. Get rid of serif and stick to Raleway, it’ll bring more consistency.
Next, add more content to theme’s demo site…. where are videos, galleries, shortcodes? Find more attractive photos too.
CONTINUE READING link is so BIG and far away from the text summary, it doesn’t make any sense.
Maybe I’m wrong but it looks like that countdown info is of greater importance than anything else on Under Construction page. What one would expect to see (by the order of importance):
a) What is this all about? It’s an Under Construction page!
b) Thanks for understanding
c) When the site will be back alive?
d) our social profiles
Information presentation belongs to design, of course, and you’ll have to figure it out by yourself. Keep things as simple as possible.
Regardless UI, I think the problem is with TF not following WordPress upgrades fast enough. Yeap, WP 3 .2 is still fresh but users go for it as soon as that upgrade notice is visible in Dashboard.
WP 3 .2. brings new jQuery (1.6) as well and some things have been changed here as well. Heads up for syntax errors!
I guess ‘empty’ will not work. Did you try ‘isset’ instead? If not working, comparing it with an empty string ( if( $_POST[ ‘var_name’ ] != ’’ ) ) should work.