<p>Jeff mentioned the concept of 'Progressive Enhancement' when talking about using JQuery to write stackoverflow.</p>

<p>After a quick Google, I found a couple of high-level discussions about it.</p>

<p>Can anyone recommend a good place to start as a programmer.</p>

<p>Specifically, I have been writing web apps in PHP and would like to use YUI to improve the pages I am writing, but a lot of them seem very JavaScript based, with most of the donkey work being done using JavaScript. To me, that seems a bit overkill, since viewing the site without Javascript will probably break most of it.</p>

<p>Anyone have some good places to start using this idea, I don't really care about the language.</p>

<p>Ideally, I would like to see how you start creating the static HTML first, and then adding the YUI (or whatever Ajax framework) to it so that you get the benefits of a richer client?</p>

[{'answer_id': 2500, 'author': 'GateKiller', 'author_id': 383, 'author_profile': 'https://Stackoverflow.com/users/383', 'pm_score': 4, 'selected': False, 'text': "<p>As you've said</p>\n\n<blockquote>\n  <p>To me, that seems a bit overkill, since viewing the site without Javascript will probably break most of it.</p>\n</blockquote>\n\n<p>This isn't progressive enhancement. Progressive enhancement is when the site works perfectly without JavaScript or CSS, and <em>then</em> adding (layering) these extra technologies/code to increase the usability and functionality of the website.</p>\n\n<p>The best example I can give is the tag input box on this website. With JavaScript turned off, it would still work allowing you to enter tags separated with a space. With JavaScript turned on, you get a drop down with suggestions of previous entries.</p>\n\n<p>This is progressive enhancement.</p>\n"}, {'answer_id': 2506, 'author': 'palehorse', 'author_id': 312, 'author_profile': 'https://Stackoverflow.com/users/312', 'pm_score': 2, 'selected': False, 'text': '<p>Going at it from the other direction is sometimes referred to as graceful degradation.  This is usually needed when the site is built first with the enhanced functionality afforded by the various technologies then modified to degrade gracefully for browsers with those technologies are not available.</p>\n\n<p>It is also graceful degradation when designing to work with older browsers (ancient in the Internets terminology) such as IE 5.5, Netscape, etc...</p>\n\n<p>In my opinion it is much more work to gracefully degrade the application.  Progressively enhancing it tends to be much more efficient; however, sometimes the need to take an existing app and make it accessible in these lacking environments arise.</p>\n'}, {'answer_id': 2514, 'author': 'sparkes', 'author_id': 269, 'author_profile': 'https://Stackoverflow.com/users/269', 'pm_score': 4, 'selected': True, 'text': '<p>See also <a href="http://en.wikipedia.org/wiki/Unobtrusive_JavaScript" rel="nofollow noreferrer">Unobtrusive JavaScript</a> which is the bedrock progressive enhancement is built.</p>\n'}, {'answer_id': 2598, 'author': 'EndangeredMassa', 'author_id': 106, 'author_profile': 'https://Stackoverflow.com/users/106', 'pm_score': 2, 'selected': False, 'text': "<p>Basically, if your site still works with JavaScript turned off, then anything you add with JavaScript can be considered progressive enhancement.</p>\n\n<p>Some people may think that this is unnecessary, but plenty of people browse with addons like NoScript (or, with JavaScript simply turned off in their browser settings). In addition, many Mobile web browsers may or may not support JavaScript. So, it's always a good idea to test your site completely with and without JavaScript.</p>\n"}, {'answer_id': 99670, 'author': 'zobier', 'author_id': 18469, 'author_profile': 'https://Stackoverflow.com/users/18469', 'pm_score': 2, 'selected': False, 'text': '<p>This is such an important concept and it saddens me that so few web developers understand it.</p>\n\n<p>Basically, start by building a site/framework in Plain Old HTML -- structural elements, links and forms. Then add on some style and then shiny stuff (Ajax or what have you).</p>\n\n<p>It\'s not very difficult. Like <a href="https://stackoverflow.com/users/312/palehorse">palehorse</a> says, graceful degradation is more work.</p>\n\n<p>Websites should work in any user agent, not look the same (not even look but sound if your vision impaired), just work.</p>\n'}, {'answer_id': 3302017, 'author': 'Xeoncross', 'author_id': 99923, 'author_profile': 'https://Stackoverflow.com/users/99923', 'pm_score': 2, 'selected': False, 'text': '<p>Progressive Enhancement:</p>\n\n<ol>\n<li>The plain HTML/CSS site is awesome (<em>fully working and user-friendly</em>).</li>\n<li>Adding JavaScript defines a new level of awesome.</li>\n</ol>\n'}, {'answer_id': 13032144, 'author': 'Jeromy French', 'author_id': 1430996, 'author_profile': 'https://Stackoverflow.com/users/1430996', 'pm_score': 2, 'selected': False, 'text': '<p>Progressive Enhancement is a development technique that stresses the primacy of the semantic HTML, then testing for browser-<em>capability</em> and conditionally "layering" on JavaScript and/or CSS enhancements for the browsers that can utilize those enhancements.</p>\n\n<p>One of the keys is understanding that we\'re testing for what the browser can <em>do</em>, as opposed to browser-<em>sniffing</em>. <a href="http://modernizr.com/" rel="nofollow">Modernizr</a> is a very popular browser-capability test suite.</p>\n\n<p>Progressive-Enhancement is inherently (section 508) accessible; it provides for meeting the letter of the law <em>and</em> the spirit of the rule.</p>\n\n<p>The Filament Group wrote the excellent "<a href="http://filamentgroup.com/dwpe/" rel="nofollow">Designing With Progressive Enhancement</a>" book on the subject. (I am not affiliated with Filament Group, though they are so freaking smart I wish I were.)</p>\n'}]
['https://Stackoverflow.com/questions/2486', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/277/']