Create demo TOM app repo and include existing integration points

[jchate6]

We should make a repo with a demo app built to provide an example for all of the customization features that should be available for a tom admin/developer.

This should have a well documented readme and include all of the available integration points.

• Initialize repo
• incorporate target button integration points from TOM TNS
• Incorporate nav bar Integration Points from TOM-Alerts
• Incorporate example of extended target model

[phycodurus]

Some things we've talked about wrt to the Demo App:

• the app demonstrates the integration points INSTALLED_APPS can use to interact with the base TOMToolkit (tom_base).
• will at some point provide a template that TOM developers can use when developing INSTALLED_APPS for their science use cases
• should exemplify an architecture that separates Astronomy "business logic" from Django-y web framework code. So,
  • View methods and management command run methods should be largely free of business logic and call out to Astronomy specific modules.
  • For example, View classes should keep to the responsibility of receiving HTTP requests and returning HTTP responses by constructing a context dictionary and rendering it into a template. (Astronomy-specific code should be refactored out).
  • Likewise, management commands mainly parse args and call out to Astronomy-specific code (that has perhaps been refactored out of a View method or run() method.
  • By keeping business logic out of View (and management command) methods, it
    • can be invoked from both Views and management commands, etc
    • is more testable than code buried in View methods
    • allows TOM developers to focus more on science use cases and less on web frameworks