Themeforest Tutorial

Encourages the salesperson to create and market better topics. Purchasers can buy premium topics with some "standards" they are following. It maintains a good reputation and a lead over its competition by marketing WordPress topics that meet specific criteria of excellence. Obviously the same goes for almost all kinds of product that Envato marketplace sellers have, but I think it's fair to say that WordPress topics get the most exposure from ThemeForest critics...and again, that's a good thing for everyone.

WordPress topics could be raised to the highest level, but that doesn't necessarily mean it's difficult or even impossible to approve your topic. By following a few easy procedures, such as standard encoding and license compliance, you can promote your WordPress topics. Therefore, in this tutorial we will go through a check list to build a WordPress topic that can be released and resold on ThemeForest.

Although Tuts+ and ThemeForest are both part of the Envato familiy, I'm not an Envato staff member and this does not represent an offical view of the boys at ThemeForest. For the ThemeForest boys, the importance of the integrity of your codes is crucial: Bad programming knowledge can lead to a weak or harsh refusal.

We will investigate what "soft rejection" and "hard rejection" mean.) You need to keep your codes clear, optimised and in compliance with your own standard of excellence. Although it may be useful for you to have neat and optimised programming, you may be asking yourself what "quality standards" you must adhere to when you develop a topic's infrastructural work.

Put in simple terms, there are five standard you have to watch out for: For HTML norms, CSS norms, JavaScript norms, PHP norms and WordPress topic developing norms. You can read this part of my serial "Making the Perfect WordPress Theme" to learn more about these qualities. Incorporating and adhering to these guidelines while creating your topic will be a big plus for you, and the boys at ThemeForest won't have a problem finding out the coding for your topic.

Your design validations are another important part of the design approvals procedure and part of the set of qualifying criteria you just reviewed above - but creating a standard mark-up doesn't necessarily mean that all pages in your design passed the HTML and CSS validations via the W3C toolkit. You' ll need to test your design in detail with many, many kinds of mail contents and some favorite plug-ins that can print the contents and override the mark-up of your design.

In order to try different mail formats, you can go to WPTest. io, which is described as "a fantastic complete suite of test formats for measuring the health of your plug-ins and themes". It' really a whole bunch of test dates and may seem "too much" to you; but to pass this tough test will quite definitely ensure that your subject is still relevant.

Additionally to WPTest, I suggest a great WordPress plug-in called Monster Widget that, as the name implies, will load all 13 standard Widgets as a "super widget" so you can spend less testin' your theme's side bars. Just like with WordPress plug-ins, you should also test plug-ins that display or modify your WordPress frontend information.

Speed dial plug-ins, embedded videos, community share plug-ins, any kind of side bar plug-ins, and plug-ins that modify or append contents should be tried to provide a better user feel for your topic. Remember that this is not a request from the ThemeForest boys, but it will be a way to get fewer error messages and avoid any disappointment with your topic.

Oh, and one last thing: Don't neglect to review your design with the themes checking plug-in! Have you ever belonged to the concept "plugin area"? Essentially it is the defining of the kind of feature that can (and should) be provided by a WordPress plug-in. Providing plug-in functions to plug-ins is one of the most important (still overlooked) parts of the WordPress topic creation work.

Just think, you run your company website with a WordPress topic, but over the years you won't be enthusiastic about it anymore. They choose to switch to another topic and pass lessons to find a new one. That' s exactly the kind of disappointment that bath topic owners experience - virtually forcing them to use this topic forever.

Built-in "plugin territory" was used to describe the features that should be included in plugs and to avoid this kind of poor experiences. Take your features out of your design and make it available for installation as a seperate plug-in. Fortunately, there is a simple way for you and the user of your theme:

TGM Plugin Activation Libraries. It has been made as part of topics that "recommend" or "require" the user to add extra plug-ins. You can use this libary to get your user to download plug-ins from WordPress.org, a website, or even a zipped archive located in the folder of your design. Visit the TGM Plugin Activation section where I explain how to use TGM Plugin Activation to get more information about it.

Ensure that your artwork is good and "unique" There are many WordPress topics in ThemeForest, and it has begun to seem like there are more than a few "instances" of favorite topic type. An example are "business topics": In ThemeForest, there are literally dozens to a hundred WordPress topics, and things have begun to look the same.

It is ThemeForest's aim to provide clients with different styling options rather than similar ones, so that "uniqueness" is a key element in the authorisation of your theming. Don't miss to divide the articles with your buddies - especially with the ThemeForesters!