A
A
Serif
Sans
White
Sepia
Night
Star (
-
)
Watch (
-
)
How to Build Front-End Web Apps that Scale
About the author
Questions and Issues
Edit and Contribute
Introduction
1.
Workshop Overview
1.1.
Who are we?
1.2.
Schedule
1.3.
What we're going to learn
1.4.
What we're going to build
1.5.
Organisations & Teams
1.6.
Prerequisites
1.7.
Heads Up!
2.
KnockoutJS
2.1.
Exercise: KnockoutJS
3.
Background
3.1.
What is a Large Scale Front-End App?
3.2.
Large Codebase
3.3.
Example Large Codebase
3.4.
Complexity
3.5.
Gmail
3.6.
Caplin Trader
3.7.
Large SPAs
3.8.
Contributors
3.9.
Who Contributes?
3.10.
Lots of Questions?
3.11.
Workshop Approach
4.
Features/Blades
4.1.
Overview
4.2.
Problems Solved
4.3.
Where's the Code?
4.4.
Who Broke the App?
4.5.
F5 is the New Compile
4.6.
Exercises
4.7.
Exercise: Input
4.8.
Exercise: Messages
4.9.
Exercise: User Card
4.10.
Retrospective
5.
Apps & Aspects
5.1.
Composing Blades into Aspects
5.2.
Retrospective
6.
Services & the ServiceRegistry
6.1.
Services
6.2.
ServiceRegistry
6.3.
Problems Solved
6.4.
Developer Environment Dependencies
6.5.
Required Dependencies
6.6.
No Backend Dependencies
6.7.
Configuring Services
6.8.
Workbenches
6.9.
Modular App Services
6.10.
Modular App Services
6.11.
User Service
6.12.
Chat Service
6.13.
Exercises Overview
6.14.
Exercise: Input Blade & Services
6.15.
Exercise: Messages Blade & Services
6.16.
Exercise: User Card Blade & Services
6.17.
Retrospective
7.
Apps & Aspects (again)
7.1.
Retrospective
8.
Extras
9.
That's a Wrap!
10.
Reference
10.1.
Suggested Dev Setup
10.2.
FAQ & Gotchas
Services & Service Registry Retrospective
How does this relate to the concepts?
Building features without the real services in place
Services facilitate workbenches
Full feature testing
What problems did it solve?
What did the tooling do and how did it help?
What other tooling could achieve similar things?