Bootstrap, from Twitter
Bootstrap, from Twitter -
Blogs · @wyome
Tagged css3 · everything
Bootstrap, from Twitter -
#CSS Font Stack - The long awaited CSS font stack resource. -
RT @bkmacdaddy: Animation With CSS: It's Easier Than You Think -
Clients often expect websites to look identical across all browsers and devices, but designers and developers struggle to explain why this is technically impossible and strategically unwise. The piece identifies technical barriers—different vendor implementations, browser plugins, user preferences, and screen sizes—that make pixel-perfect consistency unachievable, and argues that pursuing such uniformity wastes resources on code hacks, sacrifices usability, and prevents innovation. Instead, the focus should be on functional consistency and allowing graceful degradation so users on newer browsers experience enhanced features while older browsers receive a stable, working baseline.
The future of CSS layouts
@DesignerDepot You sure that link is correct?
This is documentation for Masonry, a JavaScript library that arranges elements into an optimal grid layout where items of varying sizes fit together efficiently, like a brick wall. The library can be installed via download, CDN, or package managers, and initialized through jQuery, vanilla JavaScript, or directly in HTML using data attributes. Configuration involves defining a container element with child items sized by CSS, then specifying options like item selectors and column widths to control how Masonry arranges them.
Smoothness in web animations depends on consistent frame rates rather than high absolute fps—true 30 fps is preferable to 60 fps with dropped frames since users perceive jaggedness. The article provides techniques for improving animation performance through GPU acceleration, CSS transitions, proper DOM interaction patterns, and profiling strategies that identify bottlenecks in JavaScript and browser rendering cycles. Key optimization tactics include caching DOM nodes, batching DOM reads and writes, using CSS transforms instead of position changes, and leveraging requestAnimationFrame for JavaScript animations.
A tutorial on creating speech bubble UI elements using pure CSS techniques without images or extra markup.
The `scoped` attribute on HTML5's `<style>` element limits CSS rules to only the parent element's subtree, enabling styled content to be syndicated across different pages or embedded as widgets without affecting the receiving document's styles. Although no browser supported it at the time of writing (with Chrome Canary beginning experimental support), the feature faced a significant adoption barrier because non-supporting browsers would apply scoped styles globally rather than ignoring them gracefully, making widespread use impractical until cross-browser support materialized. A jQuery polyfill existed as a workaround for most browsers, though the author questioned why the spec didn't create a new element type instead of an attribute for better backwards compatibility.
StackLayout - A flexible width, component based CSS layout system -
This article evaluates different CSS techniques for hiding content visually while keeping it accessible to screen readers, examining the specific failures of each approach: text-indent fails with right-to-left languages, collapsed positioning doesn't work with Apple's Voice Over, absolute positioning causes unwanted page scrolling when focused, and the clip method triggers unexpected scrollbars in Webkit and Opera browsers. The author proposes a hybrid solution combining absolute positioning, clipping, and minimal dimensions to avoid these pitfalls while maintaining both screen reader accessibility and proper focus behavior.
I can't summarize this text because it's not a saved article—it's a comment or forum post responding to someone else's argument about browser feature support. The text presents a reader's counterargument to a piece defending IE9's lack of certain web features, listing specific CSS3 and HTML5 capabilities that the commenter believes are stable enough to warrant support. If you'd like me to summarize an actual article you've saved, please share that instead.
An interactive exploration of how typographic scale and rhythm work together on web pages, using Robert Bringhurst's principles as a foundation. The piece explains how to establish a base font size on the body element, set appropriate line-height to create vertical rhythm (symbolized as λ), and then compose all other type sizes in relation to this baseline using the em unit, allowing the entire design to scale proportionally. Draggable interface elements let readers experiment with different typographic scales (traditional, Fibonacci, Modular) and see how subheadings can be adjusted while maintaining the vertical grid that keeps text aligned to consistent rhythm.
HTML elements like `<html>`, `<head>`, and `<body>` are optional in source code because browsers automatically generate them, meaning they can still be styled with CSS even when absent. The author demonstrates this by creating a webpage with zero HTML content, instead delivering all styling through an HTTP `Link` header (defined in RFC 5988) that references an external stylesheet, which generates and styles the implied elements using CSS pseudo-elements. While these techniques are clever explorations of browser behavior, they're impractical for real websites due to quirks mode rendering, validation failures, and lack of widespread browser support for the Link header.
A collection of creative CSS3 typography experiments demonstrating innovative text styling techniques for web design.
Lettering.js is a jQuery plugin that wraps individual letters in HTML spans, enabling designers to apply CSS styling to single characters rather than entire words or lines. This solves the limitation of CSS, which lacks granular typographic control, and allows for effects like custom kerning, decorative letter treatments, and editorial design techniques that would otherwise require images or workarounds.
Browsers apply different default styles to HTML elements because the HTML standard specifies only content structure, not presentation, leaving each browser to implement its own baseline styling—resulting in elements like headings and paragraphs rendering at different sizes and margins across browsers. The article explains how this fundamental inconsistency causes layout problems and demonstrates several approaches to solve it, from manual resets to comprehensive frameworks like YUI Reset and Eric Meyer's Reset, which systematically override browser defaults to create a predictable foundation for consistent cross-browser design. While a CSS reset requires additional work to re-style elements afterward, establishing this uniform baseline prevents the cascade of layout issues that arise from seemingly minor rendering differences.
The author reconsiders their initial dismissal of CSS frameworks after experimenting with Blueprint, 960 Grid System, and YUI 3 Grids for wireframing projects. While acknowledging the valid criticisms about non-semantic class names and code bloat, they argue that frameworks provide genuine practical value by offering solid foundations that save time, particularly for quick projects, prototypes, and teams where consistency matters more than perfect code purity. The author concludes that frameworks are a reasonable tool when circumstances call for them, even if custom, semantically pure CSS remains the ideal in many situations.
This isn't a saved article—it's a cookie consent notice explaining different categories of tracking technologies. The page distinguishes between necessary cookies (required for basic functionality), functional cookies (for features like social sharing), analytical cookies (for traffic metrics), and advertisement cookies (for personalized ads and campaign measurement).