We’ve reached the final article of the series. In the last post, we took a look at introducing validation, sanitization, and a couple of basic input elements that we can take advantage of when building option pages.

In this article, we’re going to take a look at the final set of three options and how to hook them up to the front-end of the theme.

(Continue)

If you’re just now joining us, we’ve covered a lot of topics in this series – we’ve attempted to give a complete overview of the WordPress Settings API as well as its related functions. We’ve discussed settings, options, navigation, and menus. We’ve also been working through practical examples employing each of the topics we’ve discussed.

(Continue)

In Part 3 of this series, we surveyed the various menu functions that the WordPress API provides. If you’ve been following along, then you know that we’ve already setup a settings page for our theme by using the add_theme_page function. Although introducing menus and submenus aren’t explicitly part of the Settings API, they play a role in building custom functionality, plugins, and/or themes.

(Continue)

At this point in the series, we’ve taken a close look at the Settings API and what it has to offer. We’ve even begun creating our own theme to help demonstrate everything we’ve been learning. We’ve covered sections, fields, settings, menus, pages, and more.

(Continue)

In the last article, we took a deep dive into the various types of menus that are supported by the WordPress API. Although they aren’t necessarily part of the Settings API, they play a key part in development especially when working on more advanced plugins and themes.

This article is going to put menus to practical use as we begin building out our Sandbox Theme by refactoring our existing settings and adding several new pages. Note that if you’re just joining us, make sure that you’ve caught up on the previous articles and that you have the latest version of the Sandbox Theme from the repository on GitHub.

(Continue)

At this point, we’ve learned why the Settings API matters, we’ve learned all about sections, fields, and settings, and we’ve even setup a Sandbox Theme that we’re using to develop functionality as we explore the API.

In this article, we’re going to take a look at how we can interface with the WordPress menu system. It’s important to note that this isn’t actually a part of the Settings API, but it’s so closely related that we should familiarize ourselves with how to use it.

As our themes and/or plugins become more complex, we need to know all of the various ways that we can include them into the WordPress Dashboard. In this article, we’re going to be taking a look at the various WordPress menu functions, when to use them, when to avoid them, and the situations to which each function lends itself best.

(Continue)

When it comes to developing WordPress Themes and Plugins, there are a number of different ways developers are creating their menus, options, and validation functionality. The thing is, there’s really only one way to properly do this within WordPress: the Settings API.

(Continue)

As we’ve mentioned numerous times here on WP Tuts (and as you’ve no doubt noticed), there has never been a better time to be a WordPress Developer. Be it client work or product development (with either themes or plugins), getting started in the WordPress ecosystem is almost more of a question of ‘where’ rather than ‘how.’

(Continue)