Dreamweaver is working with the creators of the de facto javascript framework JQuery to integrate JQuery animations into the Dreamweaver environment on the next version release. It also plans to integrate the JQuery Mobile Project and JTouch into it’s arsenal — a powerful combination.

You can read more about this project, and the new Adobe Edge project here.
http://www.adobe.com/newsletters/edge/january2011/articles/article4/index.html

Wire-framing is one of the initial steps after defining a project’s objectives. There are plenty of techniques and strategies out there pertaining to  approaching this highly creative step, and they all depend on “what you know, and how you apply it” — but we thought this was a great overview and list of ways to get it done from sixrevisions. http://sixrevisions.com/user-interface/website-wireframing/

Web design is a mix of the aesthetics of design, knowing when and where to engage and how to visually guide your audience, coupled with the technology which helps bring it to life. It looks like this conference has a healthy mix of both sides of the equation and has a line up and workshops that can really integrate.

We can all come up with great ideas, look at preexisting work and comment of it — sometimes tearing it to shreds and sometimes praising it… but when it comes down to working together and integrating all the pieces to make a web site come alive to shine, it takes a whole lot more. Not just an understanding of how to bring all these pieces together but the know-how to get it done right and a design sense that encapsulates the experience.

But if your into CSS3 there are some options for borders in CSS3, of which one is border-radius. Both Firefox and Safari 3 have implemented this function, which allows you to create round corners on box-items.

The code for this example above is actually quite simple:
(The example below is an image so all browsers can see it)

<div style=" background-color: #ccc;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border: 1px solid #000;
padding: 10px;" >

These different corners can also each be handled on their own:
(The above example is an image so all browsers can see it)

These are handled by this:
-moz-border-radius-topleft / -webkit-border-top-left-radius
-moz-border-radius-topright / -webkit-border-top-right-radius
-moz-border-radius-bottomleft / -webkit-border-bottom-left-radius
-moz-border-radius-bottomright / -webkit-border-bottom-right-radius

This isn’t anything new A List Apart wrote about this back in 2004, but with page-speed being a concern these days, regarding a faster page load could mean better rankings in Google, and it’s an easy way to optimize a website design.

Below is an example of an on and off state for a button in a single image.

What this image shows is the normal state and the hover state of a button. What we want to do is just add a line of code to your CSS like this: background-position:0px -26px; on the hover state and it will shift the position of the image.

A sprite would be just like this, but contain all or most of your button on and off states, little icons, header graphic, images for your navigation buttons, graphic headers and basically anything that can be ganged up into one image.

Why is this better than a whole bunch of small images ?
Wouldn’t it be faster to load a whole bunch of small images ? Isn’t everyone slicing up images trying to get them to load faster ? Nope! Those are old school techniques that never really got us anywhere (so excuse us for mentioning something that you already know, but it’s just a healthy reminder! and since Google and page speed have been mentioned a lot in the web design and web development news lately — and having better rankings involves faster page load speed) So loading a bunch of small images really just fool the eye to make it look like the page was loading faster by loading bits and pieces all over at once. Each one of those images is a separate HTTP-Request, and the more of those, the less efficient your page is. So in short… reducing the number of HTTP requests has the biggest impact on reducing response time and is often the easiest performance improvement to make.

If you want to check a site and see how you can create a sprite from the existing website design — a good choice is SpriteMe — it will open up an overlay over the right side of your browser and help you make a sprite.

Here’s the skinny on @font-face design and implementation:
Supported browser Versions Include: IE V.5+, Mozilla/Firefox V.3.5+, Safari V.3.1+, Opera V.9+, iPhone V.3.1.
But this is true only if you are including .TTF, .OTF, .EOT and .SVG font formats… so you should also always include common fonts and a default font.
h3 {
font-family: yourNameForTheFont, curlyQ, arial, helvetica, sans-serif;
}

Including all those different font types, making your fonts visible to the widest possibe audience might seem daunting but font squirrel has a fine solution. Font Squirrel will generate the fonts you need to upload so it can work across all browsers and platforms:
http://www.fontsquirrel.com/fontface/generator

Because of font licensing concerns, web designers cannot simply embed any font on your website. Your best bet is to get a free font. There are lots of great free fonts out there, and lots of sites have lists of free fonts that you can use with @font-face. One very good free font site is fontex.org.

Below you will find a link that explains all the steps necessary to make @font-face happen
http://blog.themeforest.net/tutorials/how-to-achieve-cross-browser-font-face-support/

A nice resource for web design is this 30 beautiful and free fonts you can use with @Font
http://designlovr.com/30-beautiful-and-free-fonts-you-can-use-with-font-face/

An HTML and CSS framework that allows website designers and front-end developers to create forms more easily.
Did you use to spend a lot of time aligning fields and calculating margins and paddings in a quest for a perfect form? No more!
http://www.formee.org/

While at the same time — Mashable’s HTML5 vs. Flash Debate POLL is still churning out results below:

It looks like , so far over 18 thousand people have voted and the results seem quite rational:
Flash will still be an important part of rich media playback and creation. HTML5 will be the choice for many things across the web – just as jQuery and java-script libraries have recently revolutionized how information can be conveyed on the web. It just makes sense that it can all work together

http://mashable.com/2010/05/01/apple-adobe-poll/
Apple: HTML5 is the future of the web 30.7% (5,696 votes)
Adobe: Flash will still be an integral part of the web in the future 54.7% (10,132 votes)
Neither side is completely right 14.6% (2,706 votes)