The Type We Want (MIX10)

The document provides an agenda for a CSS3 workshop that explores new CSS3 selectors and properties. The agenda includes an introduction to CSS3, exploring new features like color opacity, text effects, columns, fonts, shadows, borders and border images. The presentation provides examples and lessons learned for implementing these new CSS3 features across browsers.

The document discusses the Advanced Custom Fields (ACF) WordPress plugin. It begins by introducing ACF and its developer. It then explains that ACF makes creating custom fields easier through an intuitive interface. It notes that ACF allows adding additional information to posts through custom fields like name, address that can be displayed on the website. While custom fields are possible without ACF, it requires more coding. ACF streamlines the process and integrates well with custom post types. Both programmers and non-programmers can benefit from its documentation and user-friendly interface.

This document provides an agenda and overview for an HTML5 and CSS3 workshop. The agenda includes exploring new CSS3 selectors, properties, and techniques like opacity, text effects, fonts, shadows, borders, and image masks. The presenter will demonstrate these features in CSS3 and discuss browser support and techniques for making the features cross-browser compatible when possible. Attendees will then have time to experiment with CSS3 examples on their own and review additional resources. The goal is to help attendees include new CSS3 features into their own designs. The workshop covers many emerging and unfinished CSS3 modules being developed by the W3C and implemented gradually by browser vendors.

This document provides an agenda and overview for a presentation on CSS3 features including new selectors, properties, and techniques for cross-browser compatibility. It explores CSS3 modules like color, opacity, text effects, fonts, shadows, borders, and images. The presentation examines properties such as RGBA, text-overflow, text-selection, columns, @font-face, text-shadow, box-shadow, border-image, and techniques for implementing these features across browsers. Lessons are provided on browser support and workarounds for older browsers.

This document discusses typography and web fonts. It provides a brief history of fonts used on the web from 1996 to 2010. It then covers the @font-face rule which allows custom fonts to be used on websites. Both free and paid solutions for using web fonts are presented. Key considerations around web fonts like download size, copyright, and font quality are also outlined. The document concludes with comparisons between different techniques for displaying non-web fonts like sIFR, Cufon, and @font-face.

Given at the Western MA WordPress meetups, 5/30/12. A short presentation on webfonts. The talk featured a brief introduction to webfonts, considerations for picking the right webfont, and integrating webfonts into WordPress.

Talk given at the SensioLabs+eZ Roadshow, first stage in Cologne, Germany. Details on the next stages of this roadshow at: http://ez.no/de/Ueber-eZ/Veranstaltungen-Neuigkeiten/Neuigkeiten/Roadshow-eZ-Publish-meets-Symfony

Version 5 of eZ Publish is now running on Symfony 2 full stack. This talk will recount this fantastic journey, how the heart of a legacy content management engine was reworked, re-architectured, and injected into a Symfony 2 powered HMVC architecture. You will learn how two large technologies merged, what the pitfalls were, how they were overcome, and how these two large communities touched-base and look ahead together.

This document summarizes options for client-side persistent storage on mobile web. Local storage using localStorage has broad support and is recommended. Other options like cookies have size limits, and SQLite requires a SQL API. IndexedDB and the File API are not fully supported. Storage needs vary by platform - iOS and Android have different limits. Frameworks can provide a common API across storage mechanisms. Performance of localStorage is fast for reading and writing. Security considerations apply depending on the storage mechanism used. Overall, client-side storage options are improving and localStorage is generally sufficient.

The document discusses strategies for creating high-quality content to build links and increase website visibility. It recommends defining a topic, researching competitors, using proper grammar, emphasizing key terms, adding relevant images and videos, and segmenting content with hashtags. The document also provides tips for finding opportunities to gain links through guest posts, comments, forums, question-and-answer sites, and presentations. The goal is to meet user needs with useful content and find visibility opportunities to attract important links.

This document discusses various approaches to implementing single sign-on (SSO) with IBM Notes and Domino. It describes offload, synchronization, and integration approaches and provides examples of each. Specifically, it covers Notes Shared Login (NSL), synchronization using Tivoli Directory Integrator (TDI), Security Protocol for Next Generation Networks (SPNEGO), and Security Assertion Markup Language (SAML)/Notes Federated Logon (NFL). It emphasizes that a common user ID between the identity source and Domino is required and provides tips for setting up the Notes client with SSO.

This document discusses Firefox OS, a web-based operating system developed by Mozilla. It begins by introducing the speaker, Veck Hsiao, a postgraduate student at NCCU studying system programming and programming languages who contributes to Firefox OS. The document then discusses key topics like how Firefox OS uses web technologies like HTML, CSS, and JavaScript to function as an operating system. It describes components of Firefox OS like Gaia, Gecko, and Gonk. It outlines reasons for using Firefox OS like mobility, cross-platform capabilities, being open source, and using web standards. It provides information on how to test and contribute to Firefox OS through Bugzilla and GitHub. It also describes the Firefox OS Tablet Contribution Program

The document discusses strategies for developing mobile web applications for smartphones like iPhone and Android, focusing on technologies like HTML5, CSS3, and JavaScript that enable responsive design and native-like experiences. It also covers tools and frameworks for building cross-platform mobile apps, such as PhoneGap and Titanium, as well as strategies for optimizing content delivery and the user experience for less capable mobile devices.

From Web Directions North 2008, Jonathan Snook compares some of the leading JavaScript Frameworks out there.

This document provides tips for giving presentations. It suggests focusing a presentation on defining a problem and telling a story to engage the audience. The tips include using different types of slides like bullets and code to highlight important information, injecting humor with pictures, speaking slowly, and being prepared to answer questions. Presenters are advised to not reveal all details at once and to take breaks between slides to keep the audience interested.

The document discusses building on existing tools, frameworks, platforms and ideas rather than reinventing the wheel. It lists examples of existing tools and frameworks in various categories like JavaScript, CSS, programming languages and platforms that can be leveraged to build new applications and speed up development. The benefits mentioned are that existing solutions are well-tested, development can be faster, and new ideas can solve problems outside the original solutions.

This session will take a look at two prominent desktop platforms, AIR and Titanium, and examine some of the pros and cons of developing with that environment. We'll also take a look at ways to speed up development using rich components like jQuery UI and take advantage of the features of HTML5 and CSS3 that can be used right away.

by Benedict Evans. Please see this link for full description, slides, AND version with talk track: http://a16z.com/2016/12/09/mobile-is-eating-the-world-outlook-2017/

Looking to scale something up? Depending on how you're going after your market/ acquiring users, you may need to build a sales organization that's optimized for a top-down or bottom-up sales process (or perhaps both). Watch the video overview at http://a16z.com/2015/03/06/go-to-market-bootcamp/ and then check out this slide deck, which shares some concrete tips and tools for accelerating time to market -- from the go-to-market experts at a16z, led by 'sales savant' Mark Cranney. Because selling to enterprises is a lot like getting a bill passed through Congress: it can get stuck. And getting stuck -- or going down the wrong path -- can mean death to startups in a competitive market. Here's how to avoid that.

Bio in 2015 is like software in 2005. The bio fund is really about funding software companies in the bio space.

Get in touch: guillaume@lajavaness.com A short presentation outlining the main customer targeting strategies a B2B SaaS startup might decide to use.

Network effects. It’s one of the most important concepts for business in general and especially for tech businesses, as it’s the key dynamic behind many successful software-based companies. Understanding network effects not only helps build better products, but it helps build moats and protect software companies against competitors’ eating away at their margins. Yet what IS a network effect? How do we untangle the nuances of 'network effects' with 'marketplaces' and 'platforms'? What’s the difference between network effects, virality, supply-side economies of scale? And how do we know a company has network effects? Most importantly, what questions can entrepreneurs and product managers ask to counter the wishful thinking and sometimes faulty assumption behind the belief that “if we build it, they will come” … and instead go about more deterministically creating network effects in their business? Because it's not a winner-take-all market by accident.

In this update of his past presentations on Mobile Eating the World -- delivered most recently at The Guardian's Changing Media Summit -- a16z’s Benedict Evans takes us through how technology is universal through mobile. How mobile is not a subset of the internet anymore. And how mobile (and accompanying trends of cloud and AI) is also driving new productivity tools. In fact, mobile -- which encompasses everything from drones to cars -- is everything.

We finally have a support of the CSS @font-face rule, on most browsers on the market. There will be an overview of their implementations, advantages and constraints that this brings, as well as some good practices for its use. (This is a translation of my original french presentation http://www.slideshare.net/yvg/css-fontface-des-polices-personnalises)

Thomas Phinney introduces web fonts, covers font selection and combination, and also includes: • How and why mobile devices and iOS have killed off web safe fonts • Best practices for picking and combining individual typefaces • On-screen text rendering differences • Creative inspiration for designing with web fonts in Adobe® Photoshop®

This document discusses web fonts, including the business drivers for using them, the supporting technologies, distribution mechanisms and licensing options, performance impacts, useful tools, and best practices. It notes that web fonts allow approved typefaces from companies and are brought in as an opt-in feature. While the <font-face> CSS feature has existed since IE4, different formats like TTF, OTF, EOT, WOFF and SVG require support. Distribution includes hosting on websites, CDNs, or third-party services, while licensing models include commercial and free options. Performance impacts include additional HTTP requests, blocking rendering, and perceived slowness. Tools aid optimization, subsetting, and conversion between formats. Caching, compression,

Microsoft Silverlight is a cross-browser plugin that allows developers to build rich interactive applications and media experiences for the web. Key features include vector graphics, media playback, animation, and integration with existing web pages. Silverlight uses XAML for markup and a .NET subset for programming. It provides a sandboxed runtime environment and supports common development scenarios like media, rich content, and rich internet applications. Developers can use XAML to build user interfaces with shapes, brushes, text and images, and add interactivity through transforms and animation.

An alphabetical tour of digital media landscape terminology, covering concepts from Ajax to Usability. Designed for training of journalists entering the digital media landscape.

Recent implementation of CSS3 features in modern browsers allow for greater design control and creativity in our Web sites. In this three-hour workshop, attendees will learn about using colors through RGBa and opacity, multiple background and border images, text and box shadows, CSS-enabled gradients and transitions as well as laying out text in multiple columns. In addition to font embedding techniques and third-party font bureaus, we look into designing with older browsers in mind when coding with CSS3.

When designers and developers collaborate, it creates a strong foundation for projects. Choosing fonts requires understanding web safe fonts, image replacement techniques, trends from services like Google Fonts, and keeping designs flexible for variable content. Thorough testing across browsers and devices is important, and teams should share knowledge to overcome common roadblocks like over-reliance on JavaScript fixes or lack of accessibility.

Web fonts offer great flexibility for brands and designers to use a wider range of fonts online. Using a custom font on the web was only achievable through various techniques, all with certain limitations. Most designers opted to stick with Web Safe Fonts – which are fonts that are already installed by default across different operating systems.

In the beginning, web designers only had a handful of typefaces at their disposal to use in their designs. Then Flash and Javascript allowed unlimited fonts but lacked accessibility features. In the past year, it seems we finally have a winning solution: the @font-face method which has support from all major browsers and does so using only HTML and CSS. Meanwhile, a second conversation is happening amongst those who actually own the fonts – the foundries. Would these emerging technologies ensure that their typefaces could not be easily copied from the web? Unfortunately @font-face is still not widely accepted by most foundries. Some allow you to use a hosted service like TypeKit, or you can venture into the burgeoning movement of open source and commercial-free fonts and enjoy free rein over your web typography.

The document discusses the @font-face CSS rule, which allows embedding fonts through CSS rather than relying on users' installed fonts. It provides examples of how to implement @font-face and addresses issues like the "flash of unstyled text" that can occur as embedded fonts load. Tips are given for fighting this, such as placing CSS at the top, using font formats like WOFF, and subset fonts to reduce file size. Browser differences and fixes for issues like font rendering in IE are also covered.

This document discusses typography on the web. It provides an overview of the history of embedding fonts online through technologies like @font-face, and formats like EOT, TTF, OTF and WOFF. It also discusses OpenType features that allow for rich typography effects through CSS, though browser support is still limited. The document advocates optimizing typography to improve readability and the user experience of reading on the web.

Presented at MinneWebCon 2011 Web typography is making the internet look better than ever before. You're particular about the fonts you choose in other mediums, don't settle for anything less for your online projects. This session will address the basics of effective typography and techniques that everyone can apply right away to harness the power of web typography on their website or blog.

This talk discusses standards evolution, HTML5 and CSS3 in detail. Starting with the history of HTML and CSS, it goes on to show how HTML5 and CSS3 were developed, why they were necessary, the problems they aim to solve, what the main new features are and why they are so useful, and how we can start using these features in the real world, right now. It also provides advice for the discerning web standards gentleman.

- There are 4 weeks left in the course, with milestones on September 24th, October 1st, and October 8th, and all badges awarded by October 15th. Students are encouraged to finish HTML5 Core this weekend and knock out CSS by September 24th. - When creating a single webpage, the main parts include the HTML file, CSS stylesheet, images, and other media files. All parts need to be uploaded to the website when posting the page. - Browser developer tools like the Web Developer toolbar for Firefox and Chrome, and Firebug for Firefox, can help with webpage development and troubleshooting.

HTML is the main markup language used to create web pages and other information displayed in web browsers. It has evolved over time from HTML in 1990 to newer specifications like HTML5, with HTML5 expected to be finalized by 2016. CSS is used to describe the presentation and formatting of HTML documents, and has also evolved from CSS1 to the current CSS3 specification, which is divided into modules that add new capabilities without breaking compatibility. Together, HTML and CSS provide a common application platform for building websites and web apps that can be viewed across devices like desktops, tablets, and mobile phones.

Ever spent countless hours crafting a totally awesome type system for your beautiful design, only to have it lost in translation when it goes to development? Examine type and icon fonts through a developer lens, and learn how designers and front-end developers can work together to get everyone on the same (elegantly designed) page! How to utilize web fonts and icon fonts within your projects How icon fonts can help your site performance Tools for crafting an efficient type system on the web

Talk given at DevCon 5 in Santa Clara: The power of the web has arrived for mobile phones and tablets. CSS3 gives web sites a dynamic, interactive capability and greater useability. CSS3 adds fine grained controls for designers looking to bring the web closer to reality.

This document summarizes a workshop on web typography presented by Jim Kidwell and Thomas Phinney. It begins with biographies of the presenters and an agenda for the workshop. The first section provides a history of web fonts, starting with the limited "web safe" fonts of the early internet and the introduction of technologies like @font-face, EOT, and WOFF that enabled the use of true type fonts on the web. Subsequent sections discuss best practices for choosing, setting, and using web fonts, including topics like font licensing, legibility, pairing different fonts, and CSS features. The document provides an overview of the workshop's content and discussions.

The document discusses the characteristics of a successful single page application (SPA). It recommends choosing frameworks and libraries that have good documentation, large communities, and support needed functionality. It also emphasizes building robust, stable APIs and keeping performance in mind from the start. The document suggests optimizing JavaScript and backend code, knowing the runtime environment, and using developer tools to minimize resource-intensive reflows and repaints. Overall, it presents SPAs as a good option for mobile apps if frameworks, libraries, APIs, and performance are chosen and developed carefully.