Front End Development Guidelines Accessibility What's Up, DOCTYPE? The absence of a DOCTYPE is a crime punishable by death. You may have relied on the following DOCTYPE in the past, but it's important to know that this is now being superseded by a leaner and meaner snippet. Ideally, the HTML5 DOCTYPE should be used. Write Valid Semantic Markup Writing websites with clean, semantic HTML is something we wish we could always do. Headings should be heirarchically created from <h2>onwards, paragraphs should always be in <p> tags and so on and so forth. Which do you think looks cleaner, this? <span class="sectionHeading">A Heading</span><br /><br /> Lorem ipsum dolor sit amet. ... Or this? <h2>A Heading</h2><p> Lorem ipsum dolor sit amet. ... Fallbacks for Middle Mouse Clicks One of the most frustrating accessibility and usability flaws of the modern web stems from the remapping of hyperlink click functions. A modern example of a popular website that is contributing to this problem is the Twitter web app. Use Microformats
General Interface Resource Center @ TIBCO Developer Network Websites as graphs Everyday, we look at dozens of websites. The structure of these websites is defined in HTML, the lingua franca for publishing information on the web. Your browser's job is to render the HTML according to the specs (most of the time, at least). You can look at the code behind any website by selecting the "View source" tab somewhere in your browser's menu. HTML consists of so-called tags, like the A tag for links, IMG tag for images and so on. I've used some color to indicate the most used tags in the following way: blue: for links (the A tag)red: for tables (TABLE, TR and TD tags)green: for the DIV tagviolet: for images (the IMG tag)yellow: for forms (FORM, INPUT, TEXTAREA, SELECT and OPTION tags)orange: for linebreaks and blockquotes (BR, P, and BLOCKQUOTE tags)black: the HTML tag, the root nodegray: all other tags Here I post a couple of screenshots, and I plan to make the app available as an applet, so that anybody can look at their websites in a new way. cnn.com boingboing.net apple.com
128b Joseph Scott’s Blog » Blog Archive » AJAX Edit In Place With Prototype, Version 0.2.0 UPDATE Thu 29 Nov 2007 @ 5:30pm : The Edit In Place code has a new home at editinplace.org UPDATE Fri 30 Jun 2006 @ 8:20am : You can find the latest Edit In Place blog posts at It has been almost two months since my since the first version of Edit In Place (version 0.1.0). Doing OO in JavaScript is a bit strange. There are some new default CSS names used: Making IDs editable have new function calls as well: The EditInPlace.makeEditable() function only requires the id and save_url, the type option defaults to text. id: false, save_url: false, css_class: 'eip_editable', savebutton: 'eip_savebutton', cancelbutton: 'eip_cancelbutton', saving: 'eip_saving', type: 'text' The css_class, savebutton, cancelbutton and saving are all CSS classes. My JavaScript skills are still pretty basic so if you have some recommended changes feel free to drop me a note .
Keyczar Google Powered Site Search with jQuery Martin Angelov By far one of the most requested features by Tutorialzine’s readers, is building a site-wide search. One way to do it, is to build it yourself from the ground up. Another way is to use the services of the one search engine that already knows everything about everyone. Important update (October 2014): Google has canceled the API that this search engine uses, so this script will no longer work. The HTML Lets start with the HTML markup. search.html <! In the body section, we have the main container element – the #page div. Inside the form is the text input box, after which comes the radio group for searching on the current site / the web, and the four search type icons, organized as an unordered list. Google Powered Site Search The CSS The CSS styles reside in styles.css. styles.css – Part 1 As mentioned above, the form’s functions are not limited to only submitting data, but also to act as a regular container element. styles.css – Part 2 styles.css – Part 3 The jQuery Conclusion
» The Web-based Office will have its day | Web 2.0 Explorer | ZDNet.com I first profiled a Web 2.0 office in early September and since then more web-based office products have surfaced. Peter Rip posted recently that he's now "bumped into an alpha or beta Web-incarnation for every Microsoft desktop product". He says most are AJAX, but some are Flash or Flex-based (both Macromedia products). Peter thinks desktop apps are on the way out, because "no one works at their desktop anymore." While he rightly points out that office people are spending more and more time on the Net, I don't agree with his conclusion that this necessarily signals the end of desktop apps - yet. However I do think that long-term, the writing is on the wall for desktop office applications. The time for the web-based office will come, mark my words. Ones I mentioned in my initial post: Writely - "The Web Word Processor" (note that for creating documents, it uses an HTML editor and then converts to Word format) FCKeditor is also an MS Word-like web app.
argouml.tigris.org