In case you missed it yesterday, my article, Advanced Sites Deserve Advanced Custom Fields, has been published in the December issue of php[architect]. This marks my first feature-length magazine article!
Page 11 of 14
Today marks one month since I joined #Team10up as a Senior Web Engineer. Before starting the position I was hesitant to switch to 100% remote working, so I’d like to share some of the things I’ve learned and experiences I’ve had over the last 30 days in the hopes that they might help put would-be remote employees’ apprehensions to rest.
I just got back last night from the inaugural php[world] conference in Washington, D.C., put on by the team at php[architect], and thought I’d share some of my thoughts and experiences:
Sadly, I’m not participating in Movember this year. It’s for rather selfish reasons, admittedly (I’m speaking at php[world] in Washington, D.C. this week, which is the largest speaking engagement of my career, and don’t want to be mid-‘stache during the conference), buthat doesn’t mean I don’t want to be involved with Movember. As I won’t be shaving off the beard for some mustache fun this month, I’d like to propose this alternative:
Today is my last day as a developer at Buckeye Interactive.
Beginning November 17th, I’ll be joining the team at 10up as a Senior Web Engineer. That’s after a week of recharging the mental batteries, then four days in Washington, D.C. for php[world]. I’m excited to be joining one of the top WordPress development teams in the world, taking on new clients and new challenges.
Built for the second annual National Day of Civic Hacking, Petition The People leverages the We The People Write API to collect signatures on WTP petitions. Petition The People makes it easy to collect signatures while canvassing or at events, and is built responsively so it looks as great on a phone or tablet as it does the desktop.
The app is targeted at advocacy groups and organizations who might want to draw attention to more than one issue at a time, so organizations are able to create what I named “Campaigns,” consisting of one or more petition. Each campaign has its own unique URL, and users are presented with the body of each petition. After selecting at least one of the campaign’s petitions to sign, a single signature form is presented. This enables a user to sign multiple petitions at once, rather than manually entering their information across several petitions.
At first glance, T-Pro Solutions is a pretty typical marketing site: hero carousel, big banner images on each page, and a whole mess of calls-to-action. There's nothing wrong with a site like this, but they're not always the most exciting to build. T-Pro's site, however, has a little bit of magic under the hood that's worth sharing.
Nathan Driver and Brian Retterer were nice enough to invite Phil Hoyt and I on the inaugural WP Decoded podcast, where we talked WordPress 4.0, WordCamp Columbus, and why “WordPress 101” sessions at WordCamps are a lot like Freshman Orientation.
This week a few people in the office got really excited about the Signals app from HubSpot, which lets you see when your emails have been opened and whether or not links have been clicked in your emails. While it’s extremely useful for marketers, project managers, and others who have a vested interest in knowing you’ve read their emails, I’d prefer to be able to read the email at my leisure without having the sender essentially standing over my shoulder to see if I’ve read it. For most people it’s not a big concern, but it is incredibly simple to thwart if you’d like a little more privacy in your inbox.
I’m working on a site right now that uses the Social Login plugin by OneAll, which is the first time I’ve dealt with users logging into a WordPress account via social networks. The plugin works really well, but I ran into one major issue: new user accounts were being created when matches weren’t found.
This particular project is a BuddyPress site for a fraternity; brothers can log in to see private events, content, and the full roster but the general public can only see the public pages. There’s also a public roster page with basic information about each member (name, graduation year, major, etc.), but those are dynamically generated by listing all BuddyPress members (excluding my team’s accounts, of course). Out of the box, OneAll would create a new user account for anyone who tried to log in, resulting in my mug appearing in the roster right along all the registered fraternity members…yikes!