As many of you know, I’ve recently launched a new weekly newsletter called Web Tools Weekly. In addition to providing a weekly, categorized list of tools for front-end developers, most issues begin with a brief tip or tutorial that usually includes code examples that have syntax highlighting.
The method I use is based on a suggestion given to me by Joshua Clanton, who writes the very cool A Drip of JavaScript newsletter. When I asked him how he embeds code in his, he directed me to a page on MailChimp’s blog along with a GitHub repo.
In recent months, I’ve come across a number of links discussing the issue of Search Engine Optmization (SEO) for single page apps or similar complex JavaScript-driven web apps.
This certainly should be a key concern for anyone building these types of projects. So below I’ve compiled two categories of links related to this topic.
Buy Now for $2 (via PayPal) This e-book is a collection of articles published here on Impressive Webs. The first 10 articles are basic tips and concepts, while the remainder are tricks and techniques of varying levels. You can buy all 28 articles as a single easy-to-read PDF e-book for just $2. The e-book has […]
In addition to the unique property/value pairs that CSS offers, there are also a small handful of language-wide features that can come in handy, including a few that are brand new in the spec.
These often go unnoticed, especially by beginners, because when CSS properties and their possible values are discussed (in tutorials, books, or even in the spec), these features are usually omitted for brevity.
Off and on over the past few months, I’ve been planning and working on a new project that is now ready to launch: Web Tools Weekly, a (you guessed it) weekly email newsletter targeted at front-end developers, with a special focus on tools.
This is not, by any stretch of the imagination, a unique idea. As many of us know, there are lots of options in the recent web dev newsletter boom.
It should be a coder’s goal to make sure that every character in every line of code serves some purpose.
The quality of code is not dependent on good form, prettiness, or theoretical benefits. Code should solve problems.
HTML5 lets you omit closing paragraph tags and closing tags for list items. Some cringe at the thought of this, but it’s perfectly valid code. So if omitting extra tags helps your code become leaner and faster, then you’re solving a problem and that makes it good code.
Let’s say you’re viewing different pages in your browser, and in the midst of your browsing you decide to visit a Google’s home page.
The cursor is blinking in the search field. This means the cursor has been automatically focused into the search field, either via JavaScript or using HTML5’s autofocus attribute.
At the recent W3Conf Nicolas Gallagher explained that although pseudo-elements have helped us add decorative content to our pages while keeping our HTML clean, this has led to some maintainability issues.
Developer tools can help to some degree, but oftentimes dynamically added content like pseudo-elements or extra elements added via JavaScript are initially harder to track down.
As Nicolas pointed out, the far-future improvement in this area is the Web Components spec, but I think this is something we can improve on right now.
On March 2nd and 3rd, I attended and had the privilege of speaking at jQueryTO, Canada’s first ever jQuery conference. It was a really cool experience, and was especially cool because I finally got to meet in person certain developers that I’ve respected from afar for some time, including Darcy Clarke (who organized it), Paul Irish, Addy Osmani, Alex Sexton, and Adam J. Sontag.
If you’ve been reading this blog for awhile now, then you know that I have little, if any, business speaking at a JavaScript conference. So I tried to keep things fairly simple for myself and proposed a talk where I could focus largely on CSS.
To keep up with the latest news in tech, design, and development, I have a subscription-only email address that I use to subscribe to various industry newsletters.
I obviously can’t read everything in all these sources, but I skim all of them regularly, and read many of the links they refer to.
As many of you know, I’ve recently launched a new weekly newsletter called Web Tools Weekly. In addition to providing a weekly, categorized list of tools for front-end developers, most issues begin with a brief tip or tutorial that usually includes code examples that have syntax highlighting.
In recent months, I’ve come across a number of links discussing the issue of Search Engine Optmization (SEO) for single page apps or similar complex JavaScript-driven web apps.
In addition to the unique property/value pairs that CSS offers, there are also a small handful of language-wide features that can come in handy, including a few that are brand new in the spec.
Off and on over the past few months, I’ve been planning and working on a new project that is now ready to launch: 
It should be a coder’s goal to make sure that every character in every line of code serves some purpose.
Let’s say you’re viewing different pages in your browser, and in the midst of your browsing you decide to visit a Google’s home page.
At the recent W3Conf Nicolas Gallagher explained that although pseudo-elements have helped us add decorative content to our pages while keeping our HTML clean, this has led to some maintainability issues.
On March 2nd and 3rd, I attended and had the privilege of speaking at 
To keep up with the latest news in tech, design, and development, I have a subscription-only email address that I use to subscribe to various industry newsletters.
