agileweb.org - posts tagged 'typography' http://www.agileweb.org/ agileweb.org - posts tagged 'typography' - posts tagged 'typography' http://www.agileweb.org/ http://1.asset.soup.io/asset/0129/4353_8c96.gif 128 128 Ross Lawleys tumblelog mainly on software and agile methods. Resume: A Tale of Desire, Intrigue, and Formatting {"tags":["design","jobsearch","article","tips","howto","typography","fonts","career","jobs","cv","resume","formatting","foss"],"type":"link","title":"Resume: A Tale of Desire, Intrigue, and Formatting","source":"http://www.zackgrossbart.com/hackito/resume/","body":"I hardly ever hand people paper documents, but about a year ago two events happened in my life which caused me to think more about them. The first was reading The Elements of Typographic Style by Robert Bringhurst. The second was getting laid off. I started thinking about the one piece of paper every engineer prints out and hands to people, their resume."} <p>I hardly ever hand people paper documents, but about a year ago two events happened in my life which caused me to think more about them. The first was reading The Elements of Typographic Style by Robert Bringhurst. The second was getting laid off. I started thinking about the one piece of paper every engineer prints out and hands to people, their resume.</p> <p><a href="http://www.zackgrossbart.com/hackito/resume/">http://www.zackgrossbart.com/hackito/resume/</a></p>Mon, 02 Nov 2009 10:27:40 GMThttp://agileweb.org/post/33335592/Resume-A-Tale-of-Desire-Intrigue-andurn:www-soup-io:1:33335592linkdesignjobsearcharticletipshowtotypographyfontscareerjobscvresumeformattingfoss cufon - GitHub {"tags":["typography","sIFR","javascript","webdesign","font","css","webdev","fonts","progressive","enhancement"],"type":"link","title":"cufon - GitHub","source":"http://wiki.github.com/sorccu/cufon/about","body":"Cuf\u00f3n aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use. To achieve this ambitious goal the following requirements were set:\n\n 1. No plug-ins required \u2013 it can only use features natively supported by the client\n 2. Compatibility \u2013 it has to work on every major browser on the market\n 3. Ease of use \u2013 no or near-zero configuration needed for standard use cases\n 4. Speed \u2013 it has to be fast, even for sufficiently large amounts of text\n\nAnd now, after nearly a year of planning and research we believe that these requirements have been met."} <p>Cufón aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use. To achieve this ambitious goal the following requirements were set: 1. No plug-ins required – it can only use features natively supported by the client 2. Compatibility – it has to work on every major browser on the market 3. Ease of use – no or near-zero configuration needed for standard use cases 4. Speed – it has to be fast, even for sufficiently large amounts of text And now, after nearly a year of planning and research we believe that these requirements have been met.</p> <p><a href="http://wiki.github.com/sorccu/cufon/about">http://wiki.github.com/sorccu/cufon/about</a></p>Mon, 06 Apr 2009 10:47:44 GMThttp://agileweb.org/post/16815403/cufon-GitHuburn:www-soup-io:1:16815403linktypographysifrjavascriptwebdesignfontcsswebdevfontsprogressiveenhancement