Format

This guide will be written loosely in the format of a book about web application development.

In reality, a web application in the modern world can mean many things. Similar to programming, it can be rather helpful to avoid treating things as monoliths, and instead breaking them down into components. That same direction will apply here. The various chapters will reflect standalone concerns or components as much as possible. Based on business requirements, your application may include just one or all the components you may find here.

For each component, I’ll try and explain the concerns purely in English, being as tech stack agnostic as possible: fomenting on the requirements, possible features, and possible pitfalls. Then, we will look at the ecosystem for what’s available to implement this component, and weight the pros and cons. Finally, we will pick a concrete tech for this component, and include some basic examples of what the component might look like in the wild. Through this method, most of the content should be re-usable for any language.

• Agnostic
• Ecosystem
• Concrete

disclaimer: I haven’t quite decided whether it works better as a book format or as a conventional list of articles blog format.

Home | Go back | Next up