Web 2.0 means different things to different people. Here, it refers to the designs and technologies used to implement modern, user-friendly Rich Internet Application ( RIA ) sites.
However this doesn't include any of the third-party 'eye-candy' libraries and frameworks that currently exist, such as JQuery. These contribute little or nothing to usability while bloating page sizes and slowing down site loading.
This site provides working examples of designing and developing web sites without using these libraries and frameworks, and without relying on features in specific HTML versions beyond HTML 4.01. The focus is on building usable web sites, with design and coding blended in a practical, state-of-the-art guide to creating cross-browser Web 2.0 RIA sites in the simplest way that achieves the desired end result.
The web site architecture used here to implement Rich Internet Applications is pragmatic. A single code base is used for cross browser-compatible Web 2.0 RIA 'Master Pages' that pass W3C validation.
Server-side code should only run functions that absolutely must execute on back-ends, such as database SQL queries. And the use of back-end pages to write front-end pages' structure to browsers should be avoided, and they should just write the server-side data they access to front-end pages that load this content into the appropriate section of the page / site.
Whatever type of server-side pages are employed, client-side browsers use the DOM to swap old content out of view, format and write new content to front-ends, and swap new content into view. Examples show returned data from partial and whole HTML pages, database SQL query results from PHP pages, remote domain mashups, information delivered in data arrays such as .CSV and JASON, and more.
Many different browser vendors and versions exist, so cross-browser solutions are provided that run in Internet Explorer ( IE ) 6, 7, 8, 9, 10, and 11, Firefox, Chrome, Opera, and Safari, under various Operating Systems, without third party libraries or frameworks.
HTML is fault-tolerant, with its ability to ignore new entities that will be defined in future releases of HTML, and that current and older versions cannot render. And the concepts of fault-tolerance and avoidance, internally in web page code, are covered.
Dividing functionality between front-end UI code, server-side code and databases, and graphics production and design, will be discussed. And the use of version control, both locally on development systems, and on servers used for hosting, will also be covered