You know, we use ad-blockers as well. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf San Francisco, dedicated to smart front-end techniques and design patterns.
Category: Developer’s Toolbox
Check out all of the posts in ‘Developer’s Toolbox’ below. If you still can't find what you are looking for, try searching using the form at the top of the page.
Following the market's demand for minimalistic and consistent UIs, and the growth in modular web development, we tend to pay more and more attention to documentation and the efficiency of designer–engineer workflow with each project we undertake. Also, since the documentation process is often the weakest spot for modern web teams, we're constantly looking for the right tools to help us.
Living style guides help front-end developers transform front-end codebases into well-described pattern libraries with the minimum of effort. But to make them really efficient, we need to choose the proper tools — so let’s have a closer look at what our community has to offer.
Although the syntax might be initially confounding, flexbox lives up to its name. It creates intelligent boxes that are stretchable, squeezable and capable of changing visual order. It provides simple solutions to layout paradigms that CSS has always struggled with: vertical centering and equal heights. Flex items are truly accommodating and a pleasure to work with.
Flexbox truly shines with HTML5 web applications. Most web apps consist of a series of modular, reusable components. You can use flexbox for those bits of layout that induce headaches and that depend on brittle CSS hacks to work. Small modules work very well with flexbox, and you can use floats and other tools for broader sections of the layout.
Suppose your company decides to change its code-hosting provider or you wish to move your own Git repository to a different host. It doesn’t happen often, but it happens. When I had to move a number of Git projects to a new host, it took me quite some time to find an accurate method.
Having made many attempts, and a couple of fails, and carefully reading Git’s documentation, I found a solid and effective way. I thought, then, that every developer would benefit from knowing how to migrate a Git repository to a new host quickly and easily. The most important thing is to make sure that your branches and tags and your commit history are all moved.
In the Web industry, a lot of exciting knowledge and diverse opinions are shared daily. They are delivered in fragments across hundreds of blogs, feeds, Twitter accounts and apps. In addition, the number of topics seems to multiply daily. We are building and designing for moving targets. Technology is constantly forking and disrupting the way we interact and do business. This is our industry, and I love it. I also know it could be better.
Why does finding and reading content have to be so painful at times? We set out to build great (user) experiences, yet our own experience of reading and learning from blogs is not always so pleasant. We end up relying on our peers and trending topics to see what we should be reading. Just knowing how to get a handle on what’s going on becomes a job requirement — more of a distraction than a good use of time when we have project deadlines, among other responsibilities.