WARNING! I use a Mac so these comments and examples are from the point of view of a Mac owner.
Setting up an environment with the required dependencies can be a chore to be blunt. Here’s a rundown of the best approaches to keep these dependencies in place once they’re installed. This is not an article about installation, but what to do once they are installed and maybe a few hot items/points of interest to enhance your experience. As a FRED these days you’ll certainly run into a project that may have node or may use Ruby and knowing how to operate in these environments plus keep them updated can be a huge advantage to you or your team members.
Reading specs is hard. There I said it, but it’s not like it hasn’t been said before by the bajillion other developers out there and today is no different for me. I’ve been doing some writing lately that requires me to conduct research within the actual documentation which brings our work to life. It’s also the content we search heavily for on blogs that help interpret it for us to digest.
As we all know the majority of the Web development community uses Git or Github in some way or fashion. The funny part to the whole story is the fact that most developers don’t even know what version they’re using.
Now, before I get up on my high horse here I’ll preface everything by saying I was in the same boat as the rest of you. Sadly, making sure my version of Git is up to date is the last thing on my mind. Thankfully I’ve grown up since those troubled days and now know the value of keeping Git up to date and using the best techniques to keep it that way.
“Silky Smooth Hopping” is a term coined by Paul Irish at the HTML5DevConf held by marakana on November 5th, 2012. It’s a way to login via SSH painlessly and with ease. You’ll need to know what the Terminal is before you begin, and have some knowledge of basic commands (e.g. listing directories, viewing file contents, etcetera). You’ll also need to know how to create a public SSH key with a service such as Github. What we’re gonna do is really not that difficult –and honestly, I’m no Terminal whiz either so I’ll make sure to hold your hand every step of the way.
In the spirit of discovery and process once again, I set out to ask 1 front–end developer to share his procedure when making stuff for the Web on a Non–Mac machine including a little share from myself for Windows scenarios. We’ll start with the initial set up of the local environment and end with deploying the final product. A special thanks to @remybach for opening up the curtain and sharing his secrets on Ubuntu.
Lately I’ve been curious about units used in #RWD –mostly rems I have to admit. Yes, discussing the correct or preferred values to use in #RWD is a topic that definitely makes me fall asleep, but instead of writing the same post about why ems are good for sizing in #RWD, I thought I would look at why
pt isn’t beneficial when used in a #RWD setting – also due to a recent conversation on Twitter about the lonely
pt. This surely goes for you nasty pixels too, but I’ll keep it to the
pt for today –no pun intended.
In order to run Yeoman properly you’ll require a few dependencies like Command Line Tools for Xcode, Homebrew, NodeJS, git, NodeJS, ruby, RubyGems, Compass, jpegtran, optipng, yeoman global npm module and the most important puzzle piece and part of today’s discussion; PhantomJS.