#HTML5 Boot Camp

##The future of Web Apps is here! ###Are you ready for it?

####Index

1. Objective

2. Who Should Attend

3. Duration

4. Technical Assistance

5. Performance Measurement

6. Handling advanced Developers

7. Materials

8. General Guidelines

9. Proposed Test Applications

10. [Environment Setup]

11. Learning Days

    • Topic 0: HTML & CSS Basics

    • Topic 1: JavaScript Intro and jQuery

    • Topic 2: OOP and Inheritance in JavaScript

    • Topic 3: AMD + RequireJS

    • Topic 4: Template Engines

    • Topic 5: MVC + Backbone

    • Topic 6: HTML5 APIs

12. Your First Project Starts Now!

###Objective

This course teaches the basics of modern Web UI development which enables the creation of best of breed user experiences, gaming, and mobile applications.

→ index

###Who Should Attend

The training will start at a low level and does not require in depth knowledge of the platform in question. Desirable participant profile: trainees and outside Globant candidates. A basic knowledge on HTML, CSS, and JavaScript is desired, though.

→ index

###Duration

Five weeks total.

Three weeks for guided learning and two weeks for app development.

→ index

###Technical Assistance

You can contact other bootcamp participants or any available tutor if you need technical assistance. We will create one chat for boot camp members only, and another one for boot camp members and tutors when boot camp starts.

###Performance Measurement

1. Code review after each practice and sprint

2. Checkpoint completion after Learning stage with your assigned tutor

→ index

###Handling Advanced Developers

Developers that move faster than average can go ahead and complete as much exercises as wanted.

→ index

###Materials

1. At least, three different browsers installed on the developer machine. Example, Chrome, Firefox, and the Android browser using Android's emulator.

2. The IDE to use is SublimeText.

3. Skype Account + headset (audio calls)

4. Create your own GitHub account. Follow this guideline to setup your account.

5. Install your own NodeJS server.

• Download NodeJS
• Install http-server globally, by running npm install -g http-server
• To start the server, from a command line interface, run http-server in the directory where you will clone the startup repo
• Open your web browser and point to localhost:PORT (the http-server should have outputted the number of PORT you should use)

6. Fork this repo https://github.com/intii/startup to use as a base to host the project code.

→ index

###General Guidelines

The boot camp is organized in the following way:

1. The first three weeks will be used for intensive self learning. Each topic will have reading and practices parts. Tutors will be available to answer technical questions on a given chat room.

2. The next two weeks will be used to develop an application following a life process.

3. The project manager will coordinate learning days encouraging team communication in daily meetings.

4. The project manager will gather information regarding individual progress so we can look for alternative assistance where needed.

5. The project manager will lead the boot camp sprints as if it were a real project using SCRUM agile methodology.

6. Two boot camp chats will be created for feedback and technical assistance:

   1. Bootcamp HTML - ALL Every person participating in the bootcamp is present here (students, tutors and PMs). Here is the place to ask for technical assistance!

   2. Bootcamp HTML - Assistants Here you will reach just your boot camp fellows for asking question sharing knowledge.

7. Team play is encouraged but the work will be evaluated per person.

8. Sprint duration will be 1 week.

9. The instructions will be vague as they generally are in real life projects. You must look for support and guidance from your PM, teammates and tutors.

10. All code and documentation must be in English.

11. Code must adhere to Globant’s UI HTML, CSS and JavaScript coding guidelines.

→ index

###Proposed Test Applications

The test application will consist in a Last.fm client.

###Learning Days###

Each day you will grab the fundamentals of the key building blocks for the next generation mobile apps; yeah, web apps! Web apps powered by the latest, and coolest toolkits, and techniques.

On each learning day you will have to:

1. ####Read:#### We will provide you with documentation related with current sprint content so you can have a background reference, guide and examples to complete the following practice.

2. ####Practice:#### You will implement the previously gathered knowledge in simple coding activities. Most important task numbers are listed in the "Key Points" section for each day and they should get most of your attention; if you feel you don’t have enough time to complete all tasks, start with these ones when possible.

3. ####Commit:#### You will commit all your code on a daily basis, when you finish your practice.

Introduction

At high level you could see the keys as:

HTML describes the content semantics and structure of a web page. It was designed as a markup language, if you know XML, you could consider HTML as a subset of XML with a predefined semantic.

On the other hand, CSS allows to define the look and feel of the content. It's used to set colors on HTML elements, customize sizes, define the layout of the document content, among others. (e.x. "The following list of elements must be shown as a menu", "The main title of the page should use this particular font").

JavaScript is a programming language that runs in all Web Browsers. It allows to add dynamism to a web page, by supplying a way to have more control over user interaction, and allowing altering the document content that is displayed.

Now that you know which are the three pilars of a web application's UI, it's time to dive into them in more depth.

####Topic 0: HTML & CSS Basics (5 days)

####Topic 1: JavaScript Intro and jQuery (1 day)####

#####Reading:#####

1. Beginners: Eloquent JavaScript basic tutorial (in case you need it!)

2. Beginners: Have fun with Codecademy (more experienced devs might find it fun!).

3. Recommended: jQuery Fundamentals

4. Explore jQuery documentation

5. JavaScript Prototypes: http://www.slideshare.net/Dmitry.Baranovskiy/demystifying-prototypes-6183470

#####Extra documentation:#####

• Web Platform Documentation Project: http://www.webplatform.org/

• MDN JavaScript Reference: https://developer.mozilla.org/en/JavaScript/Reference

• Annotated ECMAScript 5.1: http://es5.github.com/

#####Practice:#####

1. Create a basic index.html file. Use correct doctype, and tags. Add jQuery's latest version.

2. Add a stylesheet to the index.html. Use the stylesheet to center the text to all

   elements of the page.

3. Add a hidden

   with the following text inside: "Hello world".

4. Add a button below the

   to your index.html.

5. When the page has finished loading the section must fade in.

6. Add a textbox with the class "alias", and put the cursor inside it right after the

   fades in.

7. Attach an event to the created button which calls a function that gets a response from http://bootcamp.aws.af.cm/welcome/tunombre

8. Write the response to the

   element.

9. Show

   content in red when a server error occurs.

10. Take some free air and then create a function to highlight your name in the server response content. Call it right after setting the response inside the div.

11. AJAX: get the response from http://tweetproxy.ap01.aws.af.cm/search with parameter data "q=html5" First log the service response in Chrome's console to analyze data, then display tweets inside another section in the right side of the screen. The

    element must be used to contain the Tweets. For each tweet show: from_user, text, created_at, profile_image_url.

12. Add a transparent background covering the whole screen behind the tweets

    so the background gets dimmed.

13. Validate your page using W3C validator: https://addons.mozilla.org/en-US/firefox/addon/web-developer/

#####Key Points:#####

1, 5, 7, 10, 13

#####Mobile Test:#####

Test your code in a mobile device or in Android emulator.

#####Commit:#####

Commit your practice code.

→ index

####Topic 2: Design Patterns and OOP in JavaScript (3 days)####

#####Reading:#####

1. Understand JavaScript Prototypes: http://javascriptweblog.wordpress.com/2010/06/07/understanding-javascript-prototypes/

2. Understand JavaScript OO: http://javascriptissexy.com/oop-in-javascript-what-you-need-to-know/

3. Read this article about JavaScript design patterns by Addy Osmani

#####Extra documentation:#####

• JavaScript Patterns Collection

• A fresh look at JavaScript Mixins

#####Practice:#####

1. Create a Movie object:

Movie

-attributes : hashmap

+ play() + stop() + set(attr:string, value) + get(attr:string)

2. Instantiate some of your favourite movies and play with them in the console.

3. Add a MovieObserver class that listens for "playing" and “stopped” events.

4. Publish "playing" event on Movie.play(). You should be able to do something like this in the console:

   var terminator = new Movie();
   terminator.set('title', 'Terminator');
   // ...
   terminator.play(); // output: Playing Terminator...

5. Publish "stopped" event on Movie.stop().

6. Log to console when each event is fired.

7. Refactor Movie class as a Module keeping your previous code for reference.

8. Create a DownloadableMovie that extends from Movie adding a download method.

9. Create a mixin object called Social with the methods: share(friendName) and like().

10. Apply the mixin to Movie object and play with the console output. You should be able to do something like this in the console:

    var ironman2 = new Movie();
    ironman2.set('title', 'Iron Man 2');
    // ...
    ironman2.share('V. Rivas'); // output: Sharing Iron Man 2 with V. Rivas

11. Create an Actor class and create some actors from one of your favorite movies.

12. Show how you would add an array of actors to a Movie object.

#####Key Points:#####

3, 4, 8, 10

#####Commit:#####

Commit your practice code.

→ index

####Topic 3: AMD + RequireJS (1 day)####

#####Reading:#####

1. Read about AMD paradigm

2. Read about module pattern limitations

3. Read RequireJS documentation and samples

Extra documentation:

• AMD: The Definitive Source

• Writing Modular JavaScript

#####Practice:#####

1. Create a new index.html file as you did it the first day.

2. Add RequireJS .

3. Create the same Movie class as in the previous practice, but inside a module; the module will be an external file.

4. Create a Director class inside a module and set it as a dependency on the Movie module.

5. Add name:string, a quotes:array properties, and a speak()methods to Director; calling speak() will return director’s quotes.

6. Add a Director to a Movie You should be able to do something like this in the console: var alien = new Movie(); ... var ridleyScott = new Director(‘Ridley Scott’); //sets name in constructor ridleyScott.set('quotes', ['Cast is everything.', 'Do what ...']); alien.set('director', ridleyScott); alien.get('director').speak(); //output: Ridley Scott says: 'Cast is...'

7. Add jQuery as a module (hint: use the shim support).

8. Using jQuery show Director quotes.

#####Key Points:#####

2, 3

#####Commit:#####

Commit your practice code.

→ index

####Topic 4: Template Engines (1 day)####

#####Reading:#####

1. Know Handlebars.

2. Know Underscore template parsing capabilities.

3. Know {dust}.

#####Extra documentation:#####

• Client-side template engine comparison: http://engineering.linkedin.com/frontend/client-side-templating-throwdown-mustache-handlebars-dustjs-and-more

#####Practice:#####

1. Create a new index.html file and link the three template engines. The three files must be linked from a libs directory.

2. Write a template for a professional profile (linkedIn alike but simpler).

3. Create a JSON file with your professional profile data.

4. When document finishes loading parse the template with your data.

5. If you didn’t add work experience to the JSON file do it now using an array.

6. Adjust your template and parse it using template engine facilities for iteration.

7. Repeat with the next template engine from the reading list.

#####Key Points:#####

4, 6

#####Mobile Test:#####

Test your code in a mobile device or in Android emulator.

If it does not look good fix it with minimal changes.

#####Commit:#####

Commit your practice code.

→ index

####Topic 5: MVC & Mixins (3 days)####

#####Reading:#####

1. Read about the MVC design pattern

2. MVC Architecture for JavaScript Applications

3. Learn the basics of Backbone.js; https://github.com/addyosmani/backbone-fundamentals

#####Practice:#####

1. Using Backbone, create a movie listing with your favorite movies. Data shall be persisted in localhost.

2. Show movie details in a separate details view.

3. Allow to add / edit / remove movies from the list.

#####Key Points:#####

1, 2, 3

#####Commit:#####

Commit your practice code.

→ index

####Topic 6: HTML5 APIs (1 day)####

#####Reading:#####

1. Take a glimpse into HTML5 APIs: http://www.html5rocks.com/en/

   1. Storage APIs: http://www.html5rocks.com/en/features/storage

   2. Graphic APIs: http://www.html5rocks.com/en/features/graphics

   3. Connectivity APIs: http://www.html5rocks.com/en/features/connectivity

   4. Drag & Drop API: http://html5doctor.com/native-drag-and-drop/

   5. File APIs: http://www.html5rocks.com/en/features/file_access

2. Now, take a deep dive into HTML5: http://diveintohtml5.info/ (optional)

3. Use http://playground.html5rocks.com/ to play a little bit with them.

#####Practice:#####

1. Create a page with a textarea and a save button. Save textarea content's when the user clicks on save. Use both localStorage and IndexedDB.

2. Add a clear button to erase saved content.

3. Add drag and drop support to load text files.

4. Open a web socket and test it against this echo service.

5. Create a web page with a canvas element. Upon page load draw basic geometric figures with random colors and strokes.

6. Using the Canvas API animate a rectangle's position on the screen. Make sure not to use setTimeout but requestTimeFrame to perform the animation.

7. Create a web page with a SVG element to show a vector graphic. Make sure you understand when is better to use SVG instead of bitmaps, and viceversa.

#####Key Points:#####

1, 3, 6

#####Commit:#####

Commit your practice code.

→ index

###Your First Project Starts Now!###

####It’s time for the real thing.####

You will work on a project to achieve a fully working multi platform mobile app developed in JavaScript and using the latest tags and APIs available in HTML5.

You will apply all the knowledge obtained during the learning weeks.

You’ll be given with a backlog of user stories you will estimate with your PM.

Once estimated, user stories will be divided into sprints of one week.

You will participate on daily scrum meetings. Will you be able to consult documentation? Of course! You will be able to use any resource you know that helps you complete your user stories, be it going back to documentation sites, tutorials or just googling what you need. Luckily the web is plenty of awesome resources waiting for you to grasp them!

####Commits####

You will commit your code to GitHub on a daily basis.

####Reviews####

Tutors will give you feedback at the end of each sprint by reviewing and commenting your committed code in GitHub. If possible tutors will give you even more frequent feedback, sometimes at the end of the day.

→ index

Thanks for reading!