diff --git a/1-js/01-getting-started/1-intro/article.md b/1-js/01-getting-started/1-intro/article.md
new file mode 100644
index 00000000..07cbc18a
--- /dev/null
+++ b/1-js/01-getting-started/1-intro/article.md
@@ -0,0 +1,121 @@
+# An introduction to JavaScript
+
+Let's see what's so special about JavaScript, what we can achieve with it and which other technologies play well with it.
+
+## What is JavaScript?
+
+*JavaScript* was initially created to *"make webpages alive"*.
+
+The programs in this language are called *scripts*. They can be written right in the HTML and execute automatically as the page loads.
+
+Scripts are provided and executed as a plain text. They don't need a special preparation or a compilation to run.
+
+In this aspect, JavaScript is very different from another language called [Java](http://en.wikipedia.org/wiki/Java).
+
+```smart header="Why JavaScript?"
+When JavaScript was created, it initially had another name: "LiveScript". But Java language was very popular at that time, so it was decided that positioning a new language as a "younger brother" of Java would help.
+
+But as it evolved, JavaScript became a fully independent language, with its own specification called [ECMAScript](http://en.wikipedia.org/wiki/ECMAScript), and now it has no relation to Java at all.
+```
+
+At present, JavaScript can execute not only in the browser, but also on the server, or actually on any device where exists a special program called [the JavaScript engine](https://en.wikipedia.org/wiki/JavaScript_engine).
+
+The browser has an embedded engine, sometimes it's also called a "JavaScript virtual machine".
+
+Different engines have different "codenames", for example:
+
+- [V8](https://en.wikipedia.org/wiki/V8_(JavaScript_engine)) -- in Chrome and Opera.
+- [Gecko](https://en.wikipedia.org/wiki/Gecko_(software)) -- in Firefox.
+- ...There are other codenames like "Trident", "Chakra" for different versions of IE, "ChakraCore" for Microsoft Edge, "Nitro" and "SquirrelFish" for Safari etc.
+
+These terms above are good to remember, because they are used in developer articles in the internet. We'll use them too. For instance, if "a feature X is supported by V8", then it probably works in Chrome and Opera.
+
+```smart header="How the engines work?"
+
+Engines are complicated. But the basics are easy.
+
+1. The script is written and distributed as a plain text (can be compressed/optimized by so-called "javascript minifiers").
+2. The engine (embedded if it's a browser) reads the script ("parses") and converts ("compiles") it to the machine language.
+3. And then it runs, pretty fast.
+
+The engine applies optimizations on every stage of the process. It even watches the script as it runs, analyzes the data which flows through it and applies optimizations to the machine-code basing on that knowledge.
+```
+
+## What can in-browser JavaScript do?
+
+The modern JavaScript is a "safe" programming language. It does not provide low-level access to memory or CPU, because it was initially created for browsers which do not require it.
+
+The capabilities greatly depend on the environment which runs JavaScript. For instance, [Node.JS](https://wikipedia.org/wiki/Node.js) supports functions that allows JavaScript to read/write arbitrary files, perform network requests etc.
+
+In-browser JavaScript can do everything related to webpage manipulation, interaction with the user and the webserver.
+
+For instance, in-browser JavaScript is able to:
+
+- Add new HTML to the page, change the existing content, modify styles.
+- React on user actions, run on mouse clicks, pointer movements, key presses.
+- Send requests over the network to remote servers, download and upload files (so-called [AJAX](https://en.wikipedia.org/wiki/Ajax_(programming)) and [COMET](https://en.wikipedia.org/wiki/Comet_(programming)) technologies).
+- Get and set cookies, ask questions to the visitor, show messages.
+- Remember the data on the browser side ("local storage").
+
+## What can in-browser JavaScript NOT do?
+
+JavaScript abilities in the browser are limited for the sake of the user's safety. The aim is to prevent an evil webpage from accessing private information or harming the user's data.
+
+The examples of such restrictions are:
+
+- JavaScript on the webpage may not read/write arbitrary files on the hard disk, copy them or execute programs. It has no direct access to OS system functions.
+
+ Modern browsers allow it to work with files, but the access is limited and only provided if the user does certain actions, like "dropping" a file into a browser window or selecting it via an `` tag.
+
+ There are ways to interact with camera/microphone and other devices, but they require an explicit user's permission. So a JavaScript-enabled page may not sneakily enable a web-camera, observe the surroundings and send the information to the [NSA](https://en.wikipedia.org/wiki/National_Security_Agency).
+- Different tabs/windows generally do not know about each other. Sometimes they do, for example when one window uses JavaScript to open the other one. But even in this case, JavaScript from one page may not access the other if they come from different sites (from a different domain, protocol or port).
+
+ That is called a "Same Origin Policy". To workaround that, *both pages* must contain a special JavaScript code that handles data exchange.
+
+ The limitation is again for user's safety. A page from `http://anysite.com` which a user has opened occasionaly must not be able to open or access another browser tab with the URL `http://gmail.com` and steal information from there.
+- JavaScript can easily communicate over the net to the server where the current page came from. But its ability to receive data from other sites/domains is crippled. Though possible, it requires the explicit agreement (expressed in HTTP headers) from the remote side. Once again, that's safety limitations.
+
+
+
+Such limits do not exist if JavaScript is used outside of the browser, for example on a server. Modern browsers also allow installing plugin/extensions which may get extended permissions.
+
+## What makes JavaScript unique?
+
+There are at least *three* great things about JavaScript:
+
+```compare
++ Full integration with HTML/CSS.
++ Simple things done simply.
++ Supported by all major browsers and enabled by default.
+```
+
+Combined, these 3 things only exist in JavaScript and no other browser technology.
+
+That's what makes JavaScript unique. That's why it is the most widespread way of creating browser interfaces.
+
+While planning to learn a new technology, it's beneficial to check its perspectives. So let's move on to the modern trends that include new languages and browser abilities.
+
+
+## Languages "over" JavaScript
+
+The syntax of JavaScript does not suit everyone's needs. Different people want different features.
+
+That's normal, because projects and requirements are different for everyone.
+
+So recently a plethora of new languages appeared, which are *transpiled* (converted) to JavaScript before they run in the browser.
+
+The modern tools make the transpilation very fast and transparent, actually allowing developers to code in another language, autoconverting it "under the hood".
+
+Examples of such languages:
+
+- [CoffeeScript](http://coffeescript.org/) is a "syntax sugar" for JavaScript, it introduces shorter syntax, allowing to write more precise and clear code. Usually Ruby guys like it.
+- [TypeScript](http://www.typescriptlang.org/) is concentrated on adding "strict data typing", to simplify development and support of complex systems. It is developed by Microsoft.
+- [Dart](https://www.dartlang.org/) is a standalone language that has its own engine that runs in non-browser environments (like mobile apps). It was initially offered by Google as a replacement for JavaScript, but as of now, browsers require it to be transpiled to JavaScript just like the ones above.
+
+There are more. Of course even if we use one of those languages, we should also know JavaScript, to really understand what we're doing.
+
+## Summary
+
+- JavaScript was initially created as a browser-only language, but now it is used in many other environments as well.
+- At this moment, JavaScript has a unique position as a most widely adopted browser language with full integration with HTML/CSS.
+- There are many languages that get "transpiled" to JavaScript and provide certain features. It is recommended to take a look at them, at least briefly, after mastering JavaScript.
diff --git a/1-js/01-getting-started/1-intro/limitations.png b/1-js/01-getting-started/1-intro/limitations.png
new file mode 100644
index 00000000..d5d315c5
Binary files /dev/null and b/1-js/01-getting-started/1-intro/limitations.png differ
diff --git a/1-js/01-getting-started/1-intro/limitations@2x.png b/1-js/01-getting-started/1-intro/limitations@2x.png
new file mode 100644
index 00000000..01483997
Binary files /dev/null and b/1-js/01-getting-started/1-intro/limitations@2x.png differ
diff --git a/1-js/01-getting-started/2-code-editors/article.md b/1-js/01-getting-started/2-code-editors/article.md
new file mode 100644
index 00000000..8a835e61
--- /dev/null
+++ b/1-js/01-getting-started/2-code-editors/article.md
@@ -0,0 +1,62 @@
+# Code editors
+
+A code editor is the place where a programmer spends most of his time.
+
+There are two archetypes: IDE and lightweight editors. Many people feel comfortable choosing one tool of each type.
+
+[cut]
+
+## IDE
+
+The term [IDE](https://en.wikipedia.org/wiki/Integrated_development_environment) (Integrated Development Environment) means a powerful editor with many features that usually operates on a "whole project". As said, that's not just an editor, but a full-scale "development environment".
+
+An IDE loads the project (can be many files), and then allows to navigate between files, provides autocompletion based on the whole project, integrates with version management system (like [git](https://git-scm.com/)), with testing environment and other "project-level" stuff.
+
+If you haven't considered selecting an IDE, look at the following variants:
+
+- IntelliJ editors: [WebStorm](http://www.jetbrains.com/webstorm/) for frontend development and [PHPStorm (PHP)](http://www.jetbrains.com/phpstorm/), [IDEA (Java)](http://www.jetbrains.com/idea/), [RubyMine (Ruby)](http://www.jetbrains.com/ruby/) and other if you need additional languages.
+- Visual Studio is fine if you're a .NET developer.
+- Eclipse-based products, like [Aptana](http://www.aptana.com/) and Zend Studio.
+- [Komodo IDE](http://www.activestate.com/komodo-ide) and it's lightweight free version [Komodo Edit](http://www.activestate.com/komodo-edit).
+- [Netbeans](http://netbeans.org/).
+
+All of them with the exception of Visual Studio are cross-platform. Visual Studio is now available for Mac and for Windows (https://www.visualstudio.com/vs/visual-studio-mac/)
+
+Most IDEs are paid, but have a trial period. Their cost is usually negligible compared to a qualified developer's salary, so just choose the best one for you.
+
+## Lightweight editors
+
+"Lightweight editors" are not as powerful as IDEs, but they're fast, elegant and simple.
+
+They are mainly used to instantly open and edit a file.
+
+The main difference between a "lightweight editor" and an "IDE" is that IDE works on a project-level, so it loads much more data on start, analyzes the project structure if needed and so on. A lightweight editor is much faster if we need only one file.
+
+In practice, lightweight editors may have a lot of plugins including directory-level syntax analyzers and autocompleters, so there's no strict border between a lightweight editor and an IDE.
+
+The following options deserve your attention:
+
+- [Visual Studio Code](https://code.visualstudio.com/) (cross-platform, free).
+- [Atom](https://atom.io/) (cross-platform, free).
+- [Sublime Text](http://www.sublimetext.com) (cross-platform, shareware).
+- [Notepad++](https://notepad-plus-plus.org/) (Windows, free).
+- Vim, Emacs are cool, if you know how to use them.
+
+## My favorites
+
+The personal preference of the author is to have both an IDE for projects and a lightweight editor for quick and easy file editing.
+
+I'm using:
+
+- [WebStorm](http://www.jetbrains.com/webstorm/) for JS, and if there is one more language in the project, then I switch to other Jetbrains editors like [PHPStorm](http://www.jetbrains.com/phpstorm/) (PHP), [IDEA](http://www.jetbrains.com/idea/) (Java), [RubyMine](http://www.jetbrains.com/ruby/) (Ruby). There are editors for other languages too, but I didn't use them.
+- As a lightweight editor -- [Sublime Text](http://www.sublimetext.com) or [Atom](https://atom.io/).
+
+If you don't know what to choose -- you can consider these ones.
+
+## Let's not argue
+
+The editors in the lists above are those that me or my friends -- good developers are using for a long time and are happy with.
+
+There are other great editors in our big world, please choose the one you like the most.
+
+The choice of an editor, like any other tool, is individual and depends on your projects, habits, personal preferences.
diff --git a/1-js/01-getting-started/3-devtools/article.md b/1-js/01-getting-started/3-devtools/article.md
new file mode 100644
index 00000000..544b6175
--- /dev/null
+++ b/1-js/01-getting-started/3-devtools/article.md
@@ -0,0 +1,60 @@
+# Developer console
+
+A code is prone to errors. You are quite likely to have errors... Oh, what am I talking about? You are *absolutely* going to make errors, at least if you're a human, not a [robot](https://en.wikipedia.org/wiki/Bender_(Futurama)).
+
+But in the browser, a user doesn't see the errors by default. So, if something goes wrong in the script, we won't see what's broken and can't fix it.
+
+To see errors and get a lot of other useful information about scripts, browsers have embedded "developer tools".
+
+Most often developers lean towards Chrome or Firefox for the development, because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catching-up" to Chrome or Firefox. So most people have a "favorite" browser and switch to others if a problem is browser-specific.
+
+Developer tools are really powerful, there are many features. To start, we'll learn how to open them, look at errors and run JavaScript commands.
+
+[cut]
+
+## Google Chrome
+
+Open the page [bug.html](bug.html).
+
+There's an error in the JavaScript code on it. It's hidden from a regular visitor's eyes, so let's open developer tools to see it.
+
+Press the key `key:F12` or, if you're on Mac, then `key:Cmd+Opt+J`.
+
+The developer tools will open on the Console tab by default.
+
+It looks somewhat like this:
+
+
+
+The exact look of developer tools depends on your version of Chrome. It changes from time to time, but should be similar.
+
+- Here we can see the red-colored error message. In this case the script contains an unknown "lalala" command.
+- On the right, there is a clickable link to the source `bug.html:12` with the line number where the error has occured.
+
+Below the error message there is a blue `>` symbol. It marks a "command line" where we can type JavaScript commands and press `key:Enter` to run them (`key:Shift+Enter` to input multiline commands).
+
+Now we can see errors and that's enough for the start. We'll be back to developer tools later and cover debugging more in-depth in the chapter .
+
+
+## Firefox, Edge and others
+
+Most other browsers use `key:F12` to open developer tools.
+
+The look & feel of them is quite similar. Once you know how to use one of them (can start with Chrome), you can easily switch to another.
+
+## Safari
+
+Safari (Mac browser, not supported for Windows/Linux) is a little bit special here. We need to enable the "Develop menu" first.
+
+Open Preferences and go to "Advanced" pane. There's a checkbox at the bottom of it:
+
+
+
+Now `key:Cmd+Opt+C` can toggle the console. Also note that the new top menu item named "Develop" has appeared. It has many commands and options.
+
+## Summary
+
+- Developer tools allow us to see errors, run commands, examine variables and much more.
+- They can be opened with `key:F12` for most browsers under Windows. Chrome for Mac needs `key:Cmd+Opt+J`, Safari: `key:Cmd+Opt+C` (need to enable first).
+
+Now we have the environment ready. In the next section we get down to JavaScript.
diff --git a/1-js/01-getting-started/3-devtools/bug.html b/1-js/01-getting-started/3-devtools/bug.html
new file mode 100644
index 00000000..edb02375
--- /dev/null
+++ b/1-js/01-getting-started/3-devtools/bug.html
@@ -0,0 +1,17 @@
+
+
+
+
+
+
+
+
+
+ There is an error in the script on this page.
+
+
+
+
+
\ No newline at end of file
diff --git a/1-js/01-getting-started/3-devtools/chrome.png b/1-js/01-getting-started/3-devtools/chrome.png
new file mode 100644
index 00000000..fd029b74
Binary files /dev/null and b/1-js/01-getting-started/3-devtools/chrome.png differ
diff --git a/1-js/01-getting-started/3-devtools/chrome@2x.png b/1-js/01-getting-started/3-devtools/chrome@2x.png
new file mode 100644
index 00000000..b87404a8
Binary files /dev/null and b/1-js/01-getting-started/3-devtools/chrome@2x.png differ
diff --git a/1-js/01-getting-started/3-devtools/safari.png b/1-js/01-getting-started/3-devtools/safari.png
new file mode 100644
index 00000000..37598a26
Binary files /dev/null and b/1-js/01-getting-started/3-devtools/safari.png differ
diff --git a/1-js/01-getting-started/3-devtools/safari@2x.png b/1-js/01-getting-started/3-devtools/safari@2x.png
new file mode 100644
index 00000000..c59cebef
Binary files /dev/null and b/1-js/01-getting-started/3-devtools/safari@2x.png differ
diff --git a/1-js/01-getting-started/index.md b/1-js/01-getting-started/index.md
new file mode 100644
index 00000000..b327c786
--- /dev/null
+++ b/1-js/01-getting-started/index.md
@@ -0,0 +1,3 @@
+# An introduction
+
+About the JavaScript language and the environment to develop with it.
diff --git a/1-js/8-oop/5-functional-inheritance/2-coffeemachine-disable-stop/solution.md b/1-js/02-first-steps/01-hello-world/1-hello-alert/solution.md
similarity index 100%
rename from 1-js/8-oop/5-functional-inheritance/2-coffeemachine-disable-stop/solution.md
rename to 1-js/02-first-steps/01-hello-world/1-hello-alert/solution.md
diff --git a/1-js/02-first-steps/01-hello-world/1-hello-alert/solution.view/index.html b/1-js/02-first-steps/01-hello-world/1-hello-alert/solution.view/index.html
new file mode 100644
index 00000000..45e6744b
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/1-hello-alert/solution.view/index.html
@@ -0,0 +1,12 @@
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/1-js/02-first-steps/01-hello-world/1-hello-alert/task.md b/1-js/02-first-steps/01-hello-world/1-hello-alert/task.md
new file mode 100644
index 00000000..afed6a91
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/1-hello-alert/task.md
@@ -0,0 +1,12 @@
+importance: 5
+
+---
+
+# Show an alert
+
+Create a page that shows a message "I'm JavaScript!".
+
+Do it in a sandbox, or on your hard drive, doesn't matter, just ensure that it works.
+
+[demo src="solution"]
+
diff --git a/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/alert.js b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/alert.js
new file mode 100644
index 00000000..4de72597
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/alert.js
@@ -0,0 +1 @@
+alert("I'm JavaScript!");
\ No newline at end of file
diff --git a/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/index.html b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/index.html
new file mode 100644
index 00000000..10895f8f
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/index.html
@@ -0,0 +1,10 @@
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/solution.md b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/solution.md
new file mode 100644
index 00000000..f42c41e6
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/solution.md
@@ -0,0 +1,8 @@
+The HTML code:
+
+[html src="index.html"]
+
+For the file `alert.js` in the same folder:
+
+[js src="alert.js"]
+
diff --git a/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/task.md b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/task.md
new file mode 100644
index 00000000..26168d6a
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/2-hello-alert-ext/task.md
@@ -0,0 +1,9 @@
+importance: 5
+
+---
+
+# Show an alert with an external script
+
+Take the solution of the previous task . Modify it by extracting the script content into an external file `alert.js`, residing in the same folder.
+
+Open the page, ensure that the alert works.
diff --git a/1-js/02-first-steps/01-hello-world/article.md b/1-js/02-first-steps/01-hello-world/article.md
new file mode 100644
index 00000000..631d8bd2
--- /dev/null
+++ b/1-js/02-first-steps/01-hello-world/article.md
@@ -0,0 +1,137 @@
+# Hello, world!
+
+The tutorial that you're reading is about core JavaScript, which is platform-independent. Further on, you will learn Node.JS and other platforms that use it.
+
+But, we need a working environment to run our scripts, and, just because this book is online, the browser is a good choice. We'll keep the amount of browser-specific commands (like `alert`) to a minimum, so that you don't spend time on them if you plan to concentrate on another environment like Node.JS. On the other hand, browser details are explained in detail in the [next part](/ui) of the tutorial.
+
+So first, let's see how to attach a script to the webpage. For server-side environments, you can just execute it with a command like `"node my.js"` for Node.JS.
+
+
+[cut]
+
+## The "script" tag
+
+JavaScript programs can be inserted in any place of HTML with the help of the `
+*/!*
+
+