Looking at it, it does what Owl would do. It has 3 slides that each contain a set of elements.
In your case, you’d code each slide with 2 elements, or 4 or whatever, placed in rows on top of each other and with Owl’s settings you can choose how many slides/columns to display side by side with breaking points for responsiveness.
You can choose to display only one column on mobile and thus have more nav dots. 3 Columns/slides on tables with fewer dots and all columns on full sized desktops with no dots.
Owl is pretty flexible that way and from my own experience, a tad more stable on mobile that BX which happens to freeze from time to time.
Why don’t you code the items in columns having each slide(column) hold 2 items one above the other? In this case both Owl Carousel and BX Slider would do the job.
Not sure if you’re aware of it, thought I’d make sure by saying it.
If you place any of the items you have in your TF portfolio on public repo’s – or anywhere with public access to copy for that matter – you’re basically breaking your exclusivity agreement with Envato, so tread carefully.
As onioneye and WebSmacker stated before, the weekend saved (in a big way) an otherwise lousy week. Don’t know how it happened, but I don’t remember having such an active weekend this year at least.
You can use a decent variety of HTML tags for your item’s description. If you plan on using images you’ll have to upload them to your own server and link to them in an <IMG> tag. That’s the technical aspect. Other than that, just use your creativity.
While the update and the intentions behind it are truly great, I can’t shake the feeling it might have really negatively influenced our sales too. There’s something weird going on.
From where I stand, a documentation needs to have these 5 major sections:
- Product info: version, release date, update date, compatibilities if case;
- Installation information and requirements;
- Setup – Different from installation, this might go into detail on how to adjust a color scheme, or setup a contact form, etc;
- Product components: a detailed view of products elements: headers, sliders, icons, porfolios etc;
- Credits to included script authors: While some authors might not require this, it’s still good as you also help your buyer to locate the documentation and new versions of the scripts in the future. Will also pass some of the support requests from you to the script’s author.
What’s interesting is that CodeCanyon buyers seem much more relaxed and objective toward support.
It kinda make sense. CC buyers work with scripts and in a lot of cases they are more savvy, while between the TF buyers we see a lot of DIY people for whom the web knowledge is limited to Notepad, Save, Upload… “Missing stylesheet”, or people with little knowledge that are just starting a web-freelance business for a quick buck in a shaky economy. Not that not having this knowledge is a bad thing, we can’t all be good at everything. What I mean is that the targeted buyers come from a different spectrum.
Don’t dispair, our latest template went through a few rounds of soft-rejects too. Most rounds were actually things that were there since the first submission and the reviewer only mentioned a few. So we had to keep going back and forth to get it live, but we did in the end.
Have a bit more patience, I know it can be frustrating, but consider this: Just as we make our own mistakes that we get rejected for, reviewers are humans too and can overlook things, or be too zealous. This is really not a bad template, definitely not one to give up on.
From where I stand, better spacing within each post box would be ideal, on all sides. Titles are too close to the excerpt text, which messes the visual hierarchy a bit.
On post pages, the blockquote could use some better styling and fonts. Looks a bit out of place. Also consider that on higher resolutions (basically any desktop these days), your paragraph lines are pretty long and that creates readability issues. You could try a 50px on .post_content and getting it to 30px on mobile combined with a max-width: 750px (or close) on .post_excerpt, #author_vcard, #comments & #respond. That might do the trick. Give it a try and see how you like it.
And I must say I’m not a big fan of the background photo, don’t really see its purpose in a template that’s already image-heavy. It steals away the shine of the post images. But this can be a very subjective opinion so don’t take my word for it.
Good luck in getting it live!
PS: Don’t move onto WP if you can’t get the HTML approved. The review standards are even higher there.
Hopefully Envato could also add a dropdown of all the items from the same author to the header (just like what other people to), so that people don’t need to make their own headers and all the buyers will get same user experience.
Chances for that to happen are really slim. In theory (and most time in practice too) you should not point to other products while trying to sell one product on your landing page. This should only be done post-sale (People who bought X also bought Y). If your potential buyer has almost made a decision, there’s a chance you make him question it and there’s no guarantee he’ll buy a product that’s also yours after. Also, it diverts attention from the main action: Green “Buy Now” button and that’s not a good thing obviously.