A few simple tips and tricks for getting over your fear of public speaking and/or presenting - something everyone needs to do at some point, regardless of occupation or specialization.
Why is it that every web build system needs you to adapt to its way of working? Why do you have to write manifest files, put files into a specific directory structure and do a lot of manual work to have an optimized production build of your web site. If your browser can see the unoptimized assets in your web page, why shouldn't your build system be able to as well? This will be a very short presentation of the thoughts and decisions behind the node based web optimization framework assetgraph and a demonstration of some of the features it has.
Iacobien and Rian will talk about accessibility and the WP- Accessible project. The main goals of this project are to help everyone use and maintain an accessible WordPress website.
The idea is to show about 5 short tips/tricks/hints about CSS and HTML – you know, like I do on bricss.net. Haven't yet figured out exactly which 5 subjects I'll pick, but that will also depend on the topics that are circulating in the front-end world around that time...
Responsive images are the hot topic this year and we are finally getting to an end. An editor's draft has been written for the W3C. But now you might wanna now, where we go and what to use. I'll give you a quick overview. And show how it could work on devices.
I'll be starting off by trying to identify the difference (UI wise) between Web Sites and Web Apps. Then I'll be showing how CSS Flexbox greatly simplifies creating Web Apps. Not just by talking about it using slides, but rather through live coding and examples.
Being Russia's search giant, Yandex employs thousands of developers, who are daily challenged by a huge amount of frontend development problems. Such as fast developing, maintaining long-lived services, code reusing, team scalability an many more. I would like to share with the comminity our solutions to these problems and speak about how they evolved through time and technological changes.
Development of a formula for selecting clients. Or better: how can a selection be improved if you have the choice? Customers send out signals before you make the contract. Read, analyze and understand them. So the goal has to be not a customerMatchAll(), more a matchCustomer() paired with giveMeMoneyAndShutUp(true). But some exceptions are allowed on the road to success ;-)
Covering the 3 most important things one needs to consider when building utilities/libraries for others to use. (robustness, simplicity, flexibility)
How we were asked to build a continuous, full-screen, interactive animation for a client and the hilarity that ensued. A tale of feature detection, CSS animations and transitions, scripted animation, hardware acceleration and performance.
New CSS properties like transitions, gradients and, of course, pseudo-elements — :before and :after. People use them to create complex things just on a single html element, for some extra decorations without any bloated markup and for so much more. However, pseudo-elements have a major drawback — you couldn't use CSS transitions on them. Until now! Right now the only browser who know how to transition values on pseudos is FireFox. But I'll talk about the method any modern browser would understand — and by which any modern browser could show you transitions for most of the CSS properties right on the pseudo-elements. It's a hacky, quirky way, it won't work for any property, but it's better than nothing — with transitions on pseudo-elements a lot of things would be possible — and I'll show some live examples during my talk.
The web has changed but the way we approach new web projects hasn't. In this talk I'll compare the old defaults we used to work with, like desktop screen sizes, mouse interaction and some ideas about site structure with new defaults, new ideas based on the current web.
Usually game development in web use flash, canvas or webgl. But today you may use also CSS with little bit of js. I want to show couple of tricks and explain why CSS sometimes may be good decision.
Choosing you defaults is important to have a good workflow. Making decisions all over again is bad for productivity and your lifestyle. In this session you'll learn how thinking about future decisions will improve work and life.
Responsive design involves more than just fluid grids and media queries. The move to adaptive web sites touches every part of an organisation: from content needs and content management, to editorial workflows and project management. The way we design and build web sites is changing, but the way we write, manage, and evolve our websites needs to change, too. Mark will share his thoughts and experience of how adopting responsive web design practices needs to begin in the boardroom, rather than the developer’s office.
Viewports are pretty easy on desktop: they're the browser window. Thus, an element with width: 10% will span 10% of the browser window, while width: 100px just means a width of 100px. On mobile, things are quite different. There are two viewports and three kinds of pixels, and they interact in all kinds of weird ways—ways that depend on the browser. In this technical presentation PPK will explain why a pixel is not a pixel, what the difference between the two viewports is, and which bits web developers should care about. Caution: Heads may explode!
At Guardian Interactive we work to create innovative visualisations to delight and inform our readers. With this talk I want to show you how to design and build not just simple and not-so-simple charts to illustrate data but how to design & architect larger more complex pieces of content that tell stories and illustrate ideas. We'll start by exploring some of the best tools that exist today, including d3 & Modest Maps and then looking and how we can use these tools in conjunction with some new open libraries tools we're releasing at the guardian that make it easier to structure larger interactive content, using both realtime dashboards and narrative-driven visualisation as examples.
Use of image editors for creating web design mockups has worked until now, but responsive design is forcing us to find alternatives, as we can't simply create more mockups as we design for more screens. Have no fear, there is at least one method of replacing Photoshop for web design. Let's take a look at one of the most important aspects of this method: the creation of clear, semi-automated, self-updating style guides.
Many web developers will agree that building accessible websites is of great importance. Still, for many of us it's hard to imagine what the web is like if the 'default' ways to interact with it just don't work for you. In this panel of user experts Bram, Antoine and Bor showed us how they interact with websites and applications and discuss what does or doesn't work for them.
Chris Heilmann moderated the panel.
According to .net magazine, Lea’s “CSS3 secrets: 10 things you may not know about CSS” was one of the 15 best talks of 2011. Web developers all over Europe loved it. This talk continues on the same p
The interactive Google homepage doodles come with all sort of interesting problems and constraints. Join Marcin as he goes through some of the nice solutions, ugly hacks, terrible mistakes, and last-minute miracles accompanying doodles celebrating Pac-Man, Jules Verne, Stanislaw Lem, and recent summer games.
As engineers, we are compelled to aggregate and streamline every process we touch. But too often this mentality can be counter-productive in a grander perspective. David DeSandro will discuss wayward steps in implementing SASS, writing build scripts, and overall attempting to solve big dilemmas by introducing bigger problems. Learn about what anti-patterns to watch out for and practices to implement before you get too clever.
Jeroen will talk about the current state of HTML5 video on both desktop and mobile. The latest developments include the HTML5 element, which promises to make online video accessible and interactive.
More information: longtailvideo.com/html5
A mix of innovation, collaboration through standards, reverse engineering, content studies, and fussy politics, has created the somewhat messy yet beautiful platform we have today. It enables us to publish anything from a simple document to a complex application. This talk will dive into some of the low-level details of that platform as well as explain those fussy politics.
The word is getting out. Great web site experiences require careful development and crafty execution in the front end. Squeezing every drop of performance out of your user's browser is tough, but Steve Souders and friends have mobilized an army, and we are all having a bloody good go.
But there is a common threat to doing great work in the front-end. It lurks in the back-end and clients love it. It's the content management system, and more often than not, it stinks.
We'll look at examples of the damaging traces CMSs leave behind in the front-end and at how we might work to reduce them. We'll find ways to fight for what matters in a CMS, and ways to avoid the smell of your CMS wafting over to the user and sacrificing the craftsmanship of good front-end engineering.
Maybe you've inherited some smelly code, or maybe you've written some yourself, rushing to get a feature out the door knowing that you're leaving yourself a mess to clean up later. No matter how you end up with smelly code, eliminating smells is an important step toward making code easier to work with -- for you and your fellow developers -- reducing opportunities for introducing bugs, and making your code easier to test. Heck, it can even help you get a new job.
Progress is a process, and like most man-made processes progress can be sped up and slowed down. As the victims and beneficiaries of progress in the browser space, it pays to understand not just what's holding us back, but what could be helping us move forward faster as well. This talk examines the feedback loops that create and hinder progress, why that process will never be pretty, and why now is perhaps the best time ever to be a web developer. Transcript available on http://fronteers.nl/congres/2012/sessions/the-web-platform-and-the-process-of-progress-alex-russell