Slide 1

Slide 1 text

Modular Front-End Architectures @bermonpainter | Great Wide Open

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Patterns The foundation of repeatable interactions that when combined create rich and complex systems.

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Benefits A useful tool to use when breaking down a user interface into it’s most modular pieces, instead of thinking about things as a series of disconnected pages.

Slide 7

Slide 7 text

Benefits 1. Collaboration

Slide 8

Slide 8 text

Benefits 1. Collaboration 2. Language

Slide 9

Slide 9 text

Benefits 1. Collaboration 2. Language 3. Consistency

Slide 10

Slide 10 text

Benefits 1. Collaboration 2. Language 3. Consistency 4. Efficiency

Slide 11

Slide 11 text

Benefits 1. Collaboration 2. Language 3. Consistency 4. Efficiency 5. Speed

Slide 12

Slide 12 text

Benefits 1. Collaboration 2. Language 3. Consistency 4. Efficiency 5. Speed 6. Maintainability

Slide 13

Slide 13 text

Static Style Guides Built with (or generated) static HTML. They are standalone representations of modules that are build separately from your applications.

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Living Style Guides Generated HTML, typically created from parsing documentation created as comments in CSS files.

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Challenges You’ve implemented a pattern library. Now what? It’s difficult it is to get buy-in, train teams, maintain the codebase between the pattern library and one or more applications, deal with technical debt, etc.

Slide 26

Slide 26 text

Challenges Adoption If the people that manage the money don’t see or understand the value in a pattern library, the won’t dedicate the time, resources, and budget to maintain one.

Slide 27

Slide 27 text

Challenges Governance Loose collaboration will fail. The must be a framework that clearly defines roles, responsibilities, and who have the authority to make decisions and provide a clear direction to the team.

Slide 28

Slide 28 text

Challenges Application The entire team must be on board on writing patterns, following code standards, and maintaining the patterns.

Slide 29

Slide 29 text

Challenges Abstraction “Duplication is far cheaper than the wrong abstraction.” – Sandi Metz

Slide 30

Slide 30 text

Conventions SMACSS, BEM, OOCSS, ITCSS, RSCSS, Atomic Design, Oxygen

Slide 31

Slide 31 text

Folder Structure /assets /images /content /layout /fonts /javascript /libs /modules module-name.js /testing module-name.spec /sass /base /helpers /modules module-name.scss /setup /themes /theme-name module-name.scss

Slide 32

Slide 32 text

Pattern Structure .parent {…} .parent-child {…} .parent-child-grandchild {…} 1. Parent-Child-Grandchild

Slide 33

Slide 33 text

Pattern Structure .navigation {…} .navigation-item {…} .navigation-item-action {…} 1. Parent-Child-Grandchild

Slide 34

Slide 34 text

Pattern Structure .plural-items {…} .singular-item {…} 1. Parent-Child-Grandchild 2. Plural-Singular

Slide 35

Slide 35 text

Pattern Structure .images {…} .image {…} 1. Parent-Child-Grandchild 2. Plural-Singular

Slide 36

Slide 36 text

Pattern Anatomy Focus on implementing modules as a “single source of truth” to be used across multiple application, without relying on copy/paste.

Slide 37

Slide 37 text

.css Function & Unit Tests .html .js .coffee .sass .slim 1. Responsive 2. Accessible 3. Versioned 4. Managed Dependencies Module

Slide 38

Slide 38 text

.css Function & Unit Tests .html .js .coffee .sass .slim Pattern Library

Slide 39

Slide 39 text

.css Function & Unit Tests .html .js .coffee .sass .slim Pattern Library Application

Slide 40

Slide 40 text

.css Function & Unit Tests .html .js .coffee .sass .slim Pattern Library Applications

Slide 41

Slide 41 text

Design System 1. Elements (base elements, like Normalize)

Slide 42

Slide 42 text

Creating Pages 1. Elements (base elements, like Normalize) 2. Modules (combination of elements)

Slide 43

Slide 43 text

Creating Pages 1. Elements (base elements, like Normalize) 2. Modules (combination of elements) 3. Theme (look and feel specific to an application)

Slide 44

Slide 44 text

Creating Pages 1. Elements (base elements, like Normalize) 2. Modules (combination of elements) 3. Theme (look and feel specific to an application) 4. Layout (combination of elements, modules, theme)

Slide 45

Slide 45 text

Creating Pages 1. Elements (base elements, like Normalize) 2. Modules (combination of elements) 3. Theme (look and feel specific to an application) 4. Layout (combination of elements, modules, theme) 5. Page (generated output served to the client)

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

API: Source of Truth

Slide 48

Slide 48 text

PATTERN API PATTERN LIBRARY APP DATA

Slide 49

Slide 49 text

Conclusion

Slide 50

Slide 50 text

Fin.