Angular 2.0

Plan for department adoption

Three Streams of Work

• Training / Knowledge Building
• Architecture / Approach / Standards
• Existing Application Strategy

We believe these can be started to be progressed in parallel but do have some ultimate dependencies

Training / Knowledge Buidling

• Consistent level of understanding
• Be able to build a simple application applying core concepts
• Be able to input and appraise proposed architecture / approach / standards

Team Objectives

• Some form of interactive workshops / learning routes with team 
• Three core areas
• Spaced apart with time in between to digest them
• Work on the content of these for the remainder of the year
• Start in anger in January

Current Thinking

Proposed Workshops / Learning Areas

1) ES6, TypeScript, Transpiling, Web Components, Simple Build

Workshop: 1 Day | Digest: 1 Week

2) Angular 2.0 Fundamentals

Workshop: 2 Days | Digest: 2 Weeks

3) Bring together knowledge and architecture / approach / standards

Workshop: 1 - 2 Days | Digest: 2 Weeks

Resources

• Software Architect G Fink: ES2015
• ng-book 2: https://www.ng-book.com/2
• Egghead: https://egghead.io/technologies/angular2
• AngularConnect 2015: video resource
• Thoughtram
• Rangle.io
• AngularClass

We do not want to reinvent the wheel or create necessary work for ourselves so will utilise existing materials where appropriate to help make most efficient use of time. 

Concerns / Dependencies

• We are still learning, hence "knowledge building" and "consistent level" objective
• Angular 2 documentation still being formalised
• Final learning area dependent on formalising architecture / approach / standards

Architecture / Approach / Standards

• Define coding standards
• Support workflow > development, testing, builds, deploying
• Define architecture / code structure, best practice, styling, approach to working with data (services)
• Provide options for consumer approach

Objectives

Concerns / Dependencies

• No final decision on services end output and how we will work with them (architecture, workflows, business process v domain, hypermedia etc), influences "approach"
• Still a fair bit to research and learn in order to formalise architecture / approach / standards
• Need some form of steer on consumer approach (devices, offline etc)

Existing Application Strategy

Some Options

• Do nothing with them
• Move all together (not NG2 related)
• Prepare them for NG2 article
• Big bang / incremental

Concerns / Dependencies

• Need internal landscape discussion external to NG2?