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

v1

code base

v2

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

  1. Request server side includes (header/scripts/footer) for application

  2. Meeting to go over timeline

  3. Wait for deployment to DEV/STAGE environment for testing

  4. Verify template looks good in DEV/STAGE

  5. Schedule Production deployment

  6. Deploy to Production 

Developer proecss

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

build dashboard

build project

the END

  • ASSETS repo  ssh://git@developer.acs.org:7999/acs/assets.git
Made with Slides.com