This document outlines requirements for submitting WordPress themes to TheWebLab. It discusses having a team with skills in design, development, and familiarity with tools like Photoshop. Theme submissions must follow best practices for spacing, color contrast, typography, and be pixel-perfect, responsive, and include documentation. Themes must properly implement WordPress features and APIs, be secure and optimized, and pass unit tests. PHP, HTML/CSS, and JavaScript quality is important. Themes should incorporate plugins and move functionality there instead of the theme.

1. WORDPRESS THEME SUBMISSION
REQUIREMENT
Enayet Husain Rajib
CEO & Founder, TheWebLab

2. Positively Emotionally Attached
Believe in yourself.

4. Better if you have a team
The no of members in the team
The skills you have in your team

5. Who can design
Who is familiar with photoshop and its tools.
Who have the idea about latest web trends

6. THREE RULES
6
1. Spacing, the use of white space
2. Color contrast
3. Typography (Very important!)

7. If your psd gets accepted. Great !
Even if your psd gets rejected but you are confident
with the design, you can try developing the html
template and submit

8. Pixel perfect psd to css/html
Perfectly responsive preferred
with Bootstrap
Add/apply css3/jQuery
animation/effects where
applicable
Clean and commented code
A documentation
theweblabltd.com/Doc.zip
FRONT END
DEVELOPER

10. Now your design gets accepted,
lets develop the WORDPRESS theme!
Next slides is for those who are familiar
with PHP and Wordpress

11. Q: Why this requirement?
A: Just to maintain a minimum standard of quality

12. WordPress Core API
WordPress Features
WordPress Unit Tests
WordPress Assets
Security
PHP Quality
HTML/CSS Quality
JavaScript Quality

13. 1. No deprecated template tags allowed
2. Use “Theme-Check” plugin to eliminate WARNING,
REQUIRED, RECOMMENDED, and INFO notices as much
as possible.
3. The following functions are mandatory:
wp_title(), wp_head(), wp_footer(), post_class(),
body_class()

14. 4. custom template files are required to be called using
get_template_part() or locate_template()
5. File naming and structure must follow WordPress best
practices. Say, don’t use custom-header.php, rather name it
like header-about.php
6. WordPress core features need to be incorporated.

15. 6. Modification of filters in wptexturize(), wpautop is not
allowed.
7. Default WordPress CSS classes must be covered in the
stylesheet, since this is expected native behavior.
8. Use a unique prefix for all function names, classes,
hooks, public/global variables, and database entries to avoid
conflict issues with plugins and other themes.

16. WORDPRESS FEATURES
The theme needs to be widget ready in all advertised
locations.
Use of Timthumb is not allowed.
Themes are required to provide child theme support.

17. wp_nav_menu() must be included in at least one theme
location for easy menu management.
All of WordPress' default widgets should be styled/display
properly in all widgetized areas.
index.php should be reserved for standard blog
"latest posts" view.

18. WordPress Theme Submission Requirements
https://help.market.envato.com/hc/en-us/articles/202822450-WordPress-Theme-
Submission-Requirements
Q A for WordPress Phase 1 Submission Requirements
https://help.market.envato.com/hc/en-us/articles/202501494-Q-A-for-WordPress-Phase-
1-Submission-Requirements

21. WORDPRESS UNIT TEST
Its basically testing and confirming all default worpdress
features are working fine
http://codex.wordpress.org/Theme_Unit_Test

22. WORDPRESS ASSETS
wp_enqueue_style() and wp_enqueue_script() must be
used to enqueue all stylesheets and JavaScript
Authors are not allowed to deregister the default version
of jQuery and load another one.

23. PLUGINS
Recommended and required plugins must be included via
the TGM Plugin Activation class

24. PHP
Set WP_DEBUG to TRUE and check for any PHP notices,
warnings, or errors
Don’t access wp database directly. Use $wpdb and its
methods
Tabs must be used for indentation
https://make.wordpress.org/core/handbook/coding-
standards/php/

25. HTML/CSS
HTML needs to be W3C validated
No inline styles
IDs and classes should follow a naming convention and
needs to be appropriate and human readable.

26. JAVASCRIPT
All js code should be placed in external files whenever
possible.
It shouldn't raise any errors or notices.
jshint.com

27. PHASE TWO
Move functionality into plugins instead of themes
Shortcodes are permitted but in plugins

28. http://www.thethemelab.com/FlatOneWP/Documentation/

30. facebook.com/theweblab
enayet@theweblabltd.com
LearnTodayWithMe.COM
TheWebLabLtd.COM

31. http://www.slideshare.net/theweblab/