Unless you’ve been under a transpiler-sized rock for the past five years or you’re an absolute beginner to front-end coding, then you’ve probably heard of npm.
Maybe you’ve clicked through to the GitHub repo of a tool of some kind, and you noticed the installation instructions had a couple of different possibilities, including something like this:
Since July 2013, I’ve curated a weekly newsletter called Web Tools Weekly. It’s been my primary side project which, admittedly, has taken time away from this blog. I’m planning to be more active on Impressive Webs again this year, but I felt it was time for a fresh new design for the newsletter. The new design launches in this week’s issue.
The redesign was done by a local friend of mine, Priscilla Di Carlo. Although I could have put something together myself, I don’t consider myself a true designer, so I preferred to pay someone to give it a fresh look. Priscilla is mostly a print designer, but since this is email design, I feel like that’s an advantage more than anything.
One thing that’s common in development blog posts and documentation is the use of HTML’s
<code> tags to mark up code snippets inline and in large blocks (the latter of which is usually done along with
One of the problems that occurs with styling of
<code> tags, however, is when they’re used inline inside of links (or
The presentation at CSS Dev Conf wasn’t recorded, but the FITC version was (without the Octopus, though!). So below you’ll find the video of my talk, the slides, and links to all the resources and features that I discuss in the presentation. I’ve also included JS Bin demo links for most of the features. Enjoy!
A couple of years ago I wrote an article for a company called Thinkful on CSS positioning, which also included a screencast that I hosted on my ImpressiveWebs YouTube channel. The video was “unlisted” but I’ve now made it public, and since some time has passed I thought I would post the video here.
It’s pretty basic stuff for most experienced CSS developers, but if anyone wants a quick primer on CSS positioning, this should be a good guide. The video is embedded below and I’ve summarized the content here in this post.
On Tuesday, April 14, I had the privilege of speaking at FITC Toronto 2015, a technology and creativity conference that features events all around the globe, many of them in Canada. It was my second talk ever, and it seemed to go over pretty well. This was a 4-track conference, so it was nice to see a packed room with standing-room only (or so they told me — as you can see from the video below, those lights blind the speaker to what’s going on in the room!).
My talk was focused on the tools explosion that we’ve seen in the front-end development industry in the past 5 years or so. If you’ve been following my tools newsletter for some time, then you would have seen some, if not most, of the stuff in the talk. But I did go in depth on a few of the tools that I featured, so there should be something new in here for most front-end developers.
I love my job at SitePoint—it’s the best job I’ve ever had. As long as SitePoint still wants me working for them, I hope I can continue to help them put out better and better content for front-end developers.
I’ve rejected or sent back for editing quite a few articles since I’ve started my editing duties. Many of those rejections suffered from the same problems. So for this post, I’ve put together my thoughts on what I think makes for a good web development article or tutorial.
The subscriber count has grown to almost 10,000 as of this writing, and that number is growing by about 70 each week. For the past couple of months, I’ve been displaying the subscriber count on the home page, and manually editing it every once in a while.
A common UI pattern for a range slider is to allow the user to move the slider and display the value of it somewhere on the page, changing the displayed value as the user moves the slider.
I think the expected behaviour in such a case is that the value should display instantly, as the user is moving the slider, rather than the page waiting for the slider to finish moving before the displayed value is updated. I suppose there could be cases where you prefer a delay over instant results, but I think the expected behaviour is to display the results instantly.
As you’ll see in the videos below and in your own testing, the behaviour of the
input event compared to the
change event is not exactly the same in different browsers when applied to a range slider.