Nicholas C. Zakas advocates for the concept of progressive enhancement, which ensures that all users can access basic content and functionality with any browser or connection, while providing enhanced experiences for those with more advanced browsers. Progressive enhancement uses web technologies in layered fashion from content to presentation to behavior. Zakas argues developers should focus on the core features of their products and support the best experience given a user's capabilities rather than trying to provide identical experiences across all browsers. Users care most about content, and progressive enhancement gives incentives for users to upgrade their browsers.
Advancing Content Management for Omni-Channel User Experiences by Roland Bene...eZ Systems
Roland Benedetti Chief Product and Marketing Officer at eZ Systems presented at re\VISION NYC on December 12, 2016. He spoke about what role content plays in a successful omni-channel user experience strategy. Content is key for digital success, but the reality is content by itself is nothing. We need to connect the right content to the right users and engage them throughout the customer journey in a consistent, meaningful way. In this talk, Roland Benedetti will share ideas on how content management technology can help organizations succeed with their content across channels and he'll also share some pitfalls to avoid.
Advancing Content Management for Omni-Channel User Experiences by Roland Bene...eZ Systems
Roland Benedetti Chief Product and Marketing Officer at eZ Systems presented at re\VISION NYC on December 12, 2016. He spoke about what role content plays in a successful omni-channel user experience strategy. Content is key for digital success, but the reality is content by itself is nothing. We need to connect the right content to the right users and engage them throughout the customer journey in a consistent, meaningful way. In this talk, Roland Benedetti will share ideas on how content management technology can help organizations succeed with their content across channels and he'll also share some pitfalls to avoid.
Slides from my May 23 webinar for the ADA Great Lakes Center. Overview of the state of things for WordPress and accessibility and the principles of web accessibility.
Framework plays a key role in application development. A website is attracted by its design and structure. We depict a short comparison of three web designing frameworks.
Increasing Productivity With Google Apps & Gmail Tools4Good.org
Google Apps is popular communication and collaboration platform for nonprofits. Gmail is the most-used part of Google Apps. This webinar introduces a number of third-party tools and techniques that make Gmail and Google Apps even better.
WordPress 2.7 is a work in progress. These
wireframes attempt to document the current state of or plans for the application. In some cases, elements may change as development proceeds, either because of technical issues or to address usability
issues. In addition, elements may change during the visual design stage. These wireframes are a guide for development that will be updated as necessary, and are not set in stone.
2.7 will use a fluid design, rather than the fixed-width of 2.5. The wireframes are scaled to represent an actual browser window at 1024x768 resolution.
I used this presentation to my first Basic WordPress Presentation last February 05, 2017. To learn more about WordPress, I will share some more tips on my blog at http://www.realbloggingadvice.com
WordPress is the most widely used Content Management System because it's easy to use, easy to customize and it's free! What a lot of people don't realize is how powerful WordPress can be with the right tools. This presentation will show you how powerful WordPress can be with minimal knowledge of how to design or develop websites. We'll cover the themes and plugins you need to know about and hopefully do some things you didn't think WordPress could do.
This presentation is for everyone whether you are using WordPress already or not. Users, non-users and developers alike should all walk away having learned something new.
A presentation on some things to think about when working on responsive web design projects. Presentation given at the Brisbane Web Design meetup - 22 May2012
A presentation created for introducing WordPress and outlining what will be covered in my WordPress Super Survival Skills Course - http://www.the-colab.com/wordpress-survival-skills-course/
Covering the ClassicPress and it's fork, WordPress. This gets into Gutenbug and the havok its created as well as how the ClassicPress platform empowers people to deliver their own websites without needing to understand complex technical details.
Responsive Web Design - Introduction & Workflow OverviewAidan Foster
Responsive Design's is a way of making a single website that works well on mobile, tablet, and desktop browsers. Back in 2010 Ethan Marcotte, first coined the term "responsive design" and described it as having 3 components:
Flexible Images
Fluid Grids
CSS Media Queries
Well it seems Ethan let quite a few cats of out bag with this one, and we've been trying to herd those cats ever since.
What started as exclusively a front-end web design technique has expanded to include a whole new range of both front-end and server-side programming techniques. The real challenge came when we also suddenly discovered that tried and true practices for project management, and creative concept development all started to fall apart. It’s not practical to create photoshop mockups of ever page in a site at every device size - There’s simply too many variables to account for in graphic design software.
Responsive Design requires a new process for creating websites, and new ways of interacting with teams and clients.
This presentation will outline a birds-eye-view of Responsive Techniques, Strategies, Tools, and Gotchas of RWD. It will focus on some of the new workflow techniques needed and cover some suggestions for where to go to learn more.
Slide Summary
1-25: History of Responsive Design
26-50: Coding Basics (Developer Focused)
51-57: Progressive Enhancement
58-70: Mobile First
71-93: Responsive Workflows
96-99: Selling Responsive Design
Wikify your Doc Set: A Writer's Role in Web 2.0Anne Gentle
Learn from other examples of wikis used for end-user documentation. Evaluate the advantages and known limitations of using a wiki. Determine if simply adopting wiki-like technology would be sufficient for your environment. Get some judo moves for defending your stance for or against a wiki.
Keynote- We're going wrong: Choosing the web's future. Peter Paul KochFuture Insights
From FOWA London 2015
Web developers and browser vendors are trying too hard to emulate native apps; in vain, PPK says, because we can't out-native native. Meanwhile this quest for native emulation has a host of undesirable by-effects: too many new browser features that need too many new (and not always performant) tools to create polyfills, which cause too many people to think they only need to understand the tools in order to be a web developer. We're going wrong. We should take some time to figure out what the web is for, how we can have a successful web ecosystem next to, but not in competition with, native ecosystems, and how we should explain what web development is to Java developers and others who come from a non-web background. We need time to think.
Webmaker Tools are used to create webpages, videos, remix the webpages and also share them on internet. These tools generate an URL after creating the stuff on the web. This URL can be shared with others.
Slides from my May 23 webinar for the ADA Great Lakes Center. Overview of the state of things for WordPress and accessibility and the principles of web accessibility.
Framework plays a key role in application development. A website is attracted by its design and structure. We depict a short comparison of three web designing frameworks.
Increasing Productivity With Google Apps & Gmail Tools4Good.org
Google Apps is popular communication and collaboration platform for nonprofits. Gmail is the most-used part of Google Apps. This webinar introduces a number of third-party tools and techniques that make Gmail and Google Apps even better.
WordPress 2.7 is a work in progress. These
wireframes attempt to document the current state of or plans for the application. In some cases, elements may change as development proceeds, either because of technical issues or to address usability
issues. In addition, elements may change during the visual design stage. These wireframes are a guide for development that will be updated as necessary, and are not set in stone.
2.7 will use a fluid design, rather than the fixed-width of 2.5. The wireframes are scaled to represent an actual browser window at 1024x768 resolution.
I used this presentation to my first Basic WordPress Presentation last February 05, 2017. To learn more about WordPress, I will share some more tips on my blog at http://www.realbloggingadvice.com
WordPress is the most widely used Content Management System because it's easy to use, easy to customize and it's free! What a lot of people don't realize is how powerful WordPress can be with the right tools. This presentation will show you how powerful WordPress can be with minimal knowledge of how to design or develop websites. We'll cover the themes and plugins you need to know about and hopefully do some things you didn't think WordPress could do.
This presentation is for everyone whether you are using WordPress already or not. Users, non-users and developers alike should all walk away having learned something new.
A presentation on some things to think about when working on responsive web design projects. Presentation given at the Brisbane Web Design meetup - 22 May2012
A presentation created for introducing WordPress and outlining what will be covered in my WordPress Super Survival Skills Course - http://www.the-colab.com/wordpress-survival-skills-course/
Covering the ClassicPress and it's fork, WordPress. This gets into Gutenbug and the havok its created as well as how the ClassicPress platform empowers people to deliver their own websites without needing to understand complex technical details.
Responsive Web Design - Introduction & Workflow OverviewAidan Foster
Responsive Design's is a way of making a single website that works well on mobile, tablet, and desktop browsers. Back in 2010 Ethan Marcotte, first coined the term "responsive design" and described it as having 3 components:
Flexible Images
Fluid Grids
CSS Media Queries
Well it seems Ethan let quite a few cats of out bag with this one, and we've been trying to herd those cats ever since.
What started as exclusively a front-end web design technique has expanded to include a whole new range of both front-end and server-side programming techniques. The real challenge came when we also suddenly discovered that tried and true practices for project management, and creative concept development all started to fall apart. It’s not practical to create photoshop mockups of ever page in a site at every device size - There’s simply too many variables to account for in graphic design software.
Responsive Design requires a new process for creating websites, and new ways of interacting with teams and clients.
This presentation will outline a birds-eye-view of Responsive Techniques, Strategies, Tools, and Gotchas of RWD. It will focus on some of the new workflow techniques needed and cover some suggestions for where to go to learn more.
Slide Summary
1-25: History of Responsive Design
26-50: Coding Basics (Developer Focused)
51-57: Progressive Enhancement
58-70: Mobile First
71-93: Responsive Workflows
96-99: Selling Responsive Design
Wikify your Doc Set: A Writer's Role in Web 2.0Anne Gentle
Learn from other examples of wikis used for end-user documentation. Evaluate the advantages and known limitations of using a wiki. Determine if simply adopting wiki-like technology would be sufficient for your environment. Get some judo moves for defending your stance for or against a wiki.
Keynote- We're going wrong: Choosing the web's future. Peter Paul KochFuture Insights
From FOWA London 2015
Web developers and browser vendors are trying too hard to emulate native apps; in vain, PPK says, because we can't out-native native. Meanwhile this quest for native emulation has a host of undesirable by-effects: too many new browser features that need too many new (and not always performant) tools to create polyfills, which cause too many people to think they only need to understand the tools in order to be a web developer. We're going wrong. We should take some time to figure out what the web is for, how we can have a successful web ecosystem next to, but not in competition with, native ecosystems, and how we should explain what web development is to Java developers and others who come from a non-web background. We need time to think.
Webmaker Tools are used to create webpages, videos, remix the webpages and also share them on internet. These tools generate an URL after creating the stuff on the web. This URL can be shared with others.
Mozilla is a non-profit that believes everyone should be able to make and share with the open web. But creating, hosting or tweaking your own stuff is often still too difficult—with obstacles like learning HTML and CSS, struggling with servers to preview your work, or figuring out where your content will live online. Thimble clears away those barriers, making it easier to create your own projects quickly and learn web skills in a way that’s easy, visual and fun.
This is a presentation from Minne Web Con 2010.
This presentation is about using CSS3 to enhance sites for browsers that support them, and the trade offs you make when only supporting some browsers.
What is website How to create a professional site and which tools is required for creating site or blog and also how to identifies the real web page and the bogus or fake web pages on the site...................................................................................
To remain viable in the publishing environment it is important for publishers stay current with evolving technology. To help publishers prepare for this new reality, SSP, in collaboration with the World Bank, presents an important full-day seminar on Digital Opportunities and Challenges. This two-part seminar explores the choices that choices publishers will have to make early in the process to enhance their return on investment as they transition to an evolving digital landscape, and presents practical examples of strategies for packaging & delivering content to different channels (not just mobile devices).
The morning session will provide an overview of the current market for electronic publishing with specific examples of business models used by a university press, a commercial publisher, and an association. The afternoon session will cover the various electronic readers, emerging mobile applications relevant to publishers, and digital rights management to include discussions on piracy and intellectual property. Together, both sessions will give a comprehensive overview of what is happening in the new digital arena.
Join us if you want to:
-Catch-up on the current state of digital transition
-Discuss emerging business models
-Examine the evolving digital devices and mobile applications used to disseminate content
-Gain insight on emerging piracy issues
This full day seminar will be invaluable to anyone interested in understanding the opportunities and challenges involved in delivering and marketing your content in a digital environment. This includes marketing coordinators, production managers, acquisitions editors, and senior management at small to medium-sized publishers of scholarly content currently in both book and journal form.
Web Application Development Tools for Creating Perfect User ExperienceChromeInfo Technologies
The era of technology today is composed of innovative applications, where web is taking the lead, check out this innovative series. So, we have put together a set of trendy tools and resources that will help you in web application development.
Everything Old is New Again: The State of Web DesignMaria D'Amato
Back to the Old School: Device-Independence with Responsive Design
Process: Art, Copy & Code: The New Creative Team
Embrace the Medium: Flat vs. Skeuomorphic Design
A talk given to the AOP Product Group, discussing the challenges with producing digital magazines that work across all devices. The problem is not delivery, but workflow. I talk about some of the design thinking and techniques that we have used to address this problem with Padify.
Is the mobile web enabled or disabled by design?Henny Swan
A look at mobile accessibility drawing on comparisons and lessons learned from desktop as well as looking ahead at existing and emerging technologies that help developers ensure content is accessible across devices.
Using Web 2.0 Tools inside Brightspace with an Eye on AccessibilityD2L
Learn about the use of free web applications inside Brightspace and find those that can be used effectively in an education environment. Discover at least four popular Web 2.0 tools that create significant accessibility barriers to students with disabilities, and about the techniques needed for creating alternative assignments or work-arounds for students who are unable to utilize inaccessible Web 2.0 tools.
Watch the webinar here: http://bit.ly/1McZHr2
Session at Mozilla Camp Europe 2011 in Berlin, Germany by Jay Patel & Jean-Yves Perrier about our work on the Mozilla Developer Network (MDN). Jay covers the evolution of MDN as a platform for developer engagement and Jean-Yves discusses our Web documentation efforts.
Similar to Progressive enhancement 2.0 what i'd like to share to designers (20)
2. Nicholas C. Zakas
A front-end consultant, author, and speaker.
He worked at Yahoo! for almost five years,
where he was front-end tech lead for the
Yahoo! homepage and a contributor to the
YUI library.
Nicholas is a strong advocate for
development best practices including
progressive enhancement, accessibility,
performance, scalability, and maintainability.
3.
4. Progressive enhancement uses web technologies in a layered
fashion that allows everyone to access the basic content and
functionality of a web page, using any browser or Internet
connection, while also providing an enhanced version of the
page to those with more advanced browser software or greater
bandwidth.
http://en.wikipedia.org/wiki/Progressive_enhancement
12. Reality:
not every browser can support all the different
technology
To support all browser in the same way,
•development takes too long
•too many bugs
•our pages are slow (bad performance)
•horrible user experiences
13. Developer may:
a.Limit the website's potential so that it will work
with older browsers
b.Not support some of the browsers
c.Use progressive enhancement to ensure that the
site can work on both modern and older browsers
14. Get angry if we see different from
different browsers?
Quality = The same across all browser?
Not Professional if it’s not consistent ?
Nicholas:
We obsessed with Identical experiences across all
browsers
35. It’s a progressive enhancement you can still attach a file by
clicking attach a file there if you don’t have drag-and-drop
36. The Gmail for the iPad also have the same elements just rearranged
a little bit to give a better experience on a tablet device
37. Can you tell the rounded corners only on Chrome and Firefox?
38. You will get a nice little notice that tell you you cannot use chat on
facebook in IE6
39. Nicholas:
Because they decided that It was too much work to
continue to support on IE6, when they could spend more
time on newer features for the more capable browsers.
“Chat is really the progressive enhancement. You
can go in, you can still see your timeline, you can
still do whatever, you just can’t chat. That’s an
added bonus you get only when you’re using a
newerget a nice little notice that tell you you cannot use chat on
You will browser, and that’s okay.”
facebook in IE6
40. There are little things based on capabilities at the time. Firefox didn’t have the
same fonts, CSS animations transition in order to create carousel
41. Nicholas:
“Whenever a user comes to the page, they get whatever
in the main point of the page.”
For Web sites, content is key
For Web applications, focus on 1 or 2 core features, that
are why people use your product.
There are little things based on capabilities at the time. Firefox didn’t have the
same fonts, CSS animations transition in order to create carousel
42. Summary
• Users care the content
• Users only use one browser
• Focus on the key features of your product
• Support the best possible experience, not the same
experience for everybody
• Give users an incentive to upgrade
43. Source
Progressive Enhancement 2.0: Because the Web isn’t Print:
http://www.slideshare.net/nzakas/progressive-enhancement-20-conference-agnostic
Nicholas Zakas: Progressive Enhancement 2.0 on YouTube:
http://www.youtube.com/watch?v=hdTxeR90_1E