Eugene Fedorenko is Designing, Writing, Reading, and Traveling
Published at Wildbit
A few weeks ago on our annual Wildbit retreat we had a group discussion on what works and what doesn’t in our internal process. A few developers mentioned the same problem — a lack of shoptalk with their peers when working remotely. They came up with different solutions, from participating in local meetups to weekly lunches with other developers, but it reminded me of a time when the same problem was very acute in our design team.
Published at Wildbit
A little over a year ago, we had 4 marketing websites built with 4 different frameworks or CMSs, and it was a mess. As the team had grown, publishing became a nightmare — nobody really knew how to access or update any specific page or a part of a website. We had some work to do. Within a few months we researched, picked, and migrated to a single CMS; moved marketing websites to a single hosting platform from multiple scattered services; and created a library of modules that is reused on all of them. This massive project isn’t completely over yet, but enough time passed both to confirm that we made a right choice and to see some of its issues.
Published at DeployBot
While working on a new Wildbit website last week I spent some time tweaking its performance. Caching CSS, JS, and images for a long period of time is one of the most important things you can do to create a fast loading website. It’s relatively easy to configure on most web servers, but comes with a downside — you’ll need to invalidate cached files whenever they change.
Published at Beanstalk
Today we’re happy to introduce an enhanced and more useful dashboard. Our team uses Beanstalk every day and we felt like the current version needed some love and some key features. And you — our customers — told us the same thing.
Published at DeployBot
This guide explains how to launch a website powered by Craft CMS with a proper development environment and workflow behind it. You’ll set up a local development environment, put Craft theme and config files under version control with Git, create and configure a new DigitalOcean droplet, install Craft on it, and then deploy your theme and configs to a live website with DeployBot.
Published at DeployBot
This guide explains how to compile website assets with Build Tools during deployment. We’ll use Grunt as an example, but everything below can be applied to Gulp or any other Node-based task runner as well.
Published at DeployBot
Have you ever avoided some parts of your website or application just because they are not up to your standards or just got old and dusty? Well, I certainly have! Lately I’ve been looking for excuses to not add any more servers to environments just because choosing a server type was kinda embarrassing:
Published at DeployBot
Today we’re introducing a new dashboard that provides more information and is easier to use than ever before. The old one was getting the job done (most of the time), but was inelegant, missed data critical for understanding recent events, and was pretty hard to scan and digest. After talking to our customers and seeing how we use it ourselves we decided to start from a blank slate and redesign it instead of applying UI band-aids.
Published at DeployBot
Announcing two exciting design improvements that will save you time when setting up and deploying to your servers.
Published at DeployBot
If you have a sharp eye you may have noticed that some things changed in DeployBot this week. We cleaned up and refreshed the design a little bit, so now it’s sparkling and ready for some new amazing features. Below I will go through what we changed.