It’s the Monday post-Thanksgiving. As you continue to recover from your food coma, check out the Cyber Monday deal being offered over at AppPresser: 25% off!
If you have a WordPress-based business, AppPresser is the quickest and easiest way to convert your WordPress website into a mobile app with ease. AppPresser gives you the tools to put your business in the palm of your customers without straining your financial or technical resources!
There are several different packages available; get started with the basics or customize something more complex. You get to determine what works best for you and you have full control of the end result. If you haven’t used AppPresser yet, you can always start by checking out the free plugin.
Use the code ‘CyberTurkey’ at checkout to get 25% off whatever you’d like, and rest easy knowing that your business will be more than ready for the new year. Start building mobile apps with AppPresser today!
In my freelance days, I remember sitting on the worn leather seats of my Panera office, listening to the cries of small business owners tell me about how much money they had wasted on the programmers before me. Like a bad couples counseling session, they would vent about how they felt taken advantage of–how they had spent hard earned money and the ten mockups they requested still weren’t right, or how the developer said he wouldn’t make it work in IE7 so that they could view it at their job. When I first began my “Bad Websites Anonymous” sessions, I would think “How could they take advantage of this person?!”
Later, I learned that the problem wasn’t always the developer; often it was a misunderstanding due to a client’s lack of code knowledge. After explaining that Microsoft doesn’t even support Windows XP and IE7, and that turning each mockup into a functional prototype could take at least five additional unpaid hours, the light would come on and the apologies would flow. If you’re a future website owner or prepping for an online rebrand, you don’t have to know how to build your own website, but you should at least know a little bit of code. Just in case you still don’t believe, here are a few reasons why everyone should:
The quest for knowledge is never-ending. We all want to be masters in our respective fields, but we also know that there is, especially in the tech universe, an ever-expanding number of things to bone up on. So, how do we get there? How do we learn every single thing we need to know? Let’s find out!
The holiday swing is getting kicked off right with WordCamp Saratoga Springs this weekend on November 21st! Damon will be there; he is one of the organizers and kicked butt to make this happen!
Although I find it hard to believe that any of our regular readers are unfamiliar with WordCamp (come on, now!), for those of you that are completely green: WordCamps are events held all over the world where WordPress nerds unite to share their skills, insights, and learn a whole lot from a bunch of other smarties.
We picked out a few sessions that especially caught our eye, although we know they are all going to be amazing. If you’re going, make sure to grab Damon and say hello!
Designers face many challenges that are often discussed and pontificated on, from Grunt to typography. What’s worth emphasizing is what happens before and after the design is created. Design isn’t just about one thing, and in order to be a designer of any consequence one must be able to sell.
It is well-known that WordPress is one of the most popular Content Management Systems available for building and maintaining a website. While a big part of that success is due to the ease-of-use, another big part of that is the wide variety of themes and plugins that are available to make WordPress do just about anything you can think of. What gives plugins and themes their true power is the Plugin API, which is a set of Actions and Filters, collectively known as Hooks, that are embedded within the core WordPress codebase. The goal of this post is to demystify the WordPress Hooks and enable you to start diving in and using them.
Your team is cruising through development on your latest project. Your lead developer has his team on lock. The site’s architecture is planned out and they’re slinging CMB left and right. Final designs? No final_v2 or homepage_rev3s in sight. You’ve got them all and your front end devs couldn’t ask for more. Then it happens…a call with your client takes you down a dark path which you never knew existed.
How could this have happened? You planned so well! And let’s be real: you’ve probably made the most perfect project plan you’ve ever constructed…at least since the last one. How could someone have such a disregard for this picture of perfection you’ve worked so hard to achieve?
I’m just going to come out and say it: This will happen (to some degree) with any project your team will embark on. The true test is how you roll with the punches. Here’s a few tried and true ways you can keep your team on track and pivot with the best of them!
“Harmonious” may not be the word a lot of clients and agencies/freelancers would use to describe their relationship. Perhaps many would even land on a more negative term. Why is it that we hear of the bad cases so much more often than the good ones? Are designers and stakeholders simply destined to be nemeses, playing an eternal game of tug-of-war over button placement? Are developers and clients set to battle over feature bloat until the end of time? Personally, that doesn’t sound fun or productive to me. I’d like to propose a better way of doing things. First, let’s get a few misconceptions out of the way.
Out of the box, WordPress has pretty great support for external object-cache implementations. Even its built-in object-caching helps WordPress be more performant and avoids redundant non-performant function calls and DB lookups.
One of the challenges we have faced at WebDevStudios is the way WordPress handles including/loading an external object cache and determining whether the default implementation is used. I won’t go into all the details, but the part we have had issues with is the fact that if there is an object-cache.php file in the wp-content directory, WordPress assumes an external object cache exists and it should not include or perform its built-in object-caching implementation.