“ Negative margins don’t show up in the Design View of Dreamweaver. Why are you even checking your site in Design View anyway?
I just had a great idea how coding your site in HTML5 can allow you to utilise a universal print stylesheet.
A great print stylesheet called Hartija is available on Google Code, but it still requires that you alter the stylesheet to hide your header, nav, footer, etc.
If you code in HTML5, and use the <header>, <nav> and <footer> tags, then this can be put in your print stylesheet once and you will not have to change it again:
body > header,
body > nav,
body > footer {
display:none;
}
This assumes that your header, nav and footer are all direct descendants from the body. If you are in the habit of having an outer ‘wrapper’ element then alter the code accordingly.
This will not work in Internet Explorer 6 but frankly, I am past caring about that particular browser!
altfontprev
karldawson via trovster:
A JavaScript bookmarklet that allows you to preview how any website would look if a particular font was not available or a different font chosen. Each font used to style elements on the page is…
ReBlogged from karldawson
I am currently updating my blog to be HTML5 (you probably won’t see the results for a few days while I iron out all the kinks) and came across another benefit to coding in HTML5.
If you author websites you’re probably used to doing something like this:
</div> <!-- end of navigation -->
</div> <!-- end of post -->
</div> <!-- end of wrapper -->
</div> <!-- end of footer -->
Without these little comments, it can be difficult to see what that </div> is for. A major validation error often occurs when you have one too few—or too many—end tags for these divs, and this is known as div soup.
Of course, using HTML5 those closing tags look something like this:
</nav>
</article>
</section>
</footer>
Semantics are extremely useful, not just for making you code machine-readable, but also for making it human readable!
