Organic Web Technology

A design philosophy

Front end web development has become quite complex. The exponential growth of tooling options is undeniably a Good Thing but now we as developers need to take a step back. We need to evaluate our needs with a sober un-biased eye. We have proven that we can build highly complex apps and we now must challenge ourselves to build the simplest apps possible.

The Organic Web philosophy proposes that we know the ingredients in our apps. If it does not have a clear and compelling purpose, it's probably not healthy.

Web standards make our lives easier. Apps that follow and embrace web standards are future-proof and lovely to work on. Think very carefully whether the job at hand can be done using a standards-compliant technique, before relying on a third-party library to handle the task.

When writing custom code or employing third-party libraries, strive to code with the utmost clarity. Code should be parseable and understandable at a glance. Not only will this make maintenance easier but it will encourage you to make logical choices during the development process.


Minimize Complexity

Use the simplest possible tool to complete the job. We all love our front end frameworks and our build systems... But sober architecture at the outset of a project will save much unnecessary effort down the road.

Use Native Functionality

Prioritize the use of native functionality before resorting to custom or third party solutions. At the most basic level, this means using semantic markup. Do not fight the browser. Use what the browser provides, and only supplement as absolutely necessary.

Maximize Clarity

Architect apps in such a way that they explain themselves. Spend energy making your intentions apparent to any reader of the code. There should be no doubt as to the purpose of any given piece of code.


Check back here as more tools and resources are added, and/or make suggestions!

Complementary Philosophies