ACS Assets Architecture

by Joanna Ho | j_lit@acs.org

Web Strategy and Operations UX

Assets is a front end server for acs.org and ACS internal / external applications.

What is Assets?

Assets commonly served up CSS stylesheet, javascripts, images, fonts, and server side includes to provide the front-end/UI layer of the site or application

Benefits of using assets

Consistent look and feel of the ACS branding
ACS bootstrap ready to provide UI quick-start
Front end / mobile support
Compiled / Optimized JavaScript, CSS and Images
JavaScript Documentation
Code Review
Bug and Feature Request Tracking
Automated Code Deployment
Automated Functional and Unit Testing
Version Control

There are currently over 40 ACS sites and applications that are using the assets as their front end server

How it is organized

code base

Full template

Minimal template

Standardized style

http://bit.ly/1BYsL1L

ACS Bootstrap

Grid System

Responsive

Typography

Tables

Forms

Buttons

Icons

<more>

ACS Bootstrap

Grid system

ACS Bootstrap

ACS Icons

Business unit proecss

Request server side includes (header/scripts/footer) for application
Meeting to go over timeline
Wait for deployment to DEV/STAGE environment for testing
Verify template looks good in DEV/STAGE
Schedule Production deployment
Deploy to Production

Developer proecss

Developer receives story/bug/feature request from Jira
Developer checks out some code from Stash via Git
Developer make changes
Developer runs the assets GRUNT build script to test locally
Developer commits changes back to Stash via Git
Developer adds a comment to the commit linking it to corresponding Jira issue
Bamboo automatically runs a Development build
Code is ready for testing in Development
Developer confirm code in Development environment before marking ticket to Ready to Test
Code is ready for testing in Staging and is now going through WSO QA testing process.
WSO Quality Assurance runs a Production Build after obtaining CCB approval