Feedback/run-through: Guides, Build an Application: "Tutorial" about workers-docs HOT 3 CLOSED

If y'all need additional help testing things I'd be happy to attempt it myself / pull in random engineers around the office for some quick hallway testing. Let me know!

from workers-docs.

• remove all info about getting API keys/tags and just link, i didn't want to share my global API key so I used service keys
• []

from workers-docs.

• You used italics a lot when I think you meant to use bold or code
• Instead of directory screen should use file hierarchy tree
• Remove instructions on how to get API key, but do talk about account selection
  • I am owner of A but have access to B, what do I choose for account ID versus API key?
• Remove signalnerve and use workers-tooling.cf or zoneless on Workers Tooling account
• For routes make sure to denote that the subdomain must have a DNS record if not using zoneless
• The organization was confusing to me, I think you should make it very easy for someone to find all of the configuration (from github, slack) and all the code. With that:
  • Move the generate section either at the very end or the very top but not in the middle
  • Developers don't like to read they skim, so make sure to have to essential pieces out in the open and obvious and not embedded in the paragraphs
  • Don't need to repaste the either lookup.js every time you mention it. Just show the code and the neighboring code and use "…" and at the end of talking about whatever file use the complete code
• Since some might not have wrangler, I think dividing serverless/wrangler implementations could be extremely useful
• Section "Build" is a confusing title since it's not actually building
• Even though users are expecting to replace myworkersurl.com, still allow them to copy paste the values to put into slack (e.g. owner/repo#issuenumber, https://myworkerurl.com/lookup., … all copy pasteable and together
• https://github.com/user/repo/settings/hooks change to https://github.com/user/repo/settings/:your-repo
• Have cohesive path on how to get to the configure pages, either link to a github article to do so, or at the end of all the descriptive text say home > projects > add hook > blaah
• Test issue in github, it's actually a really useful debug tool I love for webhooks: https://cl.ly/ccb39ce52806
• Doesn't actually work for me :( help? https://github.com/victoriabernard92/build_an_app

from workers-docs.