[Standards]: Modularity and decoupling of code

[joshbruce]

Issue type

• Standards & approach

Description

During R7S5 retrospective the notion of making sure our code is being developed in a modular and decoupled fashion came up. While not a specific action item for R7S6, believe this conversation is worthwhile.

During reviews I've seen a few areas where we can decouple concepts:

1. User interface components as Angular 2.0 components.
2. Interfacing with the APIs - an "API Kit".
3. SAM Web Design Standards CSS, JS, and the US Web Design Standards.

@carlosvalle @JihadMotii-REISys @diego-ruiz-rei @tarandhupar @jagannathch

[joshbruce]

We had a follow-up workshop related to the future of the SAM Web Design Standards. Believe it would be prudent to begin considering folder structure for the Angular 2.0 components. Maybe follow the deprecated UI Kit, which follows the SAMWDS stylesheets...??

Creates a single mapping across the repositories.

[jbabbs]

This is only in regards to the App module for the sam-front-end project.

I really like the REI approach of separating the top-level routes into their own module. I also like @JihadMotii-REISys 's approach of defining the program route, within the search module (see program.routing.ts).