Flexbox has become one of the most popular tools for creating website layouts. Susy is another layout tool that has gained popularity with the Sass community over the last few years.
Many developers I’ve spoken with are unsure which tool is best for creating layouts for their websites. Some feel that flexbox is powerful enough to handle all of their layout problems. However, they are unsure whether to learn it because of its confusing syntax. Others feel that Susy is much simpler and prefer its simplicity to flexbox.
“Thanks for helping to organize Devfest.Asia!” Someone said to me as the largest community-organized web developer festival in South-east Asia draws to a close. “I really enjoyed it!”.
I should be happy when I hear things like this. Right? Well, I thought so too. But I didn’t feel it.
Deep down inside, instead of happiness, I feel a stab of pain whenever someone thanked me for organizing Devfest.Asia.
Strange, isn’t it? I couldn’t explain this feeling for a long time.
Now, I finally understood what has happened, and how it affects my life. I’d like to share this story since it might affect yours positively too.
Note: This would be an interesting read if you are someone who constantly feels you’re not good enough, or you haven’t done enough. For the rest, you can stop reading here now.
One of the most asked questions I get about migrating from Bootstrap to Susy is this: “How do I build a Bootstrap-like grid with Susy?”
I feel that if I answer this question, I’ll be leading you down a path that I don’t agree with. That’s why I hesitated with answering this question previously.
In this article, I want to tell show you why this is a wrong question to ask, and what to do instead.
What files should you push up into a Git repository? What files should you ignore? These are two questions that plague most beginners when they’re learning about Git.
We’re going to explore these two questions in this article so you’ll never have doubts on whether you should ignore a file in the future.
Template Engines are tools that help us break HTML code into smaller pieces that we can reuse across multiple HTML files. They also give you the power to feed data into variables that help you simplify your code.
However, with Node.js, we can now harness the power of template engines easily through the use of tools like Gulp.
That’s what we’re going to cover today in this chapter. We’re going to find out what template engines are, why we should use them, and how to set one up with Gulp.
Gulp is a tool that helps you out with several tasks when it comes to web development. It’s often used to do front end tasks like:
- Spinning up a web server
- Reloading the browser automatically whenever a file is saved
- Using preprocessors like Sass or LESS
This is not a comprehensive list of things Gulp can do. If you’re crazy enough, you can even build a static site generator with Gulp (I’ve done it!). So yes, Gulp is extremely powerful, but you’ll have to learn how to use Gulp if you want to create your own customized build processes.
So that’s what this article is for. It helps you get so good with the basics of Gulp that you can begin exploring everything else for yourself.
Last week, we set up a simple gulp task to convert Sass into CSS. We also touched on how to watch the
styles.scss file for changes and how to reload the browser automatically with Browser Sync.
In this article, we’re going to dive further into the
sass task to find out how to watch more than one file for changes, and how to customize options for the plugins that we have used.
Let’s get started.
Gulp is a build tool that helps you automate your development workflow. In this article, we will dive deep into Gulp to show you how to use it effectively to create a simple workflow.
Let’s get started.
Choosing to use one tool over another is one of the largest challenges developers face. Regardless of what you’re choosing, be it a code editor, a framework, or even a build tool. It’s never an easy decision.
When it comes to build tools, the two most popular options right now are Grunt and Gulp. But are these the only two you should choose from? If not, what other choices do you have?
Let’s answer this question.
Most tools that help you automate your workflow require the use of the command line. Hence, the first obstacle you have to overcome is getting comfortable with the command line.
But the command line is scary.
Playing with it feels like you’re dismantling a bomb that could go off any moment. One wrong move and that’ll mean the end of your life, and your computer.
I didn’t dare to touch it when I first began to code. I felt that the command line was a tool that only experts could use.
However, as I got to know more about it, I began to realize that the command line isn’t scary at all! It’s incredibly safe, even for beginners, and anyone can use it to help improve their workflow.
In this article I’ll show you why the command line isn’t that scary, and how to start to get comfortable with it.
Ready to go? Let’s begin!