Improve environment specific build process for front end

[cchojnacki]

Currently Grunt is configured to target development and production. Front end build system could use a few improvements

1. Development build includes authentication code segments that the developer is required remove manually. Build configuration could be improved to remove authentication code automatically. Overall build system could be improved to use templates.
2. The development and production build appear to have minor differences related to css and html. The minification process could be causing this and should be looked into

[jassoncasey]

It would be nice if we had three grunt development options:

• just frontend
• frontend + remote backend (dev)
• frontend + local backend

[cchojnacki]

can the gruntfile be modified to do the following?

• 'grunt serve:auth' launches the frontend in an authenticated state
• 'grunt serve' launches the frontend in an unauthenticated state

[cchojnacki]

Front end build has been configured to be able to launch

• grunt serve - will launch frontend without the need to auth (you will still need to login, but any credentials will authenticate you)
• grunt serve:local - will launch the frontend that is connected to a backend database, so you will be able to save assets to backend during deveopment