-
Notifications
You must be signed in to change notification settings - Fork 1
Best Practices for Website Development
The principle of progressive enhancement dictates that a web request should result in a legible document even with a downlevel browser with JavaScript enabled, or a text-based one such as eLinks. This principle is based on the fact that many people are accessing the web with old mobile phones or old hardware, such as schools or libraries, or countries where refurbished electronic devices have greater longevity. The principle also affects SEO and accessibility for the visually-impaired. (And it seems the default settings in Internet Explorer--which is still used by Luddite institutions--always have a bunch of features disabled.)
This means we should endeavor for Ajax-enabled websites to serve content in the first page response rather than loading the layout and then making an Ajax request for the content. Ajax can still be used for subsequent requests, but hyperlinks should have working urls in the event that JavaScript is disabled.
Pages in this wiki make use of the following resources throughout
- Martin, R. C., Feathers, M. C., Ottinger, T. R., Langr, J. J., Schuchert, B. L., Grenning, J. W., Wampler, K. D., ... Coplien, J. O. (2011). Clean code: A handbook of agile software craftsmanship. Upper Saddle River [etc.: Prentice Hall.
- Lowy, Juval, (July 2011). “C# Coding Standard: Guidelines and Best Practices.” (Version 2.4) www.idesign.net, © 2011 IDesign Inc.
Resources besides these will be referenced directly where they are cited.