English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 1h 06m | 190 MB
Modern development practices have shifted from thinking about entire pages to thinking about components and how to combine them to create views. This course looks at practical approaches to componentization and modularization to help you identify when a component is needed, what it does, and how to plan for and design portable and maintainable components of your own. As code componentization is relevant to all developers, instructor Morten Rand-Hendriksen shifts the focus away from coding and into the conceptual work that goes into component design. Using practical examples, Morten details how to sketch out and organize components in projects large and small. Learn about the four core principles of component development. Get tips and best practices for component planning. Plus, learn how to organize components and structure their markup, determine when (and when not to) focus on reusability, and more.
Table of Contents
Introduction
1 Components for the web
What Are Components for the Web
2 What are components for the web
3 Web components A special case
4 Why components are so popular
Components as a Mental Model
5 A mental model for components
6 Starting with a visual mockup
7 A DOM tree with branches and leaves
8 Tip Map your file tree to the DOM
9 Challenge Create a component map
10 Solution Create a component map
Component Principles
11 Loose principles for tightly scoped components
12 One-task principle
13 Top-down principle
14 Isolation principle
15 Stand-alone principle
Scoping Components
16 Plan before you code
17 Raw output
18 Properties
19 Input and output
20 State
21 Who owns state
22 Life cycle
23 Challenge Scope a complex component
24 Solution Scope a complex component
Practical Components
25 Structuring components
26 Reusability and when not to care
27 Stand-alone component development
Conclusion
28 Components everywhere
Resolve the captcha to access the links!