Thanks everyone for your patience (and the entertaining GIFs)! Apologies for the additional delay while we combed through the final details, but as promised we’ve got a thorough response for you all on the issues at hand.
I’ve opened a new thread on it here, so I’m going to lock this one down to start the conversation fresh.
As many of you will probably know there’s been a few active threads lately around the marketing and promotion of multi-purpose themes and the use of multiple demos on ThemeForest.
After thorough evaluation and internal review, we’ve written up an in-depth article to clarify our current stance on these topics and issues. Check out the blog post here.
Thanks again for your ongoing patience during the past few weeks and over the holiday. Hopefully this addresses most of your concerns, as well as outlines some next steps for moving the issue forward in a positive way.
As some of you may have noticed, we just added a new “Top New Files” menu link as well as a “Browse Top New Items” button on the homepage underneath the search bar.
Powered by our faceted search system, it’s a new way to showcase of the best-selling items published within the last month, highlighting quality content in a way that nicely balances both freshness and popularity.
Read more about it on the Market Blog, and enjoy!
We’ve done some more looking into the custom CMS question. Here’s an update with some additional clarification:Site Templates with custom CMS functionality will not be permitted in the HTML Site Templates category, and we will be creating a new ThemeForest > CMS Themes > Custom subcategory where these should be submitted. In the meantime, you can submit these items to the ThemeForest > CMS Themes > Miscellaneous category.
- A static HTML version of these custom CMS themes may still be submitted as a standalone item to HTML site templates, just as authors can create an HTML version of a WordPress item (or vice versa). You may of course cross-link between the two items.
- General, open-ended CMS utilities and frameworks should be submitted to CodeCanyon.
Again, we’ll be reaching out to a few authors we’ve identified with items that may need to be recategorized in this way. If you have items of your own or notice any others that may need to be moved in this way, please contact me privately via my profile or let us know through support and we can help expedite this process as quickly and smoothly as possible.
@Grozav when your item comes through the queue, the reviewer will be able to move it to the appropriate category if needed.
Hey everyone, no need to bump Rest assured Growth and Quality teams are working together to assess this topic very thoroughly.
Coming to the end of this week now, I wanted to give you all an update on what we’re doing and where we’re at so far. This is a massively complex issue touching on everything from theme “bundle” policy, to niche themes, multi-purpose themes, marketing and promotion of items, categorization, pricing, plugins, opportunities for exposure, and much more. We’re in the midst of lots of discussion and review of existing and recent items, researching and evaluating the issue from all angles, and ultimately working to come up with some concrete steps we can bring to the community for establishing better definitions and guidelines around themes here and improving general policy.
To be clear, I am not by any means suggesting that some sweeping change is (or is not) on it’s way. What we’re aiming for here and now is to give clarity to current policy, share our views on the concerns you all have raised, and present some next steps. I’ll circle back next week, and continue to keep my eye on this thread in the meantime.
Thanks everyone for your patience while we’ve been reviewing existing items and discussing this internally. To clarify, the initial flag was raised around how the emerging HTML template + page builder feature fit into the market compared to generic HTML generators or custom CMS functionality, and we simply wanted to pause and clarify this issue before allowing any more of these items to be submitted to the HTML site template category. Apologies for any confusion or concern in the meantime.
As most of you know, in order to customize an HTML template typically an end user would have to dig through the documentation to find sample code blocks, or find the portion of a particular demo template file that contains the element/block they need, and copy/paste from the source code into a custom page. While certainly doable, this can require additional time and expertise. What we’re seeing with the HTML page builders authors have created here is essentially a tool/interface to streamline the above process, and help end users piece together and customize the elements and blocks of the template content in a much more effective, time saving, and user friendly way.
In this way, the HTML template and page builder are very tightly integrated and have to be developed in a compatible way. Thus, in general we see the page builder as an included feature of the HTML site template item, simply providing an enhanced template customization experience for buyers. To be clear, this is fundamentally different to a custom content management system (CMS).
Here’s a summary of what we’ve found, and some clearer guidelines moving forward:
HTML site templates must always include cohesive pre-made/static page templates, complete with purposeful layouts & styling.
- While a page builder feature may be included, the actual HTML site template must be able to fully function on its own without it. In other words, the item must contain actual HTML template(s), not just a generic builder.
- All of the blocks and elements available in the page builder must come from an included page template/design.
- Open-ended page builder / HTML generator utilities or frameworks should be submitted to CodeCanyon
If an HTML site template has been built to work with a specific page builder and includes that page builder functionality to assist with template customization, it will continue to be accepted as a regular HTML site template, as it is currently.
- For example, such as this item.
- The included page builder feature will be taken into consideration when pricing the template within the general category pricing range, just as any other feature/functionality would (e.g. such as an integrated slider, etc.).
- It must be made clear in the item description if the page builder functionality is included as part of the item download, or whether it is only accessible as an online/hosted tool (e.g. alongside of online documentation / support forum registration).
- Making it available in the item download for offline use is strongly encouraged, but we understand that it may be implemented using some server side code/technology that could otherwise be difficult for general buyers to use on their own.
- If hosted only, please be aware that it is your responsibility to maintain working access to the page builder feature, and should it become unavailable your item may be temporarily disabled as a result. You must also make sure reviewers are able to access the tool at all times as well.
We will be reaching out to a few authors with items that may need to be updated according to these clarifications. If you have items of your own or notice any others that may need to be updated in this way, please contact me privately via my profile or let us know through support and we can help expedite this process as quickly and smoothly as possible.
Ah I believe KingDog was referring to having a built-in feature, which is on the wish list but not currently available. But yes, the current FAQ is correct. If you need assistance with upgrading a license, you can contact support and they will be able to help you. No special privilege required, but these are handled manually on an individual basis.
Hey, what about new official answers?
Hey everyone, apologies for the seeming silent treatment—we’re in the midst of some internal review and discussion here. This is a complex topic with many careful considerations, and we’re working to have a more complete response later this week. We appreciate your patience in the meantime