forked from rcb-ferreira/try-router-first
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
executable file
·211 lines (167 loc) · 8.46 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Try Router First</title>
<meta name="description" content="A framework for easily creating beautiful presentations using HTML">
<meta name="author" content="Hakim El Hattab">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="css/reveal.min.css">
<link rel="stylesheet" href="css/theme/beige.css" id="theme">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', use the PDF print sheet -->
<script>
document.write('<link rel="stylesheet" href="css/print/' + (window.location.search.match(/print-pdf/gi) ? 'pdf' : 'paper') + '.css" type="text/css" media="print">');
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>Try Router First</h1>
<p>
<small>Created by <a href="mailto:ferreira.rcb@gmail.com" mailto>Rui Ferreira</a></small>
</p>
</section>
<section>
<h2>Contents</h2>
<ul>
<li class="fragment">What is the problem?</li>
<li class="fragment">How can I fix it?</li>
<li class="fragment">Where am I going?</li>
</ul>
</section>
<section>
<section data-markdown>
<script type="text/template">
# What is the problem?
</script>
</section>
<section data-markdown>
<script type="text/template">
### The Kitchen Sink
</script>
</section>
<section data-markdown>
<script type="text/template">
<blockquote>
Developers have every intension of following best practices, like 80/20 rules, etc. But for some reason at the end of the project "POC" the code always looks like a kitchen sink.
</blockquote>
* sad developer
</script>
</section>
<section data-markdown>
<script type="text/template">
### Complicated state management
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
# How can I fix it?
</script>
</section>
<section data-markdown>
<script type="text/template">
### Router first
</script>
</section>
<section data-markdown>
<script type="text/template">
### Home
* **Logic:** getPath(), getPathData()
* **State:** isAuth, !isAuth
* **Content:** Title, Body, SEO (description, tags, links)
</script>
</section>
<section data-markdown>
<script type="text/template">
### Parent
* Consumes route data (Config data, API end points)
* Router should dictate how content gets rendered
</script>
</section>
<section data-markdown>
<script type="text/template">
### Child
* Parent parses route data down to child
* Lazy load as needed to save on bandwith
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
# Where am I going?
</script>
</section>
<section data-markdown>
<script type="text/template">
## Interesting Concepts
* Router should dictate how each section in the view is rendered.
* State mangement can be handled through routes
* Router can be disabled without affecting the rest of project (blue, green deployment)
* Router dictates primary, secondary links (not hardcoded!!!)
* Router should be able to cater from a single page application to application with 100s of pages.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Pros
* Free up devepers to focus on the functionality instead of state management.
* Make it easier to debug issues. (only one point of failure)
* Adding new features is a breeze.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Cons
* New concept for developers, hard to think moduler.
* Have to always make sure you add new functionality to the routes when implementing new features
</script>
</section>
</section>
<section data-markdown>
<script type="text/template">
# Q & A
</script>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.min.js"></script>
<script>
// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'default', // default/cube/page/concave/zoom/linear/fade/none
// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'lib/js/classList.js', condition: function () { return !document.body.classList; } },
{ src: 'plugin/markdown/showdown.js', condition: function () { return !!document.querySelector('[data-markdown]'); } },
{ src: 'plugin/markdown/markdown.js', condition: function () { return !!document.querySelector('[data-markdown]'); } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function () { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true, condition: function () { return !!document.body.classList; } },
{ src: 'plugin/notes/notes.js', async: true, condition: function () { return !!document.body.classList; } }
// { src: 'plugin/remotes/remotes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
</body>
</html>