You know, we use ad-blockers as well. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf San Francisco, dedicated to smart front-end techniques and design patterns.
This extended category features quality articles about developing clean, smart and fast websites with WordPress. The articles are intermediate level, with an emphasis on practical, hands-on discussions related to WordPress. Curated by Daniel Pataki. Subscribe to the RSS-Feed.
There has quite probably never been a better time to be a premium theme user. While a huge increase in the supply of quality premium themes hasn’t particularly driven down prices, it has promoted a huge push for innovation, best practices and quality design. Unfortunately, there’s one crucial thing which rarely gets quite so much attention as the must have responsive design: after-sales support.
Sadly, all too often, documentation is seriously lacking, and getting a reply on the developer’s support forum or via email takes much longer than it should. This post aims to take the pain out of using a premium WordPress theme by sharing some tips I’ve learned in my time as a “support expert” for a major theme shop.
We've all been total newbies. In fact, I spend most of my time still feeling like one. So researching this article was a great opportunity for me to do some more learning, and to share all of that good stuff with you. I reached out to people from across the WordPress community to ask what advice they would give to people just starting their WordPress journey.
I talked with developers, designers, support reps, security experts, hosting companies, theme shops, plugin developers and just about everything in between. This article is a result of their insight, and I hope that it provides some encouragement and guidance to newbies - whether you're a user or a developer - as well as some tips for advanced WordPress users who continue to learn throughout their lives.
Frank is a responsive WordPress theme. It uses a modified version of the Foundation grid system. It also offers the unique feature of a modular home page layout system. The theme comes with various different layouts for your home page (1 column, 2 column, 3 column, 4 column, etc.) that can be mixed and matched. This allows for a home page with different content sections in different layouts.
If you've been around WordPress for a while you know how difficult it used to be to create post lists based on complex criteria while also conforming to WordPress standards. Over the course of a few years the platform has come a long way. By utilising the power of the WP_Query class, we can lists posts in any way we want.
The WP_Query class is one of the most important parts of the WordPress codebase. Among other things, it determines the query you need on any given page and pulls posts accordingly.
WordPress 3.5 is currently in the third beta release and the official release is expected on December 5th. This version of WordPress will be the second major release for 2012 and is focused on improvements of existing features, rather than adding new ones, such as media library, plugins installation and theme previewer.
The biggest improvement in the upcoming WordPress 3.5 is the way that users will add photos in content. With a more simplified interface, WordPress will make the whole workflow of uploading and inserting images much easier, even for beginners.
The shortcode ability of WordPress is extremely underrated. It enables the end user to create intricate elements with a few keystrokes while also modularizing editing tasks. In a new theme we're developing, I decided to look into adding widgets anywhere with shortcodes and it turns out that it isn't that difficult.
This tutorial is for experienced WordPress users; we will be looking at the widgets object and shortcodes without delving into too much detail about how and why they work. If you are looking for more information, I suggest reading Mastering WordPress Shortcodes and the Widgets API article in the Codex.
“First, let’s set a few things straight: becoming a top WordPress [developer professional] is hard work — very hard work. It’s going to take a lot of time, energy and determination. If you’re looking for an easy checklist or some “fast pass” to the top, you’re going to waste your time. Being one of the best is hard, and statistically speaking, the odds are stacked against you.”
If you're a regular reader of Smashing Magazine, that will no doubt sound familiar to you. A few weeks back Jonathan Wold wrote a post on how to be a top WordPress developer. But development isn't the only way to get ahead in WordPress, because one of the great things about it is that you don't need to be a developer to be an expert; you just need a passion for WordPress, for open source software, and for being part of a community.
WordPress is one of the most deployed content management systems around. One of the main reasons is the number of plugins available and the ease with which we can use the system. It is not uncommon to find websites using tens of plugins to accomplish various tasks and functions. Wouldn't it be nice if you could share the site content with other websites?
You may have a need to share advertisements, product information or your photo gallery if you are a designer. Whatever the reason, this article will show you how to create an embeddable content plugin to share your WordPress content with other websites.
WordPress has been gaining a foothold in the general CMS game for a few years now but the real breakthrough was the custom post type mechanism which allows for the creation of a wide variety of content. Let's take a look at how this came to be and all the options that this great functionality offers.
In practice, custom post types have been around for a long time, more specifically since February 17, 2005, when WordPress 1.5 added support for static pages, creating the post_type database field. The wp_insert_post() function has been around since WordPress 1.0, so when the post_type field was implemented in 1.5, you could simply set the post_type value when inserting a post.