Over the weekend I rolled out a new “skin” for Impressive Webs, which I think improves the site’s design quite a bit. There’s more contrast, which creates a more distinct experience. And I finally have a logo that I’m satisfied with.
The layout of the site remains virtually the same, so, like I said, it’s not as much of a redesign as a “skinning”. I did change the height of the top navigation bar, and added some new graphics.
What a fantastic idea. I don’t know if he’s the first one to do this, but I think it’s a great way to respond to a number of comments quickly without cluttering the comments section on your blog. Of course, some preparation would be required initially to set up something like that. Or maybe he’s using a plugin? I really don’t know, but I thought it was very innovative and could be a trend that others may follow. It’s certainly a great way to personalize your blog.
If you’re at all familiar with the various methods in use today to embed custom fonts in web pages (sIFR, Cufon, @font-face, etc), then you also may have heard of a font format called EOT. Well, if Microsoft has it their way, EOT will become the standard, allowing web developers — with permission from font vendors — to be free to use virtually any font in a text-friendly manner in their web pages.
So what is EOT, and how has Microsoft pushed to standardize this method? Embedded OpenType fonts are compact OpenType fonts designed by Microsoft for use as embedded web fonts. They are recognizable by their “.eot” file extension. By means of data compression and removal of superfluous data, EOT files are made small in size and include features that protect the fonts themselves from being copied and used in unauthorized ways.
Over the weekend, my wife and I had the privilege of taking care of two of our friends’ children, while their parents had a night out at a local show. When the kids’ mom was showing us a few things around their apartment, we noticed that their daughter’s bicycle had no pedals on it. That was a little peculiar, so we inquired about it.
Her mother said she wanted her daughter (who is about 5 years old) to have her feet on the ground as she learned to ride her bicycle. This would allow her to remove her feet from the ground only for short amounts of time, thus practicing her balance without pedals or training wheels. In this way, she could focus purely on balancing herself, and not worry about trying to do more than one thing at a time.
I’m not really sure where her mom got this idea from, or even if it is any good for learning to ride a bike, but it reminded me of what I personally prefer when it comes to learning new skills in web design or development.
This exhaustive article includes relevant links, best practices, and other useful resources that will enable all web developers to incorporate sound effects into their web projects in a manner that conforms to the latest in standards and best practices.
If you’re looking for a reference that you can bookmark and use for any project where you’re asked to include some type of audio clip into a web page — whether it’s MP3, MP4, WAV, WMA, and more — this is the article for you.
This is the one and only resource you’ll need to assist with all your audio-embedding needs.
Since I started blogging and, more recently, started submitting articles to other sites, I have used a number of different sources of inspiration for generating ideas to formulate articles. I thought I would list a bunch of interesting ways that blogging developers, designers, programmers, tutorial writers and others can come up with new and fresh brainstorms that can lead to new ideas.
These are a mix of methods that I’ve personally used, or that I’ve considered using, so I hope you’ll find them useful. And feel free to include your own methods for generating blog post and tutorial ideas in the comments.
Although this article is specifically geared towards generating ideas for web developers, the methods discussed could also be a basis for other fields of writing.
To my pleasant surprise, although today did not start out as a good day for me, things certainly picked up when I discovered that Smashing Magazine published an article that I submitted to them about a week and a half ago.
I’ll explain a little about my experience, but first, here is the link:
Every week this website gets about 700 unique visits from Google searches, mostly from people searching for solutions to problems with JavaScript and CSS. I’m flattered, and I hope I can continue to publish useful articles that will assist people and help with the exchange of ideas and techniques. One search phrase that leads surfers to my site pretty much every day is something along the lines of “getElementById explorer 7”.
If you type this phrase into Google, Impressive Webs currently comes in at around result 115. Not to mention the fact that the article that comes up doesn’t really address this issue directly. That’s not a very good ranking for that search phrase — yet somehow people are still finding one of my pages through that search.
It is obvious that developers — likely beginners — are having issues getting the proper results when utilizing the getElementById method available in JavaScript, particularly in Internet Explorer versions 6 and 7. And since the users seem to be searching through dozens of web pages looking for a solution to their particular problem, then obviously the pages discussing this JavaScript method are either too confusing or don’t specifically provide a practical solution.
Many aspects of JavaScript code development are taken for granted, and scope is really no different. Of course, in many cases where minimal code is required, variable scope (or function scope) is a non-issue. But if you’re planning to get into larger application development with JavaScript, then you need to understand at least the basics on scope in JavaScript.
Using some simple code examples, I’m going to run through the basics of scope and try to give beginning to intermediate JavaScript developers a better grasp of this very important concept.
Recently, a few blogs and tutorial sites have posted some really good articles on JavaScript tips and best practices, and I thought that was a good topic that could easily be expanded upon. So I put together a list of 10 fairly simple JavaScript tips and best practices of my own.
I tried to include stuff that was not mentioned in those other posts, but I’m sure there is a little bit of overlap. Keep in mind that these are brief tips and recommendations, so I don’t go into great detail about the reasons and such, but I may go into some of them in depth in future articles and tutorials.
In the meantime, please enjoy this list of tips, recommendations, and best practices for JavaScript coding.