I have been an avid Brackets user since 2013. It’s a free, lightweight, open-source code editor that is perfect for beginners and experienced developers alike. One of my favorite features of Brackets is the number of extensions available to allow users to tailor their development experience. Today, I’ll share which extensions I use to make my job as a front-end WordPress developer easier.
Since we’ve been posting about it constantly for the last month, you probably already know that we hosted our first webinar this past Monday. Brad talked about why enterprise companies should use WordPress, and detailed some of the basic misconceptions business owners have about WordPress.
In case you missed it, we have a treat for you!
You can watch it right here and now:
A few highlights:
“A lot of the reasons that WordPress has become so popular–there aren’t really restrictions. You can use it for whatever you want.”
“A lot of people think WordPress can’t handle a large load of traffic. It’s not true. WP can handle millions and millions of hits. Really, the only limitations of what WordPress can handle depends on what your hosting can handle.”
“WordPress is a platform that people can understand how to use. Your team will want to use the tools you provide them and manage the content and manage the media because WordPress makes it easy…If your platform is hard to use, your team won’t want to use it.”
Thank you to all that attended and to those who sent us questions!
We’ll be hosting another webinar, featuring our Director of Products and Pluginize go-to, John, so keep an eye out for more details on that in a few weeks!
Have more questions about the above webinar or topics you’d like to see addressed during one of these? Drop ’em in the comments and let us know! We want your feedback!
We’ve covered the reasons why using transients (and caching in general) can greatly enhance the performance of WordPress sites. I’m offering up what I find to be two compelling solutions for pain points that are often encountered when working with transients–how to create dynamic keys and delete transients in bulk.
I consider myself lucky every morning when I wake up and get out of bed. I remind myself that I am a web developer, and every day is another day to make the internet better. I hope you feel the same. If you are a developer/designer, lead, project manager, or executive, you play your part in making the internet better, too. With these parts we play, we spend a good amount of our day in front of computers. Our time tends to be pretty sedentary. Some will counteract that with standing desks, but that is still not a lot. We need to take special considerations to stay healthy so we can keep doing what we do!
Here are a few ways I’ve found help me make my health a priority, while still working all the while.
Please note: I am not a licensed professional or “expert” on the topics that follow. Take the presented information as general information and things to consider.
We’ve helped a variety of large companies, many of which are household names, make the move to WordPress. Our experience and passion for WordPress leads us to believe that open source software is the future for enterprise companies.
There are a lot of questions about how this works–how WordPress can scale, why WordPress is the best choice over, say, a proprietary content management system that they’ve had built in-house, and what WordPress is really capable of. We’ve also encountered a lot of misconceptions about what WordPress is and what it can do.
On July 18th, our CEO, Brad Williams, is going to share why WordPress is the best choice for enterprise companies, and talk about our experiences working in the enterprise space. He’s going to share some myths and talk about the realities of WordPress for large, international companies, too!
Whether you’re thinking of bringing your company site over to WordPress, or you’re part of the WordPress community and want to know what concerns enterprise company executives have about WP, you will definitely want to get in on this.
This webinar is completely free, and we’d love for you to join us:
If you have any questions you want answered, please tag them on Twitter with #WebDevinar. Whatever we don’t get to during the Q&A portion of the webinar, we’ll answer in a follow up post.
We look forward to seeing you there!
Options are great. It’s always a wonderful thing to have options. I think most of us likely grew up being told that having options was important–for instance, fallback options, or when Plan A falls apart. Sometimes, though, too many options can create headaches and confusion. Maybe each new choice sitting in front of us looks as appealing as the one which came before it and in a mad dash to make the right choice, we create some kind of Frankenstein’s Monster combination of all of the choices.
We all know how that story turned out, right?
Threw a girl into a pond.
Please don’t throw a girl into a pond.
Instead, let’s focus on one choice– Visual Composer — and how we can tame this beast to turn it from a Frankenstein’s Monster into a Frankenstein’s Masterpiece.
Optimizing your development workflow is one of the most important things a developer can do. Being able to leverage your tools quickly and efficiently lets you spend your time working on actual development–instead of fighting your tools or doing boring, repetitive things.
A few months ago, I wrote a blog post about getting set up with the command line and starting to use some of the tools that are available. If you have not read that post yet, I’d recommend doing so, or at least glancing through it before getting into this post.
The main reason I built
vv was because I was tired of manually setting up sites on VVV for every new project. Most features inside of
vv were built to automate something that I or someone else did manually with every new project. This mindset is important to get into when developing; it’s why we learn keyboard shortcuts, why we use things like theme frameworks, and even why we use WordPress. Doing things over and over again is boring.
“Please, no matter how we advance technologically, please don’t abandon the book. There is nothing in our material world more beautiful than the book.” –Patti Smith
There are many great pathways to glean new information out there, whether it be on the web or in a class. Your mileage may vary depending on your learning style or the topic at hand. With the tech industry, evolution often occurs at a faster rate than print media can keep up.
Still, sometimes a good ol’ print version of what you need comes along that earns its place on your bookshelf. Maybe it got there after you heard it mentioned for the tenth time. Maybe it is the book you always find yourself lending out to someone when they want to dip their feet in to a new niche (regardless of the evolution of name-your-favourite-framework-here.js). Maybe it is the book that someone leant to you at a crucial step of your learning. There are brilliant books for front-end developers out there–and they are definitely worth looking over.
A single book won’t be able to provide you with the breadth of information necessary, especially with today’s multi-dimensional coding ecosystems. Often, books cite wonderfully curated online resources so you are able to use their foundation as a jumping off point for knowledge expansion.
Another week, and another awesome dev joins the WDS team!
Meet our newest front-end developer and designer, Jo Murgel. A little bit more about Jo:
Jo Murgel comes from a design and illustration background. Upon graduation from Boise State University (go Broncos!) he quickly made the turn from print to digital media, and from there web design and development.
His father’s education took them all over the country from Montana to New York, from there to North Carolina, and then onto Idaho. It wasn’t until his own travels took him through Ohio and Pennsylvania and New Jersey that he was afforded the time to pursue and hone his development skills and really latch on to WordPress as his platform of choice.
When he’s not designing or developing, you can find him out and about with his camera taking photos or at home with his three cats (Dilly, Pickles, and Little Man Simon Rumbleblaster) and two rabbits (Pixel and Monster) in a Netflix-and-chill situation with his fiancée, Brandi.
You can follow Jo @jomurgel, and find his Github and more on his team page. Please join us in welcoming the latest team member and remember, we’re still seeking back-end developers to join our team. Come join the WDS party!
I think we can all agree that unit testing is pretty neat.
An automated system for checking if your code changes break any functionality is almost magic, and if you aren’t sure where to get started with it, you should read my previous post Unit Testing Your Plugins.
If you’ve spent some time on Github, you’ve probably heard of TravisCI, a continuous integration service that automatically runs tests for every commit and pull request on your repository. It’s super cool, very easy to set up, and free for open source projects.
One of the best parts of TravisCI is its ability to run your tests in multiple environments. In one go, you can test your plugin on several versions of PHP and WordPress and catch edge cases you might run into in versions you don’t develop on.
Our plugin generator by default sets up a TravisCI configuration so without any work on your part you can have your plugin tested on multiple environments for every commit. The one issue with TravisCI is you can’t easily run these tests locally, so you won’t have an idea of if your tests will run properly on all environments until they are pushed to GitHub.
Dockunit is like a offline TravisCI. It uses Docker to create local compartmentalized testing environments so you can easily run your tests on whatever setup you want. Docker is a container based system for running applications bundled with their dependencies. I’m doing a poor job of explaining it fully, but it’s really interesting and if you like virtualization and dev ops stuff you should take a look.