Home News and Updates It’s Official. I’m a Sandboxer!

It’s Official. I’m a Sandboxer!



Updated on


Recently, I used Sandbox to build the Wrath theme.

The first time toying with the Sandbox theme was a challenging, but rewarding experience. From dynamic classes and backward compatibility techniques to negative margins and avoiding bloated markup, I’ve learned a lot.

You might not know this; my skills are self-taught. And, I haven’t had time to keep up with the latest techniques and standards so I’m grateful for it when something like Sandbox comes along. For me, it reinforced fundamentals, introduced new techniques (WordPress related), forced me to push CSS possibilities, and allowed me to end up with something up to standards. All of that within one sitting, as you can imagine, I can’t say enough about the Sandbox theme.

Conversely, although now I can see why other theme authors have been pushing for widespread adoption of Sandbox, there’s room for improvement (like all things of course).

For one thing, Sandbox’s horizontal menu does not limit


depth display to 1. If you don’t know what I’m talking about. Imagine a horizontal menu coded for one level of links having to display two or three levels. The Sandbox default stylesheet tries to work around the multiple depths display by telling the next level of links to display as drop-down links (only visible on hover).

Sandbox drop-down links are slick, but they can’t solve this problem because the drop-down solution doesn’t work out of the box, not even in Firefox. The problem isn’t whether the default styles for drop-down links matches those of the customized theme or skin. The problem is the drop-down links don’t function or display properly. Some of the drop down links are displayed in Firefox, partially. For Internet Explorer 6, they don’t appear at all.

The temporary solution is to add




, in the



For another example, the reason Wrath is only a theme based on Sandbox rather than a Sandbox skin is because there was no way for me to add the red about box without touching the source codes. This isn’t actually a problem, but it would help future Sandbox skin designers a lot if later versions allow us to add on or modify the source code without having to touch it.

Rather than despite the small room for improvements, Sandbox is a great theme because it has almost everything you need to learn and build upon.

Of course, I will continue working with Sandbox. A Sandbox checklist will be posted soon.


Please enter your comment!
Please enter your name here

Recent posts

10 Ways To Speed Up Post-Building Process With WordPress Gutenberg Themes

There’s no need to explain why I decided to start with Gutenberg-supporting products. All in all, Gutenberg is a well-known and long-awaited product. It is more...

HostPapa Linux Hosting: Reliable, robust and fast

As a small business owner, it can be challenging to find the right hosting provider for your website. HostPapa distinguishes itself from other web...

Are You Making These Costly Mistakes When Outsourcing?

In today’s world, it is almost impossible to find a small business where everything about the business process is done in-house. For most small...

Flat Design for Your WordPress Site: What Is It + 4 WordPress Flat Design Themes

Web designers in the past mostly used 3D styles for buttons that made the button seem more realistic. That all changed when flat design...

LawBlog WP Theme Review

Regardless of which area of law you practice, it’s imperative that you have proper online representation. You need to give your customers a feeling...

Recent comments