I’ve sent you a portfolio link via the message form. Unfortunately, some of the items are either “work in progress” or bound by NDAs, so I couldn’t post the link publicly. Thank you and hope you can take that in consideration.
You can sell whichever item you wish on any other market AS LONG AS IT IS NOT in your ThemeForest portfolio. Your ThemeForest reviewed and approved items fall under the exclusivity terms and only them.
You can of course sell cross-platform (PSD, HTML, WP, Drupal, Joomla) variations of them. You can sell the HTML, WP here and the PSD on your site or another market.
Just thought I’d push this up a bit in case someone still needs it. Cheers!
The thing with “when the designer is done, he’s done” always gets me laughing, particularly as you are basically talking about a team.
Getting a few things straight:
1.. A theme without a solid design won’t sell. Like it or not, a good image will always sell better. It’s the first contact buyers have with your product. Further more, I know some buyers have the habit of ignoring products because the product’s cover image is crap. So no matter how good your coder is, without your designer, you’ll be selling on CodeCanyon at best.
2. When one theme is out in the wild you need a new one. Who’s going to work on that new gorgeous high quality design? Your coder? No. Your designer.
The designer MIGHT work “less” on the first project than your developer, but on each of the following projects/themes, your designer won’t reuse and rehash much of his work if he wants to do something nice and creative. But no-one is forcing your developer not to reuse code from the previous projects, admin settings, shortcodes etc. So there you go, your developer starts to work less on creating and more or re-using and improving when such is the case. And in the end, things balance themselves out.
Things are simple, if you start this as a SMALL TEAM and want to keep it together, make it fair and split it 3 ways. Otherwise, if you think your designer is not worth the split, buy designs, pay designers per project, but forget about a “signature look”.
Oh, and one more thing… I know designers are fully capable of coming up with creative ideas and concepts. I also know there are SO many successful authors that are just devs or designers and some outsource the support. I for one wouldn’t hurry to say the designer or the dev are the ones that might not deserve the 1/3 cut. A solid design/dev team can work miracles even without a “project manager/support guy”.
Just be fair.
I’ve always found nice inspiration in the user-submitted color palettes on ColourLovers. Might be a nice place to explore.
@acosmin Hey man, thanks a lot for your input. Even though, as you noticed, didn’t fit the profile, it gave me a workaround idea for the particular case I’m struggling with. Basically, I’ll just drop the whole UL/LI idea and just use DIVs with or without a wrapper. If wrapped they act in a certain way, if not.. that’s it. Long time no talk, btw… since the Blogsessive days. Hope you’re doing well.
@Jaynesh Indeed that’s a good solution, but when you need to also add values to those list items and consider people might use commas in the skill names for whatever reason (need a less common character to explode by) and so on.. might take a wrong turn. But, for simple listing that could indeed be a better approach. Thank you for the input!
i have use some photos from stockphoto (which i have purchased it) for demo (only for my online demo, for release version i have excluded it already), do you think that why my item was rejected by approver?!
100% NO. If they are only available in the DEMO and not in the package, and you have purchased them, then you don’t need to worry.
What works well for this design is the slider, which has a unified feeling. But as Bianca said, your overall design lacks unity. Using that tab look for section titles… the arrows rounded on all corners but without space between them and the bottom line of the headline…
The footer is pretty unorganized and looks amateurish and unstyled, as if a bunch of widgets have been thrown there without proper styling.
There’s also a general lack of unity in typography and font sizes, color, weights.
The design has promise and while the functionality might be there, it still needs a lot of polish. Which you should do, cause otherwise you’d have worked for nothing and even if the theme would have been approved for sale, it would lack sales because of this unpolished look. Which would turn out to be a waste of your creative time.
I thought of that too, but that would add too much confusion in user’s head. He’d have two different shortcodes [skills] and [skill] that do the same thing (when using the same arguments), output the same thing, but under different circumstances they function like parent-child…
I don’t think it would be a safe approach. Particularly if shortcode names are similar…
Logic dictates that if shortcodes are parsed in a single traverse from top to bottom nest, there could be a way to identify the parent from within a child, since the parent has already been parsed… just can’t figure out how…