Group items tagged

var rate87=new rateit(87, "26", "090%") rate87.displaytext("26") 4.5 CSS Gradient Shadow var rate74=new rateit(74, "72", "078%") rate74.displaytext("72") 3.9 CSS Thick Tabs var rate47=new rateit(47, "71", "080%") rate47.displaytext("71") 4 SuckerTree Vertical Menu (v1.1) var rate52=new rateit(52, "60", "074%") rate52.displaytext("60") 3.7 Overlapping horizontal tabs var rate51=new rateit(51, "128", "080%") rate51.displaytext("128") 4 Animated link underlines var rate50=new rateit(50, "78", "075%") rate50.displaytext("78") 3.8 SuckerTree Horizontal Menu <!-- <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xm

CSS Bloom is a website showcasing the best CSS based designs used by Blog's and Online Portfolio's. By providing links, and previews of the best designs, we aim to provide our viewers with inspiration for their websites. If you have come across a design which is missing from CSS Bloom, but you feel should be added, or if you would like to submit your own design, then please use the Submit link at the top of the page. PetrSimi January 26th, 2007 (11 votes, average: 3.09 out of 5) &nbsp;Loading ... Comments (0) | Permalink Blog PetrSimi January 26th, 2007 (11 votes, average: 3 out of 5) &nbsp;Loading ... Comments (0) | Permalink CreativeBits January 26th, 2007

(16 votes, average: 3.88 out of 5) &nbsp;Loading ... Comments (4) | Permalink CSS Bloom is a website showcasing the best CSS based designs used by Blog's and Online Portfolio's. By providing links, and previews of the best designs, we aim to provide our viewers with inspiration for their websites. If you have come across a design which is missing from CSS Bloom, but you feel should be added, or if you would like to submit your own design, then please use the Submit link at the top of the page. PetrSimi January 26th, 2007 (11 votes, average: 3.09 out of 5) &nbsp;Loading ... Comments (0) | Permalink Blog PetrSimi January 26th, 2007 (11 votes, average: 3 out of 5) &nbsp;Loading ...

Tim Berners-Lee, inventor of the World Wide Web and director of the W3C, has said it best: “Anyone who slaps a ‘this page is best viewed with Browser X’ label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network.”

Methodologies including layered development via progressive enhancement, Unobtrusive Javascript, and Hijax ensure that higher layers don’t disrupt lower layers. However, representative testing of the core experience is critical. If you choose to adopt a Graded Browser support regime for your own web applications, be sure your site’s core content and functionality is accessible without images, CSS, and JS. Ensure that the keyboard is adequate for task completion and that when your site is accessed by a C-grade browser all advanced functionality prompts are hidden.

Writing CSS is very much like having sex. Not everyone does it the same way and there is no particular “right” way to do it. I guess for me the similarities actually end there, seeing as writing CSS is something I do every day whereas having sex is…anyway I digress. The W3C have set the standards but beyond this, writing CSS is down to an individual’s preferences. Here are 5 little tips and ideas I’ve adopted in the last 6 months that you can use to make your CSS more streamlined, maintainable and easy to read. Written by Jon Disclaimer: The CSS example files are exactly that. They are not meant to be fully functional CSS documents. Class names in the CSS files are named merely so that you may visualise the document in your head (because there is no accompanying html), not because I condone the naming convention in them.

1) Make a table of contents At the top of your CSS document, write out a table of contents. For example, you could outline the different areas that your CSS document is styling (header, main, footer etc). Then, use a large, obvious section break to separate the areas. Not only does this make your CSS look neater, but when it comes to making quick adjustments to certain areas of your website at a later date, finding the corresponding area in your CSS will be much easier. View Example File 1

3) Isolate single properties that you are likely to reuse a lot If you find yourself using a single property a lot, isolate it to save yourself repeating it over and over again and also enabling you to change the display of all parts of the site that use it. View Example File 3