Add some kind of notice to forewarn folks stumbling upon the site that it's not production-ready and that any data they enter will most likely be wiped.

Before a valid request is redirected (#4) to the destination URL we should:

• Increment the hit count for the slug
• Log the requester's IP address
• Log the request's referrer

Do not comment on this issue.

This is the ship list for the initial functional release.

Features

General

• #2 Test notice (tell folks stumbling upon the site that their data won't be saved forever)

Home Page

• #3 Enter a URL to shorten or track. Redirect a recognised URL or slug to its tracking page

Routing

• #4 Redirect requests for valid slugs to the destination page
• Gracefully handle 404s

Tracking

• #5 Number of requests
• #5 IP address
• #5 Referrer

Stretch Goals

• Allow entering a custom slug when shortening a URL
• Realtime stats on tracking page
• #6 List recently shortened URLs on the home page

It should be possible to quickly add or track a URL directly from the main page by simply entering a URL or slug; if we recognise the URL or slug we'll present a link to its tracking data, otherwise we'll show the interface to shorten a URL prepopulated with the URL or slug as appropriate.

When a request for a valid slug is identified, record some basic tracking (#5) stats and redirect to the destination URL. For instance, a request for http://twa.io/dino might direct the visitor to some house-stomping goodness.