If you’ve ever wondered how to see what fonts a website is using, the answer is as simple as opening your browser inspector. Since every bit of a website is interpreted in your browser, if you know how to use your browser inspector properly you can figure out fonts, images, CSS properties, and anything else on the page.

Most web hosting today will have some limitation on the amount of storage they’ll allow you. Maybe it’s 1GB or 20, but at some point, you’ll get near the border of using too much disk space. When you do, you’ll probably have some large files on a cPanel hosting account. And when that’s true, you’ll want to remove them to get back under your storage quota. But it’s not very clear or intuitive how.

One of the very few complaints I have about Beaver Builder is that it can be difficult to undo changes—specifically, to undo Beaver Builder layout changes, for which normal “Ctrl+Z/Cmd+Z” undoing within Beaver Builder itself simply won’t work.

There are a lot of migration systems for WordPress. We’ve had lots of good experiences with All-in-One WP Migration. Some people swear by WP Migrate DB Pro. Others are partial to WP-CLI’s terminal-based systems. One of the few tools I’d never tried was Duplicator, but I recently did and I love it. I was very pleasantly surprised about a specific facet of it: I don’t need WordPress to get a new local copy of a remote WordPress site running on my local machine. You just pull down two files, put them in the same folder, and then you’re set. It’s great!

One reason we love SiteGround is its comprehensive caching solution, SuperCacher. It sits on SiteGround’s own servers so it’s much faster and better tailored to your site than plugin-based solutions like W3 Total Cache, and so if you’re using it you basically don’t need any other WordPress caching solution.

Custom fields are one of the more powerful aspects of WordPress. They’re also, by default, victims of just about the worst interface ever designed. The idea of capturing and using metadata is great, but a better interface helps a ton. Keeping up my current infatuation with the Pods plugin, here’s how it can help you make great interfaces to WordPress post meta data.

One of the hardest things about debugging or extending WordPress plugins is often simply finding where a piece of code lives. A plugin may have many thousands of lines of code across dozens of PHP files, organized however the plugin developers thought made sense to them.

WordPress plugins can cause all kinds of errors: 500 internal server errors, PHP parse errors (also called syntax errors), errors that simply whitescreen your entire site, and more.

Custom taxonomies are a great way to organize information in WordPress. And the Pods plugin makes it easy create them without having to write any PHP code. We’ve got a full article explaining custom taxonomies in a fair amount of depth, so for here I’ll just offer a summary. You want a custom taxonomy because:

Sometimes you want your navigation menu items to link to something on the middle of the page. This is especially true for one-page websites or long scrolling homepages.