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 Jeff Starr. .
Popular tags in this category: Essentials, Techniques, Hacks, Templates, PHP, Themes, Plugins.
BuddyPress is social networking in a box, the loveable plugin that has people around the world getting social. But using BuddyPress isn’t all about waking up one morning and being struck by the amazing idea of creating the next Facebook. BuddyPress is a tool for creating communities. In fact, if you look at successful implementations of BuddyPress, you’ll see they aren’t Facebook clones, but rather niche groups that have put BuddyPress to work in growing their community.
The 1.7 release should make BuddyPress compatible with any WordPress theme, making it even more accessible to potential community builders. In this article I'm going to look at some of them; five communities that are using BuddyPress, some big, some small, some established, some emerging, some successful and some unsuccessful.
We all know that WordPress is awesome - but being awesome isn't always enough. Does it perform well under pressure? Can it deal with traffic from millions of visitors every month? There's no question that WordPress can be used for your or my blog, but what about multi-authored blogs with thousands of comments? How do developers make it scale and perform?
I talked to the developers behind some of the biggest WordPress blogs on the planet and asked them to tell me their secrets. Now I get to share them with you.
First, let's set a few things straight: becoming a top WordPress developer 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.
By the way, installing WordPress, reading a few tutorials and customizing a few themes does not make someone a top developer. They may call themselves an "Expert", and that's fine. They may know more than the average person. But a top developer moves far beyond the basics, and pushes the very boundaries of what is possible. They innovate, contribute to the community, and demonstrate mastery in the work they do. So I want you to be more than an "expert", I want you to be one of the best.
This is a personal request from your user, a rallying cry from a compatriot. I personally love WordPress. I make my living from it. The average user, though, couldn’t care less about it.
They just want to run their business, tell their family history, organize their church, share their photos or live their life online with a minimum of impedance. In its evolution from simple blogging tool to CMS, framework and software ecosystem, WordPress is losing its way. It needs us to help bring it back and cultivate simple genius.
As iOS, Android, and Windows 8 take the Web to smaller screens, designers are adopting techniques to make their websites usable on handheld devices.
Responsive Web designs present different formatting and layout to suit the device on which their pages are displayed. Browsers choose the appropriate styles on page load, freeing website owners from having to maintain different sets of pages for different display scenarios.
This tutorial explains how to create a WordPress bookshelf plugin that displays books on a shelf like Smashing Magazine’s eBook page. Some key WordPress functionality will be showcased throughout the tutorial that could benefit your own project.
The article covers how to create post types, shortcodes and meta fields using WordPress’ functionality and how to combine them to make a fully configurable plugin. To begin, we’ll explain how to register the plugin, develop the back-end functionality and then create the front-end display using shortcodes.
Whenever we set code to screen, we must follow some sort of logic. You may well be the only person who understands that logic, but you still make the effort. The reason we follow standards and practices is to adhere to a common logic, so that we find each other’s code understandable and sensible.
Today, we’ll delve into the gaping maw of knowledge that is the standards and practices of WordPress coding. By the end of this article, you should be familiar with the guidelines and the underlying approach. With some practice, you will be able to adhere to the rules and make educated guesses about the less regulated corners of the specifications.
In this article, we’ll look at writing documentation for a WordPress plugin, theme or product. Most of the information can be applied to documentation for other software types, but we’ll look at some WordPress-specific aspects. In my experience, the quality of documentation in WordPress plugins and themes varies widely.
From poorly documented plugins with one-line readmes to products with user guides, developer APIs and in-depth screencasts, you’ll find every type of documentation in the WordPress ecosystem. Many plugins and themes are built by developers who don’t have the time to write documentation or don’t have the money to pay a technical writer.
Let’s see what we got: WordPress as this flexible, easy to use Open-Source blogging and CMS system. More and more mobile devices flooding the market every day and being extremely popular. Plus the need of more beautiful designed and coded WordPress themes for users to choose from that will work well across all these different devices. So what are we waiting for? Let's get to work!
At first the idea of designing and developing a fully responsive, mobile-ready WordPress theme can be a bit overwhelming and you might think: How am I going to handle the responsive design with all this flexible content a WordPress theme has? What do I have to consider when designing for touch devices? And do I really have to get rid of drop down menus and other hover elements on mobile devices?