background preloader

Best practices

Facebook Twitter

An old guys guide to building modern websites. Season 2: The estimated time to read this article is 12 minutes Subscribe to this podcast using iTunes or RSS | Download this show When you have such a talented bunch of coders you don’t tend to code much yourself.

An old guys guide to building modern websites

However, when it came to boagworld I was determined to do the majority of it myself. I had two reasons for this. What We Don't Know. We don't know which browser, which version of that browser, or what kind of computer a user visiting our website is using.

What We Don't Know

That's why we have web standards we follow which give us the ability to code one website that can work everywhere. We use normalized templates (e.g. HTML5 Boilerplate) to give our projects a consistent and healthy starting point. We use JavaScript libraries (e.g. jQuery) to make things easier for us an alleviate cross browser issues. We don't know the capabilities of the browser the user is visiting our website with. So we feature test and polyfill where we can. We don't know what the size of browser window is of a user viewing our website. So we should design our sites to be fluid and utilize media queries to optimize the site for any screen size (responsive web design).

We don't know what the internet connection speed is of a user viewing our website. So we try and load as few resources as possible. We don't know the mindset of a user viewing our website. Share On. Web Standards Sherpa. Front-end Code Standards & Best Practices. Overview This document contains guidelines for web applications built by the Creative Technology (front end engineering) practice of Roundarch Isobar. It is to be readily available to anyone who wishes to check the iterative progress of our best practices.

This document's primary motivation is two- fold: 1) code consistency and 2) best practices. By maintaining consistency in coding styles and conventions, we can ease the burden of legacy code maintenance, and mitigate risk of breakage in the future. By adhering to best practices, we ensure optimized page loading, performance and maintainable code. Pillars of Front-end Development ◊ General Practices ◊ Indentation ◊ For all code languages, we require indentation to be done via soft tabs (using the space character). Readability vs Compression ◊ We prefer readability over file-size savings when it comes to maintaining existing files. The first component of any web page is the tag-based markup language of HTML . Template ◊ Doctype ◊