jrista / taic Goto Github PK

The IOTW REST API requires a basic data service:

• FindAll
• Create

The links on the navigation bar are not actually navigating. Incorrect bindings for route names.

The IOTW REST API needs a basic service:

• GetList
• Post

The TAIC web site will contain a single navigation bar beneath the site header. This navigation bar will contain a number of menu links to primary site areas, as well as a search bar. The search bar will be disabled until such time as search is implemented. The menu links should function from a visual standpoint, but will not link anywhere until such time as each section has been implemented.

A new separate site is required for the TAIC Admin angularjs site. This site will need to be separate from the main site, and potentially independently deployable.

• Create style infrastructure
• Add core angular modules and reference core dependencies
• Add configuration for key third-party modules:
  • Local Storage
  • Caching
  • Restangular
  • Markdown
• Set up route tracking and error handling
• Create root view infrastructure

A custom page management UI is required. The public site will support multiple custom pages, including the About page, that can be edited by site admins.

• Create listing & editing views
• Create listing & editing routes
• Create data service
• Create resource service

The Pages REST API requires a fully featured data service:

• FindAll
• Find (By Name, By Page)
• Create
• Update
• Remove

A new REST API to save and retrieve site settings is reqired:

• Get
• Put

A site settings management UI is required. The public site will support a live youtube feed, live show schedule, support toggleable on/off (for maintenance), etc.

• Create settings view
• Create settings route
• Create data service
• Create resource service

The Pages REST API requires a fully featured route:

• Get (By Name, By Path)
• GetList
• Post
• Put
• Delete (By Name, By Path)

The ability to upload an image for a new IOTW winner for display on the main site is required.

• Upload high res winning image
• Post cropping details
• Post winner details
• Update currently used "winner"

The TAIC web site will be a primary exhibition point for their Image of the Week contest winners. Winners will have their work shown on the site in several ways, including in the site header. The winner image will be exhibited via the following:

1. As the banner of the site header.
   • Will be cropped to fit.
   • The full name of the winner will appear over their image in the lower right
   • The winners name will be contained within a semi-transparent box
2. Moderately blurred out as the background of the TAIC logo in the site header.

The TAIC logo will be embedded within the blurred out copy of the winner's image. Over this image, the TAIC byline will be placed.

A site status dashboard UI is required. This will show current site status and settings config, and eventually support live analytics.

• Create dashboard view
• Create dashboard route

Log startup:

• Log prepared routes
  Log requests.

Add a Node.js server and root application.

Configure and start up Express server.
Prepare environment configuration wrapper.

A general purpose route is required for customizable "pages" edited in the adminiatrative tools. This route should support any number of pages using the /taic/pages* route, supporting any number of page names.

A controller and set of services will be required to support retrieval and rendering of Markdown content saved for each page.