Below, you can find some of less frequent, project specific reject reasons. Look around to see what to expect from reviewers.
- Keyword stuffing titles is not permitted, you can use tags for that.
- More info - https://help.market.envato.com/hc/en-us/articles/203039204-Tips-for-Excellent-Titles-Descriptions-and-Tags
- Would it be possible to get more out-of-the-box look here?
- This is bit crowded:
- A search UI should be improved, it’s bit confusing:
- A green button is more important here, therefore it should be first and read more second, it just makes better
- sense: http://envato.d.pr/upME9/3oMiY76P
- Middle page feels a bit crowded:
- Not sure why the logo is in this area?
- Add more padding please:
- Align the content vertically:
- Color contrast should be improved:
- Not enough of space:
- Align all items equally:
- Pages like this feel bland:
- Test how your theme design breakpoints across desktop, mobile, and tablet: http://design.google.com/resizer
- By default your theme doesn’t look presentable, this is what I get: http://envato.d.pr/6Cd0K/5R3qYGXw
- No comments, http://envato.d.pr/oivXh/8GlEDwBw
- Fatal error on category and author archive, http://envato.d.pr/q4IhV/FWOBkfRU
- Tables require proper styling: http://envato.d.pr/Ouilr
- Open mobile menu requires proper styling: http://envato.d.pr/bTTig
- I found validation errors with the Theme Check plugin. Don’t forget to run Theme Check as well
- https://wordpress.org/plugins/theme-check/ http://envato.d.pr/9MSTp
- ‘ct’ is not an appropriate prefix. Please use a unique prefix for all function names, custom images sizes,
- classes, constants, hooks, public/global variables, and database entries to avoid conflict issues with plugins
and other themes. Two characters is not enough. Ref: http://themereview.co/prefix-all-the-things/
- Mobile styling needs attention/improvement in some areas. Please check/test your pages carefully and resolve all
- issues. example: http://envato.d.pr/yhAR/2y1PckFF and more.
- Your theme is pretty broken upon activation, even after plugins are installed - http://envato.d.pr/6BpU/4NJWxhFz
- How to test the blog/posts layout/functionality - Import the Theme Unit Test
- [http://codex.wordpress.org/Theme_Unit_Test] file and make sure that:
- Posts display correctly, with no apparent visual problems or errors.
- Posts display in correct order.
- Page navigation displays and works correctly.
- As “sticky posts” are a core feature, the theme should style and display them appropriately.
- Lack of body text should not adversely impact the layout.
- Theme must incorporate both the “Tag” and the “Category” taxonomies in some manner.
- Floats are cleared properly for floated element (thumbnail image) at the end of the post content.
Reference link: https://wpthemetestdata.wordpress.com/
- Make sure all the WP default widgets display properly in all widgetized areas. You can check with monster
- widgets plugin.
- Please use a unique prefix (preferably the theme name or framework name) for all function names, custom images
- sizes, classes, hooks, public/global variables, and database entries to avoid conflict issues with plugins and other
themes. For example, themename_ OR frameworkname_.
- Read more at http://themereview.co/prefix-all-the-things/
- You can still be using frameworkname_ if you are using a framework while using themename_ for your themes.
example(s) from your code and there are more:
- This http://envato.d.pr/1dm83/3rnqpcgj lead to this http://envato.d.pr/CBsQ/zqoO93Vq and
- This page http://envato.d.pr/cPAF/WQDh9NRI is not necessary as you can easily write it down in the documentation.
- Theme should work out of the box http://envato.d.pr/2vYK/1PyYwZGI
- You should avoid and not to hardcode custom body_class(). Main reason for this is being able to remove the class
- when needed i.e. child themes. What you can do - https://gist.github.com/kailoon/d4d22c9204909dff21eb
- The localization file should be in English and delivered as .POT file. .POT will contain all translation strings.
- .POT file name should match the themes-slug.
Theme can include an actual translation files, but it should not add the en_US.mo or en_US.po because English
- Directory path should be get_template_directory() and not dirname( FILE ).
- Don’t leave unused code fragments as comments in the code. Please check all your files.
- Please use a unique prefix for all function names, custom images sizes, classes, CONSTANTS, hooks,
- public/global variables, and database entries to avoid conflict issues with plugins and other themes. For example,
themename_ OR frameworkname_
- Read more at http://themereview.co/prefix-all-the-things/
- You can have frameworkname_ if you are using a framework while using themename_ for your themes.
- It’s a very poor practice to deregister WordPress’ built-in jQuery and load another specific version.
Use the jQuery noConflict mode to avoid issues —
- Broken logo:
- Input placeholders will increase the UX:
- Icons are a bit crowded and not prominent enough:
- Increase the spacing:
- Rename to “Latest” Blog:
- Not sure what the arrow was for and line-height needs to be increased:
- Make the space in between more consistent:
- The typographic scale needs balancing http://spencermortensen.com/articles/typographic-scale/
- It doesn’t align vertically:
- Post titles display twice:
- Looks incomplete:
- A demo (Presentation) needs to be complete.
- Test how your theme design breakpoints across desktop, mobile, and tablet: http://design.google.com/resizer/
- Can’t close the side menu: http://envato.d.pr/lBo1Ap/5v6pw1sP
- Comments area design could be improved: http://envato.d.pr/LrYeMO/ZGH7ZQgr
- Avoid all-caps: https://envato.d.pr/ajh467/llLuYkeLwW
- This section looks really odd https://envato.d.pr/qFtszT
- There are a few inconsistent spacing/padding as well as alignment issues throughout the design. I’d like you to go over it with a fine toothed comb and weed out these basic design issues. For examples and there are more: https://envato.d.pr/1wiqaq