Add todo list + kv tutorial to docs

[kristianfreeman]

Waiting on cloudflare/wrangler-legacy#203 before this can be merged - KV namespace support in wrangler shouldn't be in documentation until it's out, on a released version. Still ready for review in the meantime :)

[xortive]

Overall really like this tutorial. Only really needs some branding changes (s/worker/workers) for consistency.

[exvuma]

I think this tutorial is phenomenally helpful, but I wish I could find this information in the reference docs without being walked through another tutorial.

We should be careful about adding anymore tutorials (there are already 4) in the future, and instead add information the the existing tutorials (e.g. using KV to store the API keys from slack bot tutorial..? ). Ideally one could go through just 1 tutorial and be on boarded with an imagination of what Workers can do and one could go through 3 tutorials and get a comprehensive understanding of all of Worker's flagship capabilities. Asking one to pick from 4+ tutorial losses a lot of audience and a lot of attention.

I suggest we 1. focus on giving KV ref docs love 2. incorporate KV to one of the existing tutorials.

[kristianfreeman]

I think this tutorial is phenomenally helpful, but I wish I could find this information in the reference docs without being walked through another tutorial.

I agree, we should have accompanying docs for the "happy path" of KV (using it with Wrangler) in the Reference part of our docs. I know some conversations have been happening about the KV section of the docs, and I imagine that either adding info about the Wrangler integration, or just linking to the Wrangler docs specifically (or the README) would cover help alleviate this.

That being said, l still think this should be a flagship tutorial, listed in the sidebar. I don't personally feel like five tutorials are too much cognitive overhead for devs to choose from, and the concepts in this tutorial, in particular, are useful and approachable in a way that some of the other ones (i.e. the Slack/GitHub webhook tutorial) aren't:

• Rendering HTML/CSS/JS from in the browser
• (obviously) using KV in Wrangler and in your actual code

I think the work in #290 is going to support how we build new educational content in the docs in the future, but I'd like to proceed with adding this tutorial, and continue to think about how to present this kind of info throughout the site!