Technical details that a programmer of a web application should consider before making the site public.

Download as .zip Download as .tar.gz View on GitHub

Webapp Checklist

Technical details that a programmer of a web application should consider before making the site public.

The idea here is that most of us should already know most of what is on this list. But there just might be one or two items you haven't really looked into before, don't fully understand, or maybe never even heard of.

Interface and User Experience



SEO (Search Engine Optimization)


Bug fixing


This was originally a question asked on Programmers-StackExchange by Joel Coehoorn and has since been answered and maintained as community wiki.

There are three reasons why I am making a GitHub repo:

  1. Collaborative editing is much more powerful on GitHub.
  2. People can fork this repo and make customizations that might not apply to everyone else.
  3. We can have translations of the answer in many languages. Not everyone is good with English.


What things should a programmer implementing the technical details of a web application consider before making the site public? If Jeff Atwood can forget about HttpOnly cookies, sitemaps, and cross-site request forgeries all in the same site, what important thing could I be forgetting as well?

I'm thinking about this from a web developer's perspective, such that someone else is creating the actual design and content for the site. So while usability and content may be more important than the platform, you the programmer have little say in that. What you do need to worry about is that your implementation of the platform is stable, performs well, is secure, and meets any other business goals (like not cost too much, take too long to build, and rank as well with Google as the content supports).

Think of this from the perspective of a developer who's done some work for intranet-type applications in a fairly trusted environment, and is about to have his first shot and putting out a potentially popular site for the entire big bad world wide web.

Also, I'm looking for something more specific than just a vague "web standards" response. I mean, HTML, JavaScript, and CSS over HTTP are pretty much a given, especially when I've already specified that you're a professional web developer. So going beyond that, Which standards? In what circumstances, and why? Provide a link to the standard's specification.