A webapp commissioned by the Australian Government's Department of Veteran Affairs to help with tips, tools and strategies that can reduce the impact of drinking on your lifestyle.

  • As the frontend framework.

  • Serving any and all static content to the client.

  • Caching static content requested by Drupal.

  • Translating saved user data that's returned from the database into useful, visually appealing user feedback.

  • Restyling and reflowing HTML5 content to better suit the browser's specific context.

  • As the dashboard for collating various user behaviours and for providing a familiar interface that will be understood by the business.

  • As the baseline database in which to:

    • install Drupal core
    • store any data created by the user during a session

  • Serving any and all dynamic content to the client.

  • To provide any vendor modules used within the frontend build, mainly AngularJS libraries.

  • Scaffolding the project's file directory as well as the AngularJS boilerplate.

  • As the main frontend build tool, covering:

    • bower dependency injection
    • deployment methods
    • build versions i.e. dist, local server etc.

  • For small tasks deemed necessary by Drupal.

  • REST API development and testing.

  • To track server health and monitor all stats.

  • As the version control directive.

  • As the serverside code editor for config files modification.

  • As the public code repository to hold any forked libraries and/or frameworks that might have been integrated.

  • As the app's CMS and CRM.

    It is being used in a headless state and is completely decoupled from the frontend; only serving it's content to the AngularJS framework via a RESTful API.

  • The version controlled repository to house all development and track any changes.

  • Time tracking for that, spent while working across multiple components and using multiple languages.

  • Localised testing of the prototype stack before deployment.

  • Bug tracking and change requests.

  • Team communication and project notes.

  • As part of the cacheing system within Drupal.

    Memcached mainly took care of creating and rebuilding the REST API cache once changes had been made within Drupal.

Verified by

Stack Match