Type study: An all CSS button This is part of a series of guest posts covering tips and tricks for working with fonts on the web. Today’s post was written by Dan Cederholm of SimpleBits. A few years ago I gave a talk about why a button made a great place to bring in type from a branding element (such as a logo). My point was that if the type in your logo was an image, and stylish buttons were also often images, then why not align the fonts in both to bring some cohesiveness to the typography. This was probably four years ago, and we’ve come a long way since. The button is also a great place to showcase many of the new CSS3 properties in one place, which is another reason I’m particularly taken with buttons at the moment. Let’s build a button, friends. The markup I’m going to use a hyperlink in this example, but the styles we’re going to add could just as easily be applied to a <button> or <input> element as well. <a href="#" class="btn"><span>Press this! Notice the extra <span> element here. Adding the styles And voilà.
iOS Fonts Media Queries OpenType OpenType® is a modern font format developed by Adobe® and Microsoft® to provide users with an accessible and advanced typographic toolset. OpenType improves on PostScript and TrueType just as the DVD trumped the video cassette. When deciding what format to choose, using the latest technology simply makes sense, but let’s dig a bit deeper and explore the ways OpenType makes life easier for typographers and graphic designers. OpenType is Efficient One Style = One File The PostScript format is limited to 256 characters per file. Based on Unicode, an OpenType file can contain up to 65,535 characters or glyphs. As a concrete example of the efficiency of the OpenType format, compare the multilingual PostScript version of FF Meta 1, a package of four type styles, with its OpenType successor. Narrow this example down to a single style (FF Meta Book), and we can see that the glyphs and metrics from several PostScript files are all included in one OpenType file. Mac and PC Compatible What’s Inside?
css-discuss.org Complete Beginner's Guide to Interaction Design Interaction design has its origins in web and graphic design, but has grown into a realm of its own. Far from merely working with text and pictures, interaction designers are now responsible for creating every element on the screen that a user might swipe, click, tap, or type: in short, the interactions of an experience. Newsletter Sign Up Original UX articles Curated Resources Never miss an issue! This article serves as a good jumping off point for people interested in learning more about Interaction Design. What is Interaction Design? Interaction Design (IxD) defines the structure and behavior of interactive systems. Interaction design began the day the first screen was designed to hold more than static copy. Interaction design has evolved to facilitate interactions between people and their environment. Common Methodologies Although interaction design spans myriad types of web and mobile applications and sites, there are certain methodologies that all designers rely on. Goal-Driven Design
CSS Template Layout Module Abstract A grid with four slots defined by ‘display: "aaaaaaa" "bccccdd"’. CSS is a simple, declarative language for creating style sheets that specify the rendering of HTML and other structured documents. This module contains CSS features to describe layouts at a high level, meant for tasks such as the positioning and alignment of “widgets” in a graphical user interface or the layout grid for a page or a window. A layout grid or “template” defines one or more “slots” that an element's content can flow into. This allows elements to have complex shapes and it allows the visual order to be different from the order of the elements in the source document. A ‘::slot’ selector allows elements to be styled differently based on which slot they appear in. Status of this document This section describes the status of this document at the time of its publication. Publication as a Working Draft does not imply endorsement by the W3C Membership. Table of contents 1. Selectors [SELECT] 2. resp 3. 3.1. 3.2. 4.
Responsive Layouts, Responsively Wireframed Responsive layouts, responsively wireframed Made with HTML/CSS (no images, no JS*) this is a simple interactive experiment with responsive design techniques. Use the buttons top-right to toggle between desktop and mobile layouts. Using simple layout wireframes, this illustrates how a series of pages could work across these different devices, by simulating how the layout of each page would change responsively, to suit the context. Responsive layouts? Producing static wireframes to design layouts for websites, web applications and user-interfaces has worked well for a long time. However, this solution creates a new problem: How should we go about the process of designing these variable layouts? Enter, responsive wireframes? The 'wireframes' on this page (which are only very simple, high-level examples) were created with HTML/CSS, and some argue that this is the answer; to design in the browser. So which is better? Traditional wireframes? HTML? So, what's the answer? Just wondering...
Essential considerations for crafting quality media queries CSS3 media queries are dead simple, in terms of their syntax. You’ve got an @media directive, a media type (which you already know from good ol’ CSS 2, like screen, print, all, etc.) and one or more media features (the characteristics we’re testing against). That’s it: @media screen and (max-width:500px) { } There are some additional little syntax details, but this is basically all you need to know to actually make a media query work. Designing web layouts with media queries is a process. This article is just as much for me as it is for you—it can be hard to keep track of all the different configuration variations you can use! How to include your media queries: embedded vs. external There are two ways to include media queries in your site: embed them within a style sheet or include them in a call to a separate, external sheet. Here’s what an embedded media query looks like (pretend that we’re inside a style sheet): @import url(narrow.css) only screen and (max-width:500px); The pros and cons