-
Notifications
You must be signed in to change notification settings - Fork 5
/
index.html
executable file
·735 lines (653 loc) · 27.1 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
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>The Language of Languages</title>
<meta name="description" content="WWCode talk on languages, variables, and a bunch of other words you don't know... yet.">
<meta name="author" content="Nupur Kapoor, Kaylyn Gibilterra, Emma Grasmeder, Katherine McClintic">
<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/solarized.css" id="theme">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', include the PDF print sheet -->
<script>
if( window.location.search.match( /print-pdf/gi ) ) {
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = 'css/print/pdf.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</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">
<!-- Home slide -->
<section>
<img src="img/WWC-logo.jpg" />
<h1>The Language of Languages</h1>
<h4>Languages, variables, and other words you don't know... yet.</h4>
<p>
<small><a href="http://twitter.com/womenwhocodedc">@womenwhocodedc</a></small>
</p>
</section>
<!-- slide 2 -->
<section>
<h2>What is a programming language?</h2>
<p>A programming language is a <b>human readable</b> set of commands to communicate between <b>machines</b> and humans. It usually comprises of a <b>set of instructions</b> for the machine to perform specific tasks.</p>
</section>
<section>
<!-- slide 3 -->
<section>
<h2>1st Generation Languages</h2>
<p>
<ul>
<li>machine-level language (0s and 1s)</li>
<li>no compiler (or translator) needed</li>
<li>used to program lower level functions of a system, such as drivers and interfaces with hardware</li>
<li>difficult to learn and understand errors difficult to find</li>
</ul>
</p>
<aside class="notes">
Type 's' in the presentation to bring up notes. Programmers code in <em>languages</em>. Java, Python, JS, Ruby, PHP, and Objective-C are all examples of languages. Languages are how we as humans can communicate with computers.
</aside>
</section>
<!-- slide 3.1 -->
<section>
<h2>2nd Generation Languages</h2>
<p>
<ul>
<li>Assembly languages</li>
<li>Allow for use of symbolic names</li>
<li>Can be read and written by a programmer</li>
<li>Language specific to particular machines (not portable)</li>
<li>Used in intensive processing in games, video editing, graphic manipulation/rendering</li>
</ul>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 3.2 -->
<section>
<h2>3rd Generation Languages</h2>
<p>
<ul>
<li>Word-like commands that make languages more programmer friendly</li>
<li>Known as high level languages</li>
<li>Compiler or interpreter needed</li>
<li>Programs independent from computer types (portable)</li>
<li><em>Examples:</em> Fortran, COBOL, C, C++, BASIC, Pascal, Java, Javascript, PHP, Ruby, Python, Objective C</li>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 3.3 -->
<section>
<h2>4th Generation Languages</h2>
<p>
<ul>
<li>Syntax used very close to human language</li>
<li>Designed to:</li>
<ul>
<li>reduce programming effort</li>
<li>time it takes to develop software</li>
<li>cost of software development</li>
</ul>
<li>Typically used to access databases</li>
<li><em>Examples:</em> SQL and ColdFusion</li>
</ul>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 3.4 -->
<section>
<h2>5th Generation Languages</h2>
<p>
<ul>
<li>Languages used to support artificial intelligence</li>
<li><em>Example:</em> Prolog</li>
</ul>
</p>
<aside class="notes">
</aside>
</section>
</section>
<section>
<!-- slide 4 -->
<section>
<h2>What makes up a language?</h2>
<p>
Variables <br />
Arrays <br />
Methods, Functions <br />
Loops <br />
Conditionals <br />
</p>
<p><em>Tools in every language that let humans communicate with computers.</em></p>
<aside class="notes">
Computers need cold, hard facts and simple, unnuanced instructions: languages provide you with tools to create logic for computers including ways to store data, get data once you've stored it, manipulate data, and serve it all up to a user.
</aside>
</section>
<!-- slide 4.1 -->
<section>
<h2>What makes one language different from another?</h2>
<p>
<ul>
<li>Syntax</li>
<li>Usage</li>
<li>Difficulty</li>
</ul>
</p>
<p><em>What you want to build dictates what tools you should use.</em></p>
<aside class="notes">
Every language is different and better suited for some things over others. Lots of programmers know a handful of languages and will choose the language best suited to solve the problem at hand. Languages will differ from one another based on what the code you're writing looks like (called <em>Syntax</em>), when it's best to use it, and just how difficult the language is. Some languages are very difficult but what you can accomplish with them is worth the pain of having to learn a harder language.
</aside>
</section>
</section>
<!-- Example of nested vertical slides -->
<!-- slide 5 -->
<section>
<section>
<h2>Where are HTML and CSS?</h2>
<p>
Not programming languages<br />
Markup<br />
<em>Small pieces in a very, very big puzzle</em>
</p>
<aside class="notes">
Some of you want to learn HTML and CSS. These are not programming languages, they're something known as <em>markup</em>. Markup is a way of tagging information so that you can manipulate it with a programming language. HTML and CSS are relatively straightfoward to learn but won't take you very far: you can build a simple web page with HTML and CSS but you can't build a web app people can log into. For that you need other tools (including at least one programming language) on top of HTML and CSS. But never fear, if learning HTML and CSS are your main goals, we have a language lab for you.
</aside>
</section>
</section>
<section>
<!-- slide 6 -->
<section>
<h2>Web Development: Frontend vs Backend</h2>
</section>
<!-- slide 6.1 -->
<section>
<h2>Frontend</h2>
<p>What the user interacts with</p>
<ul>
<li>HTML</li>
<li>CSS</li>
<li>JavaScript</li>
<li>Preprocessors</li>
<li>Client-Side Frameworks</li>
</ul>
</section>
<!-- slide 6.2 -->
<section>
<h2>Backend (Languages)</h2>
<p>A vocabulary and set of grammatical rules for instructing a computer to perform specific tasks. Concerned with launching websites, maintenance, version updates etc. Popular languages include:</p>
<ul>
<li>Java</li>
<li>Python</li>
<li>Ruby</li>
<li>PHP</li>
<li>JavaScript (NodeJS)</li>
</ul>
</section>
<!-- slide 6.3 -->
<section>
<h2>Backend (Databases)</h2>
<p>Where you store information. A database is a structured set of data stored in a computer/machine that is accessible in various ways.</p>
<ul>
<li>Relational</li>
<ul>
<li>MSSQL</li>
<li>MYSQL</li>
<li>PostgreSQL</li>
</ul><br />
<li>Non-Relation (NoSQL)</li>
<ul>
<li>MongoDB</li>
<li>CouchDB</li>
<li>Redis</li>
</ul>
</ul>
</section>
</section>
<section>
<!-- slide 7 -->
<section>
<h2>Frameworks</h2>
<p>
<ul>
<li>Programming frameworks work with languages to help you clean up and structure your code.</li>
<li>With frameworks you can develop better and faster!</li>
<li>They also make your code more maintainable, and easily upgradable</li>
<li>They allow programmers to save time by using generic modules in order to focus on other aspects of a web app</li>
</ul>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 7.1 -->
<section>
<h2>Types of Frameworks</h2>
<ul>
<li>There are two types of frameworks, client-side and server-side</li>
<li>Client-side = front-end languages and markup, mainly CSS and Javascript</li>
<li>Server-side = mainly used with back-end languages to bootstrap full web apps</li>
</ul>
</section>
<!-- slide 7.2 -->
<section>
<h2>Examples of Client-side Frameworks</h2>
<br />
<h3>CSS Frameworks</h3>
<p>
<ul>
<li>Bootstrap</li>
<li>Foundation</li>
<li>Pure</li>
</ul>
</p>
<h3>SASS Frameworks</h3>
<p>
<ul>
<li>Bourbon</li>
<li>Compass</li>
</ul>
</p>
</section>
<!-- slide 7.3 -->
<section>
<h2>Examples of Client-side Frameworks</h2>
<h3>Javascript Frameworks</h3>
<p>
<ul>
<li>Angular.js, Ember and React (Top 3)</li>
<li>Backbone, Knockout.js (older, popular frameworks)</li>
<li>Up and coming.lesser known frameworks include: Meteor, Can.js, Aurora and many more ...</li>
</ul>
</p>
</section>
<!-- slide 7.4 -->
<section>
<h2>Examples of Server-side Frameworks</h2>
<p>
<ul>
<li><em>Ruby</em> - Ruby on Rails</li>
<li><em>Python</em> - Django, Flask</li>
<li><em>Javascript (Node.js)</em> - Mean.io</li>
<li><em>PHP</em> - CakePHP, Symphony</li>
<li><em>Java</em> - Spring</li>
<li><em>.NET</em> - Sitecore</li>
</ul>
</p>
<aside class="notes">
The good news about coding is that lots of developers contribute to <em>open-source</em> - meaning that they freely release to the public code they've written to make it easier to build apps. These particular examples are known as <em>frameworks</em> and tons of them exist and are always language-specific. You have probably heard of <em>Ruby on Rails</em>, which helps people build web apps using Ruby. There's also <em>Angular</em>, which helps people build web apps with Javascript. Part of building an app means researching tools and deciding whether or not you think they'll help you or make your life more difficult.
</aside>
</section>
</section>
<section>
<!-- slide 8 -->
<section>
<h2>Which language should I learn?</h2>
<p><em>From <a href= "http://mashable.com/2015/01/18/programming-languages-2015/#sbP_Okqq5EqB" target="_blank">Mashable's 15 Programming languages you need to know in 2015</a></em></p>
<p>
<ol>
<li><em>Java</em></li>
<ul>
<li>enterprise software</li>
<li>web-based content</li>
<li>games and mobile apps</li>
<li>Android operating system</li>
</ul>
<li><em>JavaScript</em></li>
<ul>
<li>client and server side scripting language</li>
<li>considered essential for developing interactive or animated web functions</li>
<li>used in game development</li>
</ul>
</ol>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 8.1 -->
<section>
<h2>Which language should I learn?</h2>
<p>
<ol start="3">
<li><em>C# </em>(pronounced C sharp)</li>
<ul>
<li>general purpose language</li>
<li>used for Microsoft and Windows platforms</li>
</ul>
<li><em>PHP</em></li>
<ul>
<li>server side scripting language</li>
<li>used to make dynamic websites and app development</li>
<li>used to make Facebook, Wordpress, and more</li>
</ul>
<li><em>C++</em></li>
<ul>
<li>powers major software like Firefox, Adobe</li>
<li>used in engineering</li>
</ul>
</ol>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 8.2 -->
<section>
<h2>Which language should I learn?</h2>
<p>
<ol start="6">
<li><em>Python</em></li>
<ul>
<li>server side scripting language</li>
<li>used for websites and mobile apps</li>
<li>human-friendly syntax</li>
<li>powers Instagram, Pinterest</li>
</ul>
<li><em>C</em></li>
<ul>
<li>embedded applications</li>
<li>implementing operating systems</li>
</ul>
</ol>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 8.3 -->
<section>
<h2>Which language should I learn?</h2>
<p>
<ol start="8">
<li><em>SQL</em></li>
<ul>
<li>manages data in relational database management systems</li>
</ul>
<li><em>Ruby</em></li>
<ul>
<li>object-oriented scripting language</li>
<li>considered fairly user-friendly for beginners</li>
<li>used to make dynamic websites and app development</li>
<li>used to make Groupon, Shopify, GitHub, and more</li>
</ul>
<li><em>Objective-C/Swift</em></li>
<ul>
<li>used by Apple</li>
<li>powers OSX and iOS</li>
<li>used for iPhone apps</li>
</ul>
</ol>
</p>
<aside class="notes">
</aside>
</section>
<!-- slide 8.4 -->
<section>
<h2>Which language should I learn?</h2>
<p>
<ol start="10">
<li>Other popular langauges include:</li>
<ul>
<li>Perl</li>
<li>Visual Basic .NET</li>
<li>R</li>
</ul>
</ol>
</p>
<aside class="notes">
</aside>
</section>
</section>
<!-- slide 9 -->
<section>
<h2>What We Build With Code</h2>
<p>
<ul>
<li>iOS (iPad/iPhone apps) </li>
<li>Android apps</li>
<li>Web apps</li>
<li>Libraries</li>
<li>Frameworks</li>
<li>Games and much more ...</li>
</ul>
</p>
<aside class="notes">
Some of the things that we build include apps, website sites, web aps, libraries, and frameworks. Apps will run on your phone or on a tablet. A website or a web app can be accessed on the internet with a URL. A web app might do similar things to an app on your phone, meaning users can log in and save data. You might build a library, which would be tiny packets of code that other people find useful and can use in their own projects. You might build a framework, which can help other people build their own applications. You might build a computer program that others can download onto their computers. The sky's the limit if you have an idea and a willingness to learn.
</aside>
</section>
<section>
<!-- slide 10 -->
<section>
<h2>So What Should I Learn to Build x?</h2>
</section>
<!-- slide 10.1 -->
<section>
<h2>Web App</h2>
<p>
<ul>
<li><em>Front end</em>: HTML, CSS, Javascript, <em>Back end</em>: could be anything, Python and Ruby are popular</li>
<li><em>Editor</em>: Sublime Text</li>
<li><em>Environment</em>: Terminal, Editor, Browser</li>
</ul>
</p>
</section>
<!-- slide 10.2 -->
<section>
<h2>iOS App (iPad, iPhone)</h2>
<p>
<ul>
<li><em>Language</em>: Objective-C, SWIFT</li>
<li><em>Editor</em>: X-Code (IDE)</li>
<li><em>Additional Notes</em>: You need to have a Mac.</li>
</ul>
</p>
</section>
<!-- slide 10.3 -->
<section>
<h2>Android App</h2>
<p>
<ul>
<li><em>Language</em>: Java with the Android SDK </li>
<li><em>Editor</em>: Eclipse (IDE) or Android Studio (IDE)</li>
</ul>
</p>
</section>
<!-- slide 10.4 -->
<section>
<img src="img/what-should-i-learn-first.png" width="200%" height="200%" alt="What should I learn first">
</section>
</section>
<!-- slide 11 -->
<section>
<h2>Tools We Use for Coding</h2>
<p>
<ul>
<li>Text editor</li>
<li>IDE (Integrated Development Environment)</li>
<li>Environment (your operating system)</li>
</ul>
</p>
</section>
<!-- slide 12 -->
<section>
<h2>Moving forward...</h2>
<img src="img/now_what_finding_nemo.gif" />
</section>
<!-- slide 13 -->
<section>
<h2>How We Suggest You Get Started</h2>
<ul>
<li>Pick your language of choice.</li>
<ul><li>Or explore your options with free (or partially free) sites like Codecademy, Coursera, and Lynda</li></ul>
<li>Attend and learn at your own pace with our language labs and other groups.</li>
<li>Start learning a framework that's in the language you're studying.</li>
<li>Deploy a mobile, desktop, or web app!</li>
</ul>
</section>
<section>
<!-- slide 14 -->
<section>
<h2>But I want to learn something else! How do I get started with x?</h2>
</section>
<!-- slide 14.1 -->
<section>
<h2>The community is your friend</h2>
<ul>
<li>Ask questions in Women Who Code DC's Slack</li>
<ul>
<li>Sign up <a href="http://bit.ly/wwcdcslack" target="_blank">via a Google Form</a></li>
<li>Channels like: #front-end, #git, #_jobs, #social-events and more</li>
</ul>
<li>We have lots of resources on <a href="https://github.com/womenwhocodedc" target="_blank">GitHub</a></li>
<li>Come to our events and other local meetup groups</li>
<li>Google first, last, and always</li>
<li><em>All developers learn autonomously</em></li>
</ul>
<aside class="notes">
Slack, a kind of private message app, is our way of communicating on a daily basis. We have all sorts of channels for technical and non-technical topics that you might be interested in. <br>
I've heard some managers say that their best engineers are the first to Google. What they mean by that is that it's good practice to try and work out a problem on your own (including googling for a solution), before asking for help, and to understand at what point it's no longer useful to bang your head against the wall. You'll discover what works for you as you learn.<br>
You may be working your way through a tutorial, absolutely stumped or bored despite a good effort, thinking you're stupid because you can't get thorough it. Whether they're resources that we've suggested or ones that you have found on your own, not all resources work well for all people. You may have hated that one Ruby tutorial but find you actually like the language for example. It's also okay to decide that a particular language is not for you and try something else.
</aside>
</section>
</section>
<section>
<!-- slide 15 -->
<section>
<h2>What you should expect</h2>
<ul>
<li>It will be hard.</li>
<li>You will get errors.</li>
<li>You will get frustrated and angry with your computer.</li>
</ul>
</section>
<!-- slide 15.1 -->
<section>
<h2>But...don't lose hope!</h2>
<img src="img/computer-throw.gif" width="200%" height="200%" alt="Fuck computers">
</section>
<!-- slide 15.2 -->
<section>
<ul>
<li>It will be rewarding.</li>
<li>You will get better.</li>
<li>You will create amazing things if you stick to practicing.</li>
</ul>
</section>
</section>
<!-- slide 16 -->
<section>
<section>
<h2>Women Who Code Leadership Team</h2>
<h3>Language Leads</h3>
<h4>Front End (HTML/CSS, Javascript)</h4>
<ul>
<li>Isa Conteh</li>
<li>Nyasha Hamilton</li>
<li>Marian Lumba</li>
<li>Lindsey Kopacz</li>
</ul>
</section>
<!-- slide 16.1 -->
<section>
<h4>Android (Java)</h4>
<ul>
<li>Ijeoma Ezeonyebuchi</li>
<li>Lyndsey Newsome</li>
</ul>
</section>
<!-- slide 16.2 -->
<section>
<h4>Python</h4>
<ul>
<li>Violet Cullors</li>
<li>Niki Knight</li>
<li>Maya</li>
<li>Norma Palomino</li>
</ul>
</section>
<!-- slide 16.3 -->
<section>
<div>
<h4>Ruby</h4>
<ul>
<li>Zuri Hunter</li>
<li>Erin Upton-Cosulich</li>
<li>Nyasha Hamilton</li>
<li>Mary Katherine McKenzie</li>
</ul>
</div>
</section>
<!-- slide 16.4 -->
<section>
<h4>Algorithms</h4>
<ul>
<li>Valerie Woolard Srinivasan</li>
<li>Meggie Ladlow</li>
<li>Kajari Ghosh</li>
</ul>
</section>
<!-- slide 16.5 -->
<section>
<h4>Virginia Leads</h4>
<ul>
<li>Lisa McCray</li>
<li>Melissa Miller</li>
</ul>
</section>
<!-- slide 16.6 -->
<section>
<h4>Directors</h4>
<p>
Katherine McClintic <a href="http://twitter.com/scarletalphabet" target="_blank">@scarletalphabet</a> <br />
Pam Vong <a href="http://twitter.com/pamtaro" target="_blank">@pamtaro</a> <br />
Alex Ulsh <a href="http://twitter.com/AlexUlsh" target="_blank">@AlexUlsh</a> <br />
Lauren Jacobson <a href="http://twitter.com/Lauren_CJay" target="_blank">@Lauren_CJay</a> <br />
Su Kim <a href="http://twitter.com/sukim" target="_blank">@sukim</a>
</p>
<div>
<img src="img/thumbs-up.gif" />
<h3><a href="http://twitter.com/womenwhocodedc">@womenwhocodedc</a><br /></h3>
<h3><a href="https://www.womenwhocode.com/">womenwhocode website</a><br /></h3>
</div>
</section>
</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
// Parallax scrolling
// parallaxBackgroundImage: 'https://s3.amazonaws.com/hakim-static/reveal-js/reveal-parallax-1.jpg',
// parallaxBackgroundSize: '2100px 900px',
// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.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; } }
]
});
</script>
</body>c
</html>