Refactor server code & tutorial to be easy to describe & memorize

[benholland1024]

This issue deals with human cognition as much as code style probably.

What makes code easy to describe & memorize?

• Discrete, name-able, catagorizable parts
• Small numbers of categories

• Good documentation

  The file server.js is first created in v1 part A, just to serve static files and assets. The final server.js has the following duties:

  • Serve static pages, like /register or /
  • Serve static assets, like /logo.png or /fonts/CrimsonText.ttf
  • Dynamic pages: public, like /lessons/woodworking/1, and private, like /ben/secrets
  • Dynamic assets: public, like /ben/circularsaw.png, and private like /ben/passwords.txt
  • API GET and POST methods

[benholland1024]

When server.js recieves a new HTTP request, here's what might happen:

• If It's a static page...
  • Insert static page into index.html, then respond with the whole thing
• If it's a static asset...
  • Find the MIME type, then respond with the asset
• If it's a dynamic page...
  • If it's a "reserved dynamic route", find the page file, insert into index.html, then respond
  • If it's not, try to find a page at that file path. If it's public, insert into index.html, then respond.
  • If it's private or nonexistent, send the 404 page.
• If it's a dynamic asset...
  • Same conditional logic as for a dynamic page but find MIME type, and don't insert into index.html
• If it's an API request...
  • Use the route and method to find the appropriate API function, let that function handle it.
  • Most API functions require some data either in the body, the route params, or both. This needs parsed.
  • API functions respond with response codes and data

[benholland1024]

The list above is memorizable.

There are some other functions that need to be added, to "factor out" functionality of the list's functions. For example, inserting a page into index.html, or responding to a API request.

It's always going to take some time to describe.
The goal is a description that makes sense consistently and efficiently. (And code that works!)