I'm surprised that this was built in a way where it's possible to throw a 500 error. This is a simple website. Why isn't it just a couple of static pages?
Here's something for your checklist: Make sure you use an appropriate technology for the problem you're solving.
While it's down, those checklists are available on github[1]. I wondered whether they are general/reusable, but apparently it's mostly organizational (and rather specific) checklists of a software company as of now.
Hi folks, I'm Flávio from Vinta. Someone posted this before we made it almost-static and therefore HN-ready, so sorry for the issues! We were planning to launch it with more checklists and a better backend. For now, in case you face issues, please try the original markdown versions on GitHub:
Before I give you feedback on your wonderful set of checklists, wanted to give you some background for this message.
Last Thursday was Global Accessibility Awareness Day, which I cofounded. A day meant for developers and designers to learn about the importance of coding accessibility. This is for the purpose of making it possible for people like my friend Tommy Edison to use the web. Here's a demo of him using a screen reader: https://www.youtube.com/watch?v=UzffnbBex6c
What's really important for accessibility is that sites that focus on teaching coders get accessibility right. It would be great if you added an accessibility checklist as well. For example https://www.wuhcag.com/wcag-checklist/.
having a look at some of these on github ( as the software 500s ), they aren't really checklists, they are more like guides where various points in the guide are simply given a check box.
