22 Oct 2014

feedWordPress Planet

WPTavern: BuddyPress 2.2 Will Add Support for Composer


BuddyPress lead developer Paul Gibbs committed support for Composer to BuddyPress core this week. Developers who want to check it out can find the json file at: trunk/src/composer.json.

If you're not yet familiar with Composer, it's essentially a tool for dependency management in PHP. It is designed to manage packages on a per-project basis by bringing in any dependent libraries that you declare in the composer.json file. The dependencies are then automatically installed in a vendor directory or other specified location inside your project.

BuddyPress is not yet listed on Packagist.org but should be added soon. Once it's listed there, it can easily be declared as a dependency after the next version (2.2) is released.

    "require": {
        "buddypress/buddypress": "~2.2"

BuddyPress 2.2 is expected in mid-January 2015, according to Gibbs' reply in the ticket to add Composer. He plans to configure Packagist to pull from http://plugins.svn.wordpress.org/buddypress/.

Because BuddyPress is identified as a WordPress plugin in its json file ("type": "wordpress-plugin"), composer/installers will by default send it to the wp-content/plugins directory.

If you can't wait two months, and you're dying to use BuddyPress with Composer right now, there's an alternative method. I spoke with WordPress Composer evangelist Andrey Savchenko (@rarst) regarding the news. He suggests that in the meantime developers could use wpackagist, which provides a mirror of the WordPress plugin and theme directories as a Composer repository.

 "require"     : {
  "wpackagist-plugin/buddypress": "~2.1"
 "repositories": [
   "type": "composer",
   "url" : "http://wpackagist.org"

If you search for "WordPress" on Packagist, you'll find many other projects, which can also be easily added into your next BuddyPress project. Composer support makes it easy to create a master composer.json file for your projects, that will save you time by allowing you to load all of your dependencies in a matter of seconds.

22 Oct 2014 10:32am GMT

WPTavern: How to Increase or Decrease The Font Size in The Visual Editor

Visual Editor Font Size Featured Imagephoto credit: Mr Ush - cc

If you use the visual editor to write posts or pages, you'll know that the font can sometimes be hard to read due to its size. Some themes use a tiny font in the visual editor and unless you know how to apply CSS changes, you're stuck with it. Luckily, there's a plugin available specifically for the purpose of adjusting the font size in the visual editor called Visual Editor Font Size.

Developed by Nikolay Bachiyski, Visual Editor Font Size adds a meta box to the post editor. After installing and activating the plugin, check the screen options on the post editor and make sure the box next to Visual Editor Font Size is checked. The meta box has a plus and minus button to increase or decrease the font size. There's also a sample of text to indicate how large or small the font is and the revert link resets the text to the default size.

Visual Editor Font Size Meta BoxVisual Editor Font Size Meta Box

Although it works fine in WordPress 4.0, I'd rather see the size adjusting buttons added to the TinyMCE editor. The editor is the first place I look to manipulate content in the visual editor and when I didn't see any additional buttons, I thought the plugin was broken. This plugin is great if you don't have the CSS knowledge or access to make the appropriate changes, but it's not the best way to solve the problem.

If the theme you're using doesn't have a visual editor style applied to it, contact the author and send them this link. It's a Codex article that explains how to add a style to a theme specifically for the visual editor. When executed well, the content in the editor will look identical to what visitors see. Stargazer, by Justin Tadlock, is an excellent example of a theme where the content in the visual editor is the same style that's seen by visitors.

22 Oct 2014 9:36am GMT

WPTavern: Comparing The Photo Publishing Experience of WordPress For iOS to Facebook and Twitter

Welcome Home Featured Imagephoto credit: angusf - cc

In late September, WordPress.com published the first in a series of short videos that shows how easy it is to publish content from a mobile device. In the 15 second video entitled "Welcome Home," a user is seen taking photos with an iPhone in various locations. Near the end of the video, the user taps the WordPress mobile app icon and sees a post with one of the images captured by the phone. What's not shown is the process of publishing the photo.

The take away from the video is that it's easy to publish photos to WordPress.com from a mobile device. With that in mind, I was curious what it's like to perform the same task with other social networks on a mobile device. The following is my experience using WordPress For iOS for this specific task and how it compares to using Facebook and Twitter.

The WordPress For iOS Process

The first thing I do is take a photo with my phone. Next, I load the WordPress For iOS app. I tap the Pencil icon in the lower right corner and make sure to select my WordPress.com account. I give the post a title which is normally related to the image, then write some content. Writing a lot of content on the iPhone is not an ideal experience so I usually keep it short.

Next, I add an image to the post. Selecting a photo from the phone and uploading it to WordPress is an easy task. After the photo is inserted, I head into the Options area. From here, I assign a Category and relevant Tags. I preview the post and if I like what I see, I tap the Publish button.

WordPress For iOS Post PreviewWordPress For iOS Post Preview

While I'm not forced to assign a Category or Tags to posts, it's a good practice and one I've already established with the site.

The Facebook on iOS Process

I open the Facebook app and select Photo. I'm given the choice to either select a photo from the phone's media library or to take a picture. The ability to use the camera to take a photo for a post is a distinct difference between the Facebook app and WordPress. I usually have an image ready to publish but when I don't, taking a photo within the app is a nice convenience. After selecting a photo, it's uploaded to Facebook where I then add context for the image.

With the Facebook app, I can add other data to the post such as location, the people I was with or who are in the photo, and my mood. Most of the time, the additional information doesn't apply to my photo. After adding some context, I tap the Post button. Boiled down to the simplest procedure, I can publish a photo post on Facebook in five steps.

  1. Open App
  2. Select Photo
  3. Choose or Take Photo
  4. Apply Context
  5. Post

I don't have to worry about assigning a category or tags to Facebook posts.

The Twitter on iOS Process

I open the Twitter app and tap the button to write a new Tweet. I tap the button to add media and similar to Facebook, I can either choose from the phone's media library or take a photo. After selecting an image, I add context, then tap the send button. I don't have to worry about tags or categories.

Not The Simplest, But The Most Future Proof

WordPress For iOS isn't the simplest way to share photos with the world but it's the most future proof. It may be more work, but an added benefit to using WordPress.com is its Publicize feature. When a post is published, WordPress.com can send it to both Twitter and Facebook. This is an ideal way to share photos to the widest possible audience while maintaining full control of your content.

Facebook and Twitter are islands where you have no control and the carpet can be pulled out from under you. But at WordPress.com, you have a place to call your own and if you desire, you can pack up your content and leave. This is what the message "Welcome Home" means to me. What does it mean to you?

22 Oct 2014 8:30am GMT

WPTavern: Initiatives Being Developed Alongside WordPress

Opportunity Featured Imagephoto credit: {Guerrilla Futures | Jason Tester} - cc

While it's easy to focus on WordPress core development, there are a handful of satellite projects to keep an eye on. There is so much happening around the WordPress project, it's tough to keep up. This post highlights some of the satellite projects and initiatives that are being developed concurrently with WordPress.

Feature Plugin: Improve Image Editing

Led by Siobhan McKeown, the Image Flow project is aimed at improving the image editing experience in WordPress. It's a feature that will likely not be removed, so the team is doing what it can to improve it. In the most recent meeting, the group discussed various wireframes and will be making changes based on community feedback. The group meets every Friday and uses Google Hangout to conduct meetings.

Scalable Dropdowns

Created by Helen Hou-Sandi, the scalable dropdowns project is focused on addressing some long-standing issues with dropdowns in WordPress, specifically for users and pages. An initial meeting has taken place on IRC and as a result, several issues have been opened on Github for work and discussion. If you're interested, review the issues on Github and contribute where you're able to. Questions related to the project can be asked here.

Meta, Date, and Taxonomy Query Improvements

Boone Gorges is leading the way towards improving WP_Meta_Query, WP_Tax_Query, and WP_Date_Query. The improvements are slated for WordPress 4.1. According to a recent project update, most of the proposed changes Gorges listed in the initial post have been made.

Inline Documentation

Shortly after WordCamp San Francisco 2013, the inline docs team began working on providing inline documentation to every hook in WordPress. The team successfully completed documented every action and filter hook as part of the release of WordPress 3.9. In a recent meeting, the group discussed options for adopting a documentation standard for core JavaScript.

WordPress Training

The training initiative is a proposed curriculum that covers everything from explaining what a theme is, to creating and altering child themes. The group is working on various training modules that make up each class. In their most recent meeting, the group discussed the status of modules in progress, infrastructure for testing modules, and a team training sign up form. If you're interested in contributing to this project, the team has meetings every Tuesday 18:00 UTC in the #wordpress-getinvolved IRC channel.

Opportunities to Contribute

I've only scratched the surface with the number of initiatives available to contribute to. Whether you have a special interest in accessibility, UI, mobile, support, themes, or translations, there's a project that could use your help. The best way to stay informed of new and existing initiatives is visit Make.WordPress.org.

22 Oct 2014 4:06am GMT

Matt: Retina 5k Mac

imac-retina-step1-hero-2014 To me one of the most meaningful shifts in computing the past few years has been how the resolution of displays is getting higher and higher, and interfaces are starting to become resolution independent. I feel like when pixels disappear there's less of a wall between people and the technology, it starts to blend a meld a bit more. It's something I've been personally passionate about since the first retina iPhone, tirelessly beating the drum at Automattic to make everything we do shine on hi-DPI screens, or leading the WordPress 3.8 release that brought in MP6 project to make WordPress' aesthetics cleaner and vector-based.

I'm sitting in front of a Retina 5k iMac right now typing this to you. (It was supposed to arrive on Friday but came a few days early.)

It's the most gorgeous desktop display I've ever seen, breathtaking at first and then like all great work becomes invisible and you forget that there was ever a time when displays weren't this beautiful. (Until you look at some lesser monitor again.)

I've been using 4k displays, the Sharp and the ASUS, with Mac Pros for a few months now, and to be honest they come close, but this takes the cake in every possible way, including the design and aesthetics of the computer/display itself which is laptop-thin at the edges. If you've been on the fence, and you're okay with the tradeoffs an iMac has in general, get one. I can't wait for them to do a 5k Thunderbolt display (but it sounds like it might be at least a year away).

P. S. If you're looking for a gift for the iMac that has everything, consider a slipper to keep its feet warm.

22 Oct 2014 12:42am GMT

WPTavern: Monster Widgets for bbPress and BuddyPress Make It Easy to Test Core Widgets

photo credit: massdistraction - ccphoto credit: massdistraction - cc

The original Monster Widget plugin is a handy tool created by Automattic to assist theme developers with testing. Essentially, it allows you to quickly drop all core widgets into your sidebar at once, saving you the trouble of having to add them individually.

Now you can get the same for bbPress and BuddyPress, thanks to a two new plugins from @mercime, a contributor on both WordPress sister projects.

The BuddyPress Monster Widget makes it easy to populate your sidebar with all of the BP core widgets, including the following:

The widgets are pre-configured to show a set number of blog posts, members, friends, etc. The list of widgets displayed can be altered by using the 'buddypress-monster-widget-config' filter included in the plugin.


The bbPress Monster Widget plugin allows you to add all of the bbPress core widgets to your sidebar in one instance, including:

The bbPress Monster Widget also comes pre-configured with a set number of topics and replies displayed. The default list of widgets can be altered by using the 'bbpress-monster-widget-config' filter.

When creating a theme for public distribution, it's important to make sure you know how the core widgets are going to look with your theme applied. This is especially true for community-oriented sites that utilize bbPress and BuddyPress, because the widgets often play a big part in connecting members to recent activity on the site. Download the bbPress and BuddyPress monster widgets from WordPress.org to make it quick and easy to test the core widgets.

22 Oct 2014 12:00am GMT

21 Oct 2014

feedWordPress Planet

WPTavern: Compass: A Free Starter Theme for WordPress Built with Hybrid Core, Bourbon, and Neat

photo credit: Theresa Thompson - ccphoto credit: Theresa Thompson - cc

The life of a frontend developer has changed a great deal over the past few years, with the introduction of new technologies for authoring CSS and automating tasks. We're starting to see that trickle down into every new WordPress starter theme.

These days you've got to npm install allthiscrazystuff just to get started on a project. Once you've gone through the setup, you're ready to work more efficiently with many of the more boring tasks automated for you.

Compass is a new WordPress starter theme that incorporates a host of modern web development technologies to help you create themes faster while staying in line with WordPress coding standards. The folks at Flagship, a soon-to-launch theme shop, released Compass for free earlier this month, claiming that it is "the most advanced WordPress starter theme in existence."

Note: The Compass theme name keeps with the company's nautical vibe, but it's not to be confused with the open source Compass CSS framework built with Sass.

Out of the box, the theme is fairly plain but, thankfully, not hideous. Obviously, it's a starter theme, so the point is to provide the basics for getting started on your own beautiful creation.


Sass, Bourbon, and Neat with Composer Support

Similar to the Some Like It Neat starter theme, Compass features support for Sass, Bourbon, and Neat. The theme uses Composer to manage dependencies for PHP, allowing you to declare the dependent libraries for your specific project to have them installed for you.


The Flagship team has worked hard to create what they believe to be the most advanced and robust Grunt workflow available for WordPress theme development. You'll need to install Node.js to run the Grunt task runner with the Compass theme, although many theme developers will likely already have it installed. Some of the tasks will also require external command-line applications, which you'll need to install as global Node.js packages.

Once you're ready to roll, you'll be able to automate an amazing number of tasks associated with theme development, including things like auto-prefixing CSS properties, tidying up style.css to match the WordPress Coding Standards, generating the RTL style sheet, optimizing images, and much more. Here's a short sampling:

Check out the documentation on GitHub for the comprehensive list of available tasks included in the Compass theme.

Hybrid Core

Compass is built on top of Justin Tadlock's Hybrid Core, one of the oldest and most developer-friendly frameworks for building WordPress themes. The Compass release post explains why Flagship went with Hybrid Core:

There are so many things that are going to be necessary on nearly every project, and they're regularly done poorly in many of the themes that we've used and tested. Justin has done an amazing job of doing things "the WordPress way" and has been building and iterating Hybrid Core for many years.

The framework handles functionality that most themes commonly require, such breadcrumbs, grabbing media, integrating microdata like schema.org, pagination, theme layouts, and translation.

Like many other new starter themes, Compass also offers support for the Theme Hook Alliance project in an effort to provide a common set of entry points for plugin and theme developers looking to extend the theme.

Although Flagship hasn't yet officially launched, the site shows a preview of a few planned themes that were built using Compass as a starter theme.


The theme shop will soon launch with a unique pricing model that doesn't involve bundle or theme club pricing. Each theme is priced at $199, with a $99 annual fee for support. The Compass starter theme that they use to build all of their products is open source and available to developers for free on GitHub. Check out the Getting Started guide for documentation, including video tutorials on installing the tools and working with Compass.

21 Oct 2014 7:40pm GMT

WPTavern: Easily Edit a Post or Page Using The Slash Edit Plugin

Slash Edit Featured Image

If you're not a fan of the admin bar or it's disabled and you want a shortcut to edit posts in WordPress, you might be interested in a new plugin called Slash Edit. Developed by Ronald Huereca, Slash Edit adds the ability to edit the following items by adding /edit to the end of a url.

To load the appropriate editing interface, visit a post or page while logged into WordPress and add /edit to the end of the url. It can also be used as a shortcut to login to the backend of WordPress.

Huereca works in an environment where the admin bar is consistently disabled. He created the plugin to provide a convenient way to edit pages or posts without having to search for them in the backend. "I thought, wouldn't it be cool to just add "/edit" to the end of a post or page and be redirected to the right place in the admin panel?"

Huereca doesn't know what else could be added to the plugin to fulfill its basic purpose. "I'm not sure how much farther this plugin can go, but the WordPress community is ingenious as far as feature requests, so I'm eager to get feedback on the base feature set." I tested the plugin on WordPress 4.0 and it works as advertised. To keep tabs on development, you can follow the project on Github.

21 Oct 2014 3:06am GMT

20 Oct 2014

feedWordPress Planet

WPTavern: Jason Schuller to Re-Enter WordPress Theme Market with Niche Admin Designs


Jason Schuller, the original founder of the Press75 theme company, has been off the radar for a few years as he pursued experiments with alternative publishing platforms. He officially exited the commercial WordPress theme business earlier this year when Press75 was acquired by Westwerk, following a sharp decline in the shop's monthly revenue.

Prior to selling his company, Schuller had begun to focus more on his experimental projects, Dropplets, Leeflets, and Cinematico. Over the years, he had become disillusioned with the software, as he watched WordPress become increasingly more complex. This frustration, coupled with the weight of complex frameworks that started devouring the WordPress theme market, essentially vaporized his passion for the software and pushed him out to make something new.

Earlier this year, in an interview with Jeff Chandler, Schuller expressed his dissatisfaction with trying to make WordPress do what he wanted and said that he wouldn't be concentrating his efforts on WordPress in the immediate future.

Video Preview of Custom WordPress Admin for the "Pickle" Project

In his never-ending quest to simplify publishing online, Schuller has once again picked up WordPress to experiment with creating a radically simplified admin design for Pickle, his restaurant-themed HTML template.

A short video preview of my #WordPress admin redesign for "Pickle": http://t.co/lvQtgIaAWP #design

- Jason Schuller (@jschuller) October 20, 2014

Traditionally, making a template like that editable in WordPress ends up being a complex thing for your average user to navigate in the admin. The preview video shows how Schuller has re-imagined the admin for his niche one page template.


He has essentially removed the admin, de-registered all the styles and many of the components, in an effort to create a custom CMS for this particular template. The result is a better correlation between the content editing experience and the actual website, with simplified action buttons.

If you watch the preview, you'll hear Schuller summarize why he created the simplified admin:

This is my biggest issue with WordPress right now. It doesn't scale backward for minimalist websites like this. The CMS should reflect, in my opinion, what you're trying to accomplish with your website, and all of these unnecessary components of WordPress just really don't need to be here unless you need them for what you're trying to accomplish.

Schuller said that it took him approximately two days to customize the WordPress admin to suit his template. "I'm nearly finished with it. It's going to launch as a downloadable theme first and then I'll be launching a hosted version as well," he said.

The theme will not be launching on Leeflets but rather on a new domain, yet to be determined, bringing Schuller back into the WordPress theme market. Why is he returning?

"With this particular project, I really just wanted to get my vision out of my head as quick as possible," he said. "With that in mind, I couldn't see creating a custom CMS just for Pickle, so I figured WordPress would be the best way to do that quickly. Plus, you still can't ignore WordPress's reach."

I asked Schuller if the Pickle admin theme is a one time project or if he plans to create more niche admin themes to accompany his designs. "If Pickle goes well, I have a few other niche admins in mind for specific templates," he replied.

"My goal is really simple - to help my customers/users create and manage websites. If WordPress helps me do that in an efficient way, I'm all for it. But I'll be doing it my way this time around," he emphasized.

Schuller's minimalist approach to the WordPress admin is something that he hopes will be easier for his target market to wrap their brains around. The popularity of the Pickle template is what spurred him on to create an editable version using WordPress. "I wasn't expecting much when I released the Pickle HTML template," he said. "But it was an instant hit. There are quite a few people helping restaurants create websites with it. That's what triggered the idea to make a WordPress version."

At the moment Schuller is in touch with his market on a very small scale, but he hopes that it will expand with a successful launch of the Pickle theme. "My hope is that the WordPress version makes it even more enticing for businesses looking for a minimalist website/solution."

Schuller has identified a problem that many developers are hoping to solve. WordPress core is moving towards bridging the separation between the editing experience and the display of the content, with improvements to the customizer and experimental projects like the frontend editor. Others hope that the new JSON REST API will make it easier for developers to create custom admins.

These changes cannot come soon enough, but will they be fully able to provide a more natural editing experience for users? Those, like Schuller, who have wrestled with dissatisfaction, have a decent shot at creating a revolutionary editing experience for the 10 year old platform. His inspiring work on the Pickle admin breaks WordPress out of the box and forces developers to look at the content editing experience in a new way.

A more modular admin that can easily be scaled back for minimalist websites is something that would allow developers to truly customize the CMS for any niche template or project. The WordPress admin then becomes a chameleon of sorts, able to disappear into its surroundings with the content in focus. Schuller's Pickle experiment is a good example of this, and likely part of a trend that we'll see more in the future.

20 Oct 2014 10:14pm GMT

WPTavern: The First “Rate and Review a Plugin Day” is a Success

Thanks to everyone who participated in the first "Rate and Review a plugin day". After reviewing the #wppluginreviewday hashtag on Twitter, it's clear that a lot of people submitted reviews to their favorite plugins. Based on an estimate by Richard Tape, 455 reviews were published on October 17th. When compared to 254 reviews on October 16th, that's an increase of 180%. Here are a few noteworthy mentions of the hashtag in action.

Wrote a review for @eddwp here https://t.co/zvwWNJaGtu Awesome feeling! #wppluginreviewday

- Bharath Mandava (@_mandava) October 18, 2014

So I delivered a plugin review on .org today. http://t.co/4ua0iG0XjQ #wppluginreviewday /cc: @stevengliebe :)

- David Decker (@deckerweb) October 17, 2014

For Rate & Review a #WordPress Plugin Day I gave kudos to @iThemesSecurity #wppluginreviewday

- BobWP (@bobWP) October 17, 2014

Observations I Made While Submitting Reviews

It took 90 minutes to rate and review the plugins I've depended on for years. I noticed some of the plugins haven't been updated since 2010. In some cases, the last review a plugin received was from 2012 or earlier.

When I announced the holiday, I asked users to browse to the bottom of the plugin's description page and click on the broken or works box. As I submitted my reviews, I forgot about the compatibility box. When submitting a review, there is a drop down menu to select which version of WordPress I'm using. I used this in combination with my review to tell people if the plugin works or not.

WordPress Plugin Review Submission FormWordPress Plugin Review Submission Form

Clicking the works or doesn't work button is an easy task but it's a separate action from submitting a review. It's also the last widget on the description page and depending on the length of the description, may be hidden from view. I suggest merging the compatibility box into the process of submitting a review so it's one action. Even though submitting compatibility information can be as simple as pressing a mouse button, not many do it.

The Disconnect Between WordPress.org and The Backend of WordPress

Your ratings, reviews, and compatibility checks are contributions to WordPress. It's actionable data that millions of people use to determine whether or not to use a plugin. The backend of WordPress is an area millions of users interact with yet, the option to rate and review plugins as well as submit compatibility information doesn't exist. The plugin details modal doesn't show the compatibility box on the plugin's description page and although you can read reviews, you can't rate or review plugins.

Current Plugin Details ModalPlugin Details Modal

The plugin management page in WordPress hasn't seen a visual upgrade in a long time. Here's what it looks like in WordPress 4.0.

WordPress 4.0 Plugin Management PageWordPress 4.0 Plugin Management Page

WordPress 3.9 revamped the theme browsing experience while 4.0 introduced a refreshed plugin install and search experience. Perhaps it's time to refresh the plugin management page. One suggestion is to create two different list views. The management page in 4.0 could be the slim, detailed view. The enhanced view could use the card concept as seen on the Add Plugins page. Instead of displaying the crowd sourced information, you'd be able to rate and review the plugin and submit compatibility info from within the card.

WordPress 4.0 Plugin CardsWordPress 4.0 Plugin Cards

The problem with two different views is that a sub-set of users wouldn't see the card view and stick with the default. In order to maximize the potential of obtaining crowd sourced data, the submission points have to be accessible by as many people as possible.

Tighter Integration Between The Backend and WordPress.org

In order to submit ratings and reviews, you need to be logged into a WordPress.org user account. I'm unsure on how to properly address this issue. One idea is for WordPress to provide a connection similar to Jetpack where I connect a WordPress powered site to my WordPress.org account. This could also act as an opt-in mechanism. Ultimately, I'd like to see better integration between the WordPress backend and the WordPress.org website.

I'm not advocating that I be able to browse the WordPress.org website from the backend of WordPress, that's what browsers are for. I see plenty of opportunities to connect certain actions on WordPress.org to the backend of WordPress, such as the ability to create a forum post to receive support.

A New Annual Tradition

While you don't need a special day to review plugins, it's a unique feeling to do something so many others across the world are doing at the same time. I'm encouraged to see so many people who have rated and reviewed their favorite plugins. Based on the feedback we've received, this will likely become an annual tradition.

20 Oct 2014 6:54pm GMT

WPTavern: Some Like It Neat: A Free WordPress Starter Theme Built with Underscores, Bourbon, and Neat

photo credit: j03 - ccphoto credit: j03 - cc

Some Like it Neat is a new starter theme for WordPress, based on the popular ultra-minimal Underscores theme. It also incorporates Bourbon, a lightweight mixin library for Sass. On top of that it adds Neat, which applies a semantic grid framework for Sass and Bourbon, enabling you to build any responsive layout that you can dream up.

Since Some Like It Neat is a simple starter theme, there's not much to see in the screenshot, apart from a relatively blank canvas, waiting to be shaped and styled.


The power of this theme lies in the tools that it incorporates. Some Like It Neat expedites the creation of a modern frontend development workflow for WordPress theming with responsive grids and a few prepackaged styles. The theme offers support for the following tools:

This is essentially everything you need for a Bourbon-soaked development workflow. Developers starting with this theme should already be familiar with Sass, since it's the foundation for using Bourbon and Neat. If you need a Sass primer, Sitepoint has a great tutorial on the basics. WP Beginner also has a quick introduction to help WordPress theme designers get started with Sass.

Some Like It Neat also allows for Gulp.js task automation. Alex Vasquez, the theme's creator, says that this feature still has room for improvement. The theme currently includes support for the following tasks:

Additionally, Some Like It Neat adds support for the Theme Hook Alliance (THA), a community-driven project that offers a standardized set of third-party action hooks to theme developers to implement for more flexibility. THA has a growing list of compatible themes. Vasquez opted for adding it to help keep things within the theme cleaner and easier to maintain.

Why Use Bourbon and Neat?

Incorporating Bourbon and its parallel projects into your WordPress theme is a matter of personal preference. In the past, Vasquez had used frontend frameworks such as Bootstrap and Foundation, but after discovering Bourbon+Neat, he found that it gave him a more efficient approach to theme creation:

To achieve the responsiveness required of various projects, I would have to tear up my HTML, input my own selector classes and what have you, in addition to changing my CSS. I didn't like it. I heard about Neat and really liked its approach to a grid framework. You keep your HTML structure the way you like and all of the styling in your Sass files.

If that sounds like a better workflow for you, then you may want to set aside some time to give this starter theme a try. It can be used as a parent theme from which you create a highly customized child theme. Vasquez has outlined how to get started in the documentation, which will walk you through installing Node, Sass, Gulp.js, etc. He also posted a handy folder structure as an example for how projects are structured with the starter theme.

Some Like It Neat is Alex Vasquez's first submission to the official WordPress Themes Directory. You can download it via your admin theme browser or from its GitHub repository.

20 Oct 2014 6:04pm GMT

Matt: Life and Work at the Distributed Wonderland

Luca Sartoni writes How I fell into the rabbit hole: life and work at the distributed wonderland.

20 Oct 2014 4:26pm GMT

19 Oct 2014

feedWordPress Planet

Matt: Run Better

Joe Boydston, the self-described "crazy running guy" who runs as far as 90+ miles from the airport to WordCamps or meetups when he lands, has written a bit about how to run better. At our company meetup he ran running workshops and coached a lot of people including myself, and applying his suggestions I've been able to do a lot better.

19 Oct 2014 11:51pm GMT

18 Oct 2014

feedWordPress Planet

Matt: Pink Drill Bits

Fracking company teams up with Susan G. Komen, introduces pink drill bits for the cure, presented without comment. Hat tip: Kristin Grimm.

18 Oct 2014 11:27pm GMT

17 Oct 2014

feedWordPress Planet

WPTavern: Themosis Object-Oriented Development Framework for WordPress Now Available


Version 1.0 of the Themosis development framework is now available. Belgium-based application developer Julien Lambé created Themosis in order to accelerate object-oriented development with WordPress. It offers a routing system for managing WordPress behavior on an application level and also includes a Laravel-esque templating engine for view files. Last week Lambé announced that the framework is now out of beta and ready for public use.

Themosis, which Lambé describes as "a mix between WordPress best practices and a typical MVC framework," has evolved considerably since its beta period. Version 1.0 includes dozens of improvements based on developer feedback.

The website has been updated to provide complete documentation and code examples to help developers get started. Installation is quick and easy, as Themosis uses Composer for dependency package management, so you can install and update everything needed in a matter of seconds. The framework is designed with respect to WordPress best practices and should work seamlessly with its APIs and plugins.

Themosis comes with local and production environments pre-configured in order to facilitate collaboration. Once you register your database credentials and application URLS, you'll be able to define the different environment configurations, making it easy to move between development and production.

The framework guide contains everything you need to know to get started structuring and building your application. The route API docs cover all the conditional tags available with code samples for basic routing methods. Lambé describes the route system as "an enhanced 'if' statement," which is essentially based on WordPress conditional template tags and a closure callback.

The framework includes classes for handling AJAX requests, custom post types, metaboxes, custom fields, taxonomies, options, validation, and more. It also adds a unique set of Helpers which act as framework utility functions that run on the global scope.

Lambé has now separated the Themosis studio from the framework, which can be found at framework.themosis.com. He is launching a Themosis web agency, specializing in WordPress design and development, in order to fund future development of the framework to ensure its future.

The Themosis framework is an interesting option that could be very helpful for new WordPress developers, especially those who are used to using Laravel or those who simply want to structure and organize their code like a typical MVC framework. It provides another avenue for getting started using a structure that may be more approachable for PHP developers who are new to working with WordPress.

Themosis is an open source tool that Lambé decided to share with the community, and it will remain free to use. If you want to contribute to the project or report any issues, the framework can also be found on GitHub.

17 Oct 2014 10:27pm GMT

WPTavern: Watch The Q&A Session Between Matt Mullenweg and Om Malik From WordCamp Europe

Some of the sessions recorded at WordCamp Europe are now available to watch on WordPress.TV. The rest of the sessions will be added in the coming weeks. Included in the first batch of videos is the question and answer session between Matt Mullenweg and Om Malik.

The session is an hour long and includes Mullenweg's thoughts on the current status of WordPress, the media library, and what the platform may evolve into. One of the questions asked during the session is the role of women in the WordPress ecosystem.

At the 47 minute mark, you can hear the infamous "we love women" comment from a member of the audience. Mullenweg responds with "come onnnnn" with applause from the audience. Helen Hou-Sandí, who lead the release of WordPress 4.0, explains why saying "we love women" can cause unintentional destruction.

Near the 53:40 minute mark, Mullenweg is asked, "How much should WordPress businesses be contributing to WordPress and involved with the project?" This is the question that prompted the 5% figure and his post, Five for the Future.

This is a great session filled with information related to WordPress, Automattic, open source in general, and the future of the platform. If you attended the session live or watched the video, let us know your thoughts in the comments.

17 Oct 2014 6:36pm GMT