+1 If that is TF requirement, so be it. I agree.
BUT , how about doing something that is beneficial for the authors too? With the added requirements for functionality and design ( that, many still look similar even considering the past design requirement announcement – BTW ) and the number of themes available, competition is stronger than ever and the $ authors make is harder to come by. Everything that seems to be done has been to strengthen the marketplace AKA the Envato brand. This is good but Authors are working harder than ever to provided better quality themes and compete for a little space here. Themes move off the front page MUCH more quickly so they go out of focus faster and in turn generate less than they should. Contest have been good but only benefit very few and is a big bang for the marketplace because of increased submissions.
So I say “Yes” add whatever requirement you want. But how about throwing the authors a bone too. How about doing something that generates more $$$ for both TF and authors. Maybe by add a paid support system? Credits or something that we get compensated. I answer tons of questions for the $12-15 I make on a sale. That alone makes it hardly worth the trouble to create and sell here and is the main reason I stepped away submitting themes for a while.
I appreciate TF for providing a quality marketplace to sell our goods. But lets keep in mind that what TF sells is provided by the authors. They make better $, TF will draw more quality authors willing to make some time to create great file for the marketplace. Just a though.
A handshake goes both ways.
Most of the errors you see in the validator are related to CSS3 properties which are not fully supported/validated by W3C . You can still use these properties with your template. TF will not complain about it.
I am fully in favor and have/do code using some CSS3 . I keep in mind that it should degrade gracefully. Maybe , eventually, people that use IE will realize that they are getting a lesser user experience by using a browser that is not able to support standards very well and switch to one that does.
Hopefully the folks at Microsoft will finally “get it” and start making their lame browsers better. There are companies with much less resources and less years of experience that there is no excuse for IE…. same argument with every “new” version… why!? Fix it, move on. CSS3 … use it and don’t look back. My opinion.
Here is a collection of my themes that focus on portfolio style sites:
Yeah.. a little self promotion but many have been used for galleries.
I’m not familiar with the theme you bought but try this:
Also check if the theme uses TimThumb Script… host Gator is notorious for not having it white listed by default and you have to call them to enable it on your domain. Luckily newer themes are starting to use built in features since WP 2 .9 to avoid this.
Next if you contact the author for help, be sure you do it while logged in to TF with the account that you purchased from and email them by clicking their profile. Authors, including myself, use it to check purchase info. hope that will help.
At the foot of all my websites is text link back to my site which says, “website by XYZ ”. I’m not claiming to have designed it (although granted that may be inferred by some), but I have built it, configged the WP to suit them, customised a generic theme, built up all their content, layed out that content, etc – the site has been ‘built’ by me.
ant0 : I apologize if this is how it came out… It was not meant that way and I was speaking to this part of your reply and you asked for thoughts . I think that sometimes I type too much and maybe not as articulate at expressing my point. I was trying to offer scenarios to illustrate this and was not meant to be hostel. Maybe I should have bolded the “IF” or something… reading back, I’m sorry if it came off that way.
“Website by XYZ ” to “Web Services by XYZ ”... Really, that sums up my whole point.
I do appreciate the buyers and the community and I do think that themes are meant to used the way you are using them with the above. Semantics, won’t kill anyone but there really isn’t a clear guideline to this and IMO I think it is important.
@ant0 I understand your workflow and I think it is common and makes sense. You say you built the site… well really you just customized it to suit. If you built the site you wouldn’t have bought a theme to start. Read the “song” analogy a few comments back. If you were to ask Theme Forest if you could sell your version of the theme here… the answer would be definitively no. If you were to set the customized version of the theme on another domain you WOULD be violating the 1 purchase 1-domain purchase agreement. Why… because it is NOT solely your work and cannot be considered an original theme….
What if your client now took your theme that you designed for them, that they paid for, then added some mods and sold it to someone else and said web design by them. They Paid for your work, They altered it enough in there mind that they “think” it now is their creation and now claim ownership and development credit. Just because it seems to be the norm to include a copyright statement at the bottom of a website doesn’t make it right. Put your logo there, Put Web Solutions by YOUR COMPANY … go for it, Just don’t say you WebSite Design by You… cause it’s not true. Maybe semantics but I just think when you start crossing these lines where does it stop. Who says how much of the “song” has to be changed to then consider you as the composer. It is about Intellectual Property. As designers you WILL get burned by this at some point and then elevate the value of it.
Having been on both sides of developing themes and customizing per client, I would say that customizing is only a small part of the whole development. I can take any theme here and spend a few hours in the style sheet and it will look entirely different. It could look like an entirely new theme… but I could and would not consider that my own. The author spend weeks creating it and I can change it completely in a few hours to be unrecognizable. The code base, logic, functionality, option panel etc… more than skin deep.
@modernworldweb actually I am not saying that I do not support people using themes to help their clients or develop solution for them… that is what they are for. I completely support the notion that themes ARE great for designers to use exactly for that.
What I am saying is that IMO finessing a theme doesn’t makes it your creation it just makes it your interpretation or adaptation of the main core of ideas. I am saying that if you do not design it don’t say that you did. I am not talking about a law I am talking about individual integrity to claim what you have not created as your own.
My analogy is with a song… there are many artists that preform a cover versions of songs … they are even re-sold with royalties of course. It doesn’t matter if they made it better or not they still didn’t write the song and cannot claim that they did. So Designers, theme purchases, novice or not, should at least recognize the value of intellectual property. This is really the core of the concern. Intellectual property is something everyone in the creative field should strive to protect, value, and at minimum at least recognize. Once we start moving into stretching the boundaries of what can be claimed as your own work and lowing our expectations of personal integrity among creatives is when we start devaluing what we do as a whole. I think that anyone that is a creative can at least respect that.
I am not beating the person who did this I am simply opening a discussion for a topic that I think is turning out to be a nice thread.
Nice points all around. I can agree with most of them to some degree but not entirely.
@VagrantRadio: I fully get that buyers will use templates as a solution for clients and sell them up. That is typically the intent and it is a solid work flow. It is claiming other’s work as their own I have a problem with.
@epicura your points here on theme dis-closer are spot on. There is no reason to hide the fact that the solution is built on a templates framework… which will save them $xxxx.xx. I like all your points on this. Implementing solutions for clients is something we do as designers every day. We offer visual, functional solution that address the clients needs. It doesn’t matter if it is a logo design, website, or other. It’s the claiming that it is their own that is ethically wrong. Their branding statement could be worded differently to not imply that they designed the theme and still be completely respectable.
Anyway… thanks for everyone’s input.
I’ve had this happen a lot – doesn’t really bug me personally since I’m not in direct competition for their client’s business and, frankly, anyone who has a desperate need to use a template as one of their defining portfolio pieces probably doesn’t have a competitive portfolio to begin with. That said, I publish my own templates to empower designers – so if part of that means making them look like a rock star in front of their own group of clients, then more power to em’! The good news is that if they want to duplicate the same quality of work, they’ll have to come back to you for another product
I don’t have any problem at all with people using template as solutions for their clients. That is what they are available for. A great head start or complete solution. But I just am not crazy about when/why a designer would buy a theme add their clients logo and then put the “© Designed By Their Company”.
Just because you are singing someone else’s song doesn’t mean you wrote the song… no matter if you change the tune a little or a lot. It is just fundamentally wrong regardless if it effects you as a template author or not. It is Just not right for anyone in the design field to accept it when people claim someone elses’ work as their own. As Designers I would think they should know better. It lowers the standard of professionalism as a whole in our field and will effect you somehow… maybe not directly right now but by loosely guarding copyright and intellectual property, it will slowly chip away at the value of our work as a whole. These are things that designers should take a hard stance on. This is our livelihood and should not be brushed off lightly. Our Ideas and implementation are what people are buying and what we are essentially selling. We should NOT sell ourselves short by relinquishing this basic courtesy of proper credit for our hard work.
Their are a few issue in FireFox Mac that you will have to fix. I haven’t poked around too much but right away I see this: The “contact” falls under and out of the nav bar, strange link under your 3 column section…
I may even tighten-up the page descriptions for each sections maybe a little smaller. Don’t be discouraged everyone has seen that rejection email. Usually it just means to step back take an objective look with fresh(er) eyes and then refine the details.