background preloader

The Ultimate Website Prelaunch Checklist

The Ultimate Website Prelaunch Checklist
Digital Strategy Mobile: The estimated time to read this article is 10 minutes We’ve all been there. After months of development, meetings, conference calls, protracted arguments over typography, photography, colour ways and copy. All of a sudden the site is approved and the client wants it live. Do you think to yourself, ‘I know every pixel on this site inside out’ and put it live? Hopefully not. By no means is this an exhaustive list. Either way, get your team together, get out the red pen and start ticking them off. Copy Checks Check your spelling. If it comes down to a web designer to highlight the smelling pistakes of a copywriter then so be it. Check your tone of voice. Ensure this is consistent across all your pages, that your audience is being addressed the same way throughout the site. Check your details. I’m quite serious about this. Check through any ‘hidden’ copy on site. Make sure you are not going live with any test copy on your site. Check your keywords. Check your titles. Security

CSS Resets Update! Check out CSSresetr for an easy way to test and download the best reset styles for your next design. Using CSS to style semantically meaningful (X)HTML markup is an important key to modern web design practices. In a perfect world, every browser would interpret and apply all CSS rules in exactly the same way. However, in the imperfect world in which we live, quite the opposite frequently happens to be the case: many CSS styles are displayed differently in virtually every browser. Many, if not all, major modern browsers (e.g., Firefox, Opera, Internet Explorer, Netscape, et al) implement their own generalized CSS rules, which often conflict with designer-applied styles. Needless to say, the unpredictable manner in which browsers implement CSS requires us to seek realistic browser equalization strategies. Using a well-crafted set of global CSS reset styles enables designers to make assumptions about the defualt behavior of browsers. Minimalistic Reset — Version 1 Poor Man’s Reset

Icebrrg - HTML Web forms, surveys, and invitations made chillingly simple Web Audio API 4. The Audio API 4.1. This interface represents a set of AudioNode objects and their connections. Web IDL callback DecodeSuccessCallback = void (AudioBuffer decodedData); callback DecodeErrorCallback = void (); [Constructor] interface AudioContext 4.1.1. destination An AudioDestinationNode with a single input representing the final destination for all audio. sampleRate The sample rate (in sample-frames per second) at which the AudioContext handles audio. currentTime This is a time in seconds which starts at zero when the context is created and increases in real-time. listener An AudioListener which is used for 3D spatialization. 4.1.2. The createBuffer method Creates an AudioBuffer of the given size. The numberOfChannels parameter determines how many channels the buffer will have. length parameter determines the size of the buffer in sample-frames. parameter describes the sample-rate of the linear PCM audio data in the buffer in sample-frames per second. The decodeAudioData method audioData bufferSize

Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 This version: (plain text, postscript, pdf) This document is an appendix to: Latest version of Web Content Accessibility Guidelines 1.0: Editors: Wendy Chisholm, Trace R & D Center, University of Wisconsin -- Madison Gregg Vanderheiden, Trace R & D Center, University of Wisconsin -- Madison Ian Jacobs, W3C Copyright © 1999 W3C (MIT, INRIA, Keio), All Rights Reserved. Abstract This document is an appendix to the W3C "Web Content Accessibility Guidelines 1.0". This list may be used to review a page or site for accessibility. A list version of the checkpoints is also available. This document has been produced as part of the Web Accessibility Initiative. Status of this document This document is an appendix to a document that has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation.

Learning Three.js Ultimate Fade-in slideshow (v2.0) Note: June 22nd, 14': Updated to v2.6, which adds responsive layout, swipe to navigate in desktop/ mobile devices. Description: This is a robust, cross browser fade in slideshow script that incorporates some of your most requested features all rolled into one. Each instance of a fade in slideshow on the page is completely independent of the other, with support for different features selectively enabled for each slideshow. Here's a lowdown on the script's features: Sleek fade in effect that has the current image fading over the previous one. Rock on with the ultimate fade in slideshow script! Demos (in touch enabled devices, swipe left/right to navigate as well): Directions Simply add the below code inside the <HEAD> section of the page: The above code references 1 external file plus 3 images as part of its interface. fadeslideshow.js jquery.touchSwipe.min.js (Github) (Optional file to auto enable swipe navigation). That's it for installation! Available Options for new fadeSlideShow()

HTML5 Canvas Tutorials best practices - What should every programmer know about web development web development - The Definitive Guide To Forms based Website Authentication Avoiding common HTML5 mistakes Between curating sites for the HTML5 gallery and answering readers’ questions here at HTML5 Doctor, I see a host of HTML5 sites and their underlying markup. In this post, I’ll show you some of the mistakes and poor markup practices I often see and explain how to avoid them. Don’t use section as a wrapper for styling One of the most common problems I see in people’s markup is the arbitrary replacement of <div>s with HTML5 sectioning elements — specifically, replacing wrapper <div>s (used for styling) with <section>s. In XHTML or HTML4, I would see something like this: <! Now, I’m instead seeing this: <! Frankly, that’s just wrong: <section> is not a wrapper. With that in mind, here’s the correct way to mark up the above example using HTML5 and a couple of ARIA roles. <body> <header> <h1>My super duper page</h1> <! If you’re not quite sure which element to use, then I suggest you refer to our HTML5 sectioning content element flowchart to guide you along your way. Ah, <figure>. <! Summary

HTML 5 Reference It is useful to make a distinction between the vocabulary of an HTML document—the elements and attributes, and their meanings—and the syntax in which it is written. HTML has a defined set of elements and attributes which can be used in a document; each designed for a specific purpose with their own meaning. Consider this set of elements to be analogous to the list of words in a dictionary. The basic structure of elements in an HTML document is a tree structure. 3.1 Syntactic Overview There are two syntaxes that can be used: the traditional HTML syntax, and the XHTML syntax. The HTML syntax is loosely based upon the older, though very widely used syntax from HTML 4.01. <! XHTML, however, is based on the much more strict XML syntax. <html xmlns=" HTML Document</title></head><body class="example"><h1>Example</h1><p>This is an example HTML document. 3.2 The Syntax 3.2.1 DOCTYPE Declaration 3.2.1.1 Obsolete But Permitted DOCTYPEs 3.2.2 Elements tag name

Software development: Glossary 3-tier application a program that is organized into three major parts: the workstation or presentation interface; the business logic; and the database and related programming. Each of these is distributed to one or more separate places on a network. agile software development calls for keeping code simple, testing often, and delivering small, functional bits of the application as soon as they're ready. Amdahl's law stipulates that, in a program with parallel processing, a relatively few instructions that have to be performed in sequence will have a limiting factor on program speedup such that adding more processors may not make the program run faster. amelioration pattern a design pattern that describes how to go from a bad solution to a better one. antipattern a frequently used, but largely ineffective solution to a problem. API (application programming interface) application integration application program aspect-oriented programming (AOP) best practice bug a coding error in a computer program.

What I've Learned About Making ClojureScript Applications With Pedestal Posted on by Tero Parviainen Pedestal is an interesting beast. It aims to provide tools for building single-page ClojureScript webapps with the simplicity and elegance we've become accustomed to in Clojure. It is also perceived as a difficult technology to master with several new concepts to grasp, some of them quite subtle. I think there's some truth in both claims. The Promise of ClojureScript I've been playing with ClojureScript since the very early days, and even wrote one of the early Hiccup ports back when there were no idiomatic rendering libraries. However, I haven't really been able to make myself comfortable doing substantial ClojureScript applications. I think I understand now what my problem has been: Since there hasn't been anything that provides an overall architectural backbone for ClojureScript apps, I've been attempting to replicate the way I do things in JavaScript. Pedestal When Pedestal was announced, I was excited about the prospect. What Pedestal Is Further Reading

Vimcasts - free screencasts about the text editor Vim

Related: