bump pxt

removed jquery
more fixes
2020-02-04 17:10:12 -08:00 · 2020-02-04 17:02:40 -08:00 · 2020-02-04 16:58:12 -08:00 · 2020-02-04 15:06:57 -08:00 · 2020-02-04 15:01:21 -08:00 · 2020-02-04 11:27:28 -08:00
1566 changed files with 54185 additions and 34019 deletions
--- a/.clang-format
+++ b/.clang-format
@ -0,0 +1,6 @@
+BasedOnStyle: LLVM
+IndentWidth: 4
+UseTab: Never
+ColumnLimit: 100
+AllowShortFunctionsOnASingleLine: Inline
+SortIncludes: false
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@ -0,0 +1,35 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+Add screenshots to help explain your problem. You can copy paste the screenshot in the github report. The .gif screen recording is very useful as well. 
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
--- a/.github/lock.yml
+++ b/.github/lock.yml
@ -0,0 +1,75 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads
+
+
+
+# Number of days of inactivity before a closed issue or pull request is locked
+
+daysUntilLock: 365
+
+
+
+# Skip issues and pull requests created before a given timestamp. Timestamp must
+
+# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
+
+skipCreatedBefore: false
+
+
+
+# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
+
+exemptLabels: []
+
+
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+
+lockLabel: false
+
+
+
+# Comment to post before locking. Set to `false` to disable
+
+lockComment: >
+
+  This thread has been automatically locked since there has not been
+
+  any recent activity after it was closed. Please open a new issue for
+
+  related bugs.
+
+
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+
+setLockReason: true
+
+
+
+# Limit to only `issues` or `pulls`
+
+# only: issues
+
+
+
+# Optionally, specify configuration settings just for `issues` or `pulls`
+
+# issues:
+
+#   exemptLabels:
+
+#     - help-wanted
+
+#   lockLabel: outdated
+
+
+
+# pulls:
+
+#   daysUntilLock: 30
+
+
+
+# Repository to extend settings from
+
+# _extends: repo
--- a/.github/workflows/pxt-buildpr.yml
+++ b/.github/workflows/pxt-buildpr.yml
@ -0,0 +1,31 @@
+name: pxt-buildpr
+
+on: [pull_request]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [8.x]
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: npm install
+        run: |
+          sudo apt-get install xvfb
+          sudo npm install -g pxt
+          npm install
+      - name: pxt ci
+        run: |
+          pxt ci
+        env:
+          CHROME_BIN: chromium-browser
+          DISPLAY: :99.0
+          CI: true
--- a/.github/workflows/pxt-buildtarget.yml
+++ b/.github/workflows/pxt-buildtarget.yml
@ -0,0 +1,39 @@
+name: pxt-buildtarget
+
+on:
+  push:
+    branches: 
+      - master
+  create:
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [8.x]
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: npm install
+        run: |
+          sudo apt-get install xvfb
+          sudo npm install -g pxt
+          npm install
+      - name: pxt ci
+        run: |
+          pxt ci
+        env:
+          CROWDIN_KEY: ${{ secrets.CROWDIN_KEY }}
+          PXT_ACCESS_TOKEN: ${{ secrets.PXT_ACCESS_TOKEN }}
+          PXT_RELEASE_REPO: ${{ secrets.PXT_RELEASE_REPO }}
+          NPM_ACCESS_TOKEN: ${{ secrets.NPM_ACCESS_TOKEN }}
+          CHROME_BIN: chromium-browser
+          DISPLAY: :99.0
+          CI: true
--- a/.gitignore
+++ b/.gitignore
@ -15,8 +15,10 @@ clients/win10/app/bld
 clients/win10/*.opendb
 clients/**/bin/**
 clients/**/obj/**
-clients/electron/projects
+electron-out
 hexcache
+build
+crowdinstats.csv

 *.user
 *.sw?
@ -25,5 +27,10 @@ hexcache
 *.db
 *.suo
 *.log
+
+.DS_Store
+.idea
+*.iml
 .vscode/.BROWSE.VC.DB-shm
 .vscode/.BROWSE.VC.DB-wal
+package-lock.json
--- a/.travis.yml
+++ b/.travis.yml
@ -1,14 +1,20 @@
 language: node_js
+os: linux
+dist: trusty
 node_js:
-  - "5.7.0"
+  - "8.9.4"
+before_install:
+  - export CHROME_BIN=chromium-browser
+  - export DISPLAY=:99.0
+  - sh -e /etc/init.d/xvfb start
 script:
-  - "node node_modules/pxt-core/built/pxt.js travis"  
-  - "(cd libs/lang-test0; node ../../node_modules/pxt-core/built/pxt.js run)"
-  - "(cd libs/lang-test1; node ../../node_modules/pxt-core/built/pxt.js run)"
-  - "(cd libs/lang-test0; node ../../node_modules/pxt-core/built/pxt.js test)"
-  - "(cd libs/lang-test1; node ../../node_modules/pxt-core/built/pxt.js test)"
-  - "node node_modules/pxt-core/built/pxt.js testdir tests"
-  - "(cd libs/hello; node ../../node_modules/pxt-core/built/pxt.js testconv https://az851932.vo.msecnd.net/files/td-converter-tests-v1.json)"
+  - "node node_modules/pxt-core/built/pxt.js travis"
+# - "(cd libs/lang-test0; node ../../node_modules/pxt-core/built/pxt.js run)"
+# - "(cd libs/lang-test1; node ../../node_modules/pxt-core/built/pxt.js run)"
+# - "(cd libs/lang-test0; node ../../node_modules/pxt-core/built/pxt.js test)"
+# - "(cd libs/lang-test1; node ../../node_modules/pxt-core/built/pxt.js test)"
+# - "node node_modules/pxt-core/built/pxt.js testdir tests"
+#  - "(cd libs/hello; node ../../node_modules/pxt-core/built/pxt.js testconv http://az851932.vo.msecnd.net/files/td-converter-tests-v1.json)"
 sudo: false
 notifications:
  email:
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@ -0,0 +1,46 @@
+{
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Launch",
+            "type": "node",
+            "request": "launch",
+            "program": "${workspaceRoot}/../pxt/built/pxt.js",
+            "stopOnEntry": false,
+            "args": ["serve"],
+            "cwd": "${workspaceRoot}",
+            "preLaunchTask": null,
+            "runtimeExecutable": null,
+            "runtimeArgs": [
+                "--nolazy"
+            ],
+            "env": {
+                "NODE_ENV": "development"
+            },
+            "console": "internalConsole",
+            "sourceMaps": false,
+            "outDir": null
+        },
+        {
+            "name": "Attach",
+            "type": "node",
+            "request": "attach",
+            "port": 5858,
+            "address": "localhost",
+            "restart": false,
+            "sourceMaps": false,
+            "outDir": null,
+            "localRoot": "${workspaceRoot}",
+            "remoteRoot": null
+        },
+        {
+            "name": "Attach to Process",
+            "type": "node",
+            "request": "attach",
+            "processId": "${command.PickProcess}",
+            "port": 5858,
+            "sourceMaps": false,
+            "outDir": null
+        }
+    ]
+}
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@ -1,6 +1,6 @@
 // Place your settings in this file to overwrite default and user settings.
 {
-    "file.autoSave": "afterDelay",   
+    "files.autoSave": "afterDelay",
    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/built/**": true,
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@ -0,0 +1,26 @@
+# Contributing Code
+
+PXT accepts bug fix pull requests. For a bug fix PR to be accepted, it must first have a tracking issue that has been marked approved. Your PR should link to the bug you are fixing. If you've submitted a PR for a bug, please post a comment in the bug to avoid duplication of effort.
+
+PXT also accepts new feature pull requests. For a feature-level PR to be accepted, it first needs to have design discussion. Design discussion can take one of two forms a) a feature request in the issue tracker that has been marked as approved or b) the PR must be accompanied by a full design spec and this spec is later approved in the open design discussion. Features are evaluated against their complexity, impact on other features, roadmap alignment, and maintainability.
+
+These two blogs posts on contributing code to open source projects are a good reference: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik.
+
+## Security
+
+If you believe you have found a security issue in PXT, please share it with us privately following the guidance at the Microsoft [Security TechCenter](https://technet.microsoft.com/en-us/security/ff852094). Reporting it via this channel helps minimize risk to projects built with PXT.
+
+## Legal
+
+You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it.
+
+You can complete the CLA by going through the steps at https://cla.microsoft.com. Once we have received the signed CLA, we'll review the request. You will only need to do this once.
+
+## Housekeeping
+
+Your pull request should:
+* Include a description of what your change intends to do
+* Be a child commit of a reasonably recent commit in the master branch
+* Pass all unit tests
+* Have a clear commit message
+* Include adequate tests
--- a/LICENSE.txt
+++ b/LICENSE.txt
@ -0,0 +1,25 @@
+PXT - Programming Experience Toolkit
+
+The MIT License (MIT)
+
+Copyright (c) Microsoft Corporation
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
--- a/README.md
+++ b/README.md
@ -1,11 +1,15 @@
-# micro:bit target for PXT
+# Calliope target for Microsoft MakeCode

-This target allow to program a [BBC micro:bit](https://www.microbit.co.uk/) using 
-PXT ([Microsoft Programming Experience Toolkit](https://github.com/Microsoft/pxt)).
+This editor is hosted at https://makecode.calliope.cc.

-* [Try it live](https://pxt.microbit.org)
+* Got a question? Try the forum at https://forum.calliope.cc/

-[![Build Status](https://travis-ci.org/Microsoft/pxt-microbit.svg?branch=master)](https://travis-ci.org/Microsoft/pxt-microbit)
+### BUILD COMMENTS
+
+- build libs/core/dal.d.ts new requires some meddling, as the `#define` parser does not parse `#ifdef` and thus
+has some conflicts with double defines constants
+
+![](http://calliope.cc/content/1-ueber-mini/mini_board.png)

 ## Local server

@ -18,8 +22,8 @@ The following commands are a 1-time setup after synching the repo on your machin
 * See requirements for [pxt](https://github.com/Microsoft/pxt)
 * [clone this repo](https://help.github.com/articles/cloning-a-repository/) to your computer and go in the project folder
 ```
-git clone https://github.com/microsoft/pxt-microbit
-cd pxt-microbit
+git clone https://github.com/microsoft/pxt-calliope
+cd pxt-calliope
 ```
 * install the PXT command line (add ``sudo`` for Mac/Linux shells).
 ```
@ -32,14 +36,15 @@ npm install

 ### Running

-Run this command to open a local web server (add ``sudo`` for Mac/Linux shells)
+Run this command to open a local web server (add ``sudo`` for Mac/Linux shells).
 ```
 pxt serve
 ```
 If the local server opens in the wrong browser, make sure to copy the URL containing the local token. 
 Otherwise, the editor will not be able to load the projects.

-If you need modify the `.cpp` files, turn on yotta compilation with the ``-yt`` flag (add ``sudo`` for Mac/Linux shells):
+If you need modify the `.cpp` files, turn on yotta compilation with the ``-yt`` flag (add ``sudo`` for Mac/Linux shells). On Windows, you must be running
+from the ``Run Yotta`` command prompt.
 ```
 pxt serve -yt
 ```
@ -61,7 +66,6 @@ The build automatically runs the following:
 * `pxt run` in `libs/lang-test*` - this will run the test in command line runner; 
  there is a number of asserts in both of these
 * `pxt testdir` in `tests` - this makes sure all the files compile and generates .hex files
-* run the TD->TS converter on a number of test scripts from `microbit.co.uk` and make sure the results compile

 To test something on the device:

--- a/THIRD-PARTY-NOTICES.txt
+++ b/THIRD-PARTY-NOTICES.txt
@ -0,0 +1,229 @@
+/*!----------------- PXT ThirdPartyNotices -------------------------------------------------------
+
+PXT uses third party material from the projects listed below.
+The original copyright notice and the license under which Microsoft
+received such third party material are set forth below. Microsoft
+reserves all other rights not expressly granted, whether by
+implication, estoppel or otherwise.
+
+In the event that we accidentally failed to list a required notice, please
+bring it to our attention. Post an issue or email us:
+
+           abchatra@microsoft.com
+
+---------------------------------------------
+Third Party Code Components
+---------------------------------------------
+
+Some code derived (as noted) from
+
+https://github.com/bbcmicrobit/micropython
+
+The MIT License (MIT)
+
+Copyright (c) 2013-2016 The MicroPython-on-micro:bit Developers, as listed
+in the accompanying AUTHORS file
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+----------------- google/blockly -------------------
+
+Sounds under sim/public/blockly/media from Google Blockly.
+
+
+Copyright 2013 Google Inc
+
+                                 Apache License
+                           Version 2.0, January 2011
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+---------------------------------------------
--- a/calliope.code-workspace
+++ b/calliope.code-workspace
@ -0,0 +1,13 @@
+{
+	"folders": [
+		{
+			"path": "../pxt"
+		},
+		{
+			"path": "../pxt-common-packages"
+		},
+		{
+			"path": "."
+		}
+	]
+}
--- a/clients/chrome/README.md
+++ b/clients/chrome/README.md
@ -1,26 +0,0 @@
-# microbit-chrome
-Prototype chrome addon that exposes the micro:bit's serial output to webpages. 
-* watch the [demo video](https://vimeo.com/146207766)
-
-# Installation
-See [developer.chrome.com](https://developer.chrome.com/extensions/getstarted#unpacked)
-for instructions on how to install the local version into your chrome browser.
-
-# Requirements
-* Chrome 48 or later.
-
-# Sample page
-The `demo.html` webpage goes along with the
-https://github.com/Microsoft/microbit-touchdevelop/blob/master/examples/tcs34725.cpp
-program. Run `http-server` from this directory, then visit
-http://localhost:8080/demo.html
-(keep in mind that pages served from `file://` cannot open ports).
-
-# Building
-
-Open a command prompt and run the following commands.
-
-````
-npm install
-typings update
-````
--- a/clients/chrome/background.js
+++ b/clients/chrome/background.js
@ -1,67 +0,0 @@
-var connections = [];
-// A list of "ports", i.e. connected clients (such as web pages). Multiple web
-// pages can connect to our service: they all receive the same data.
-var ports = [];
-function byPath(path) {
-    return connections.filter(function (x) { return x.path == path; });
-}
-function byId(id) {
-    return connections.filter(function (x) { return x.id == id; });
-}
-function onReceive(data, id) {
-    if (ports.length == 0)
-        return;
-    var view = new DataView(data);
-    var decoder = new TextDecoder("utf-8");
-    var decodedString = decoder.decode(view);
-    ports.forEach(function (port) { return port.postMessage({
-        type: "serial",
-        data: decodedString,
-        id: id
-    }); });
-}
-function findNewDevices() {
-    chrome.serial.getDevices(function (serialPorts) {
-        serialPorts.forEach(function (serialPort) {
-            if (byPath(serialPort.path).length == 0 &&
-                serialPort.displayName == "mbed Serial Port") {
-                chrome.serial.connect(serialPort.path, { bitrate: 115200 }, function (info) {
-                    // In case the [connect] operation takes more than five seconds...
-                    if (info && byPath(serialPort.path).length == 0)
-                        connections.push({
-                            id: info.connectionId,
-                            path: serialPort.path
-                        });
-                });
-            }
-        });
-    });
-}
-function main() {
-    // Register new clients in the [ports] global variable.
-    chrome.runtime.onConnectExternal.addListener(function (port) {
-        if (/^(micro:bit|touchdevelop|yelm|pxt|codemicrobit|codethemicrobit|pxt.microbit.org)$/.test(port.name)) {
-            ports.push(port);
-            port.onDisconnect.addListener(function () {
-                ports = ports.filter(function (x) { return x != port; });
-            });
-        }
-    });
-    // When receiving data for one of the connections that we're tracking, forward
-    // it to all connected clients.
-    chrome.serial.onReceive.addListener(function (info) {
-        if (byId(info.connectionId).length > 0)
-            onReceive(info.data, info.connectionId);
-    });
-    // When it looks like we've been disconnected, drop the corresponding
-    // connection object from the [connections] global variable.
-    chrome.serial.onReceiveError.addListener(function (info) {
-        if (info.error == "system_error" || info.error == "disconnected" || info.error == "device_lost")
-            connections = connections.filter(function (x) { return x.id != info.connectionId; });
-    });
-    // Probe serial connections at regular intervals. In case we find an mbed port
-    // we haven't yet connected to, connect to it.
-    setInterval(findNewDevices, 5000);
-    findNewDevices();
-}
-document.addEventListener("DOMContentLoaded", main);
--- a/clients/chrome/background.ts
+++ b/clients/chrome/background.ts
@ -1,92 +0,0 @@
-// A list of: {
-//   id: number;
-//   path: string;
-// } where [id] is the [connectionId] (internal to Chrome) and [path] is the
-// OS' name for the device (e.g. "COM4").
-interface Connection {
-  id: string;
-  path: string;
-}
-let connections: Connection[] = [];
-
-// A list of "ports", i.e. connected clients (such as web pages). Multiple web
-// pages can connect to our service: they all receive the same data.
-let ports = [];
-
-interface Message {
-  type: string;
-  data: string;
-  id: string;
-}
-
-function byPath(path: string): Connection[] {
-  return connections.filter((x) => x.path == path);
-}
-
-function byId(id: string): Connection[] {
-  return connections.filter((x) => x.id == id);
-}
-
-function onReceive(data, id: string) {
-  if (ports.length == 0) return;
-
-  let view = new DataView(data);
-  let decoder = new TextDecoder("utf-8");
-  let decodedString = decoder.decode(view);
-  ports.forEach(port => port.postMessage(<Message>{
-    type: "serial",
-    data: decodedString,
-    id: id,
-  }));
-}
-
-function findNewDevices() {
-  chrome.serial.getDevices(function (serialPorts) {
-    serialPorts.forEach(function (serialPort) {
-      if (byPath(serialPort.path).length == 0 &&
-        serialPort.displayName == "mbed Serial Port") {
-        chrome.serial.connect(serialPort.path, { bitrate: 115200 }, function (info) {
-          // In case the [connect] operation takes more than five seconds...
-          if (info && byPath(serialPort.path).length == 0)
-            connections.push({
-              id: info.connectionId,
-              path: serialPort.path
-            });
-        });
-      }
-    });
-  });
-}
-
-function main() {
-  // Register new clients in the [ports] global variable.
-  chrome.runtime.onConnectExternal.addListener(function (port) {
-    if (/^(micro:bit|touchdevelop|yelm|pxt|codemicrobit|codethemicrobit|pxt.microbit.org)$/.test(port.name)) {
-      ports.push(port);
-      port.onDisconnect.addListener(function () {
-        ports = ports.filter(function (x) { return x != port });
-      });
-    }
-  });
-
-  // When receiving data for one of the connections that we're tracking, forward
-  // it to all connected clients.
-  chrome.serial.onReceive.addListener(function (info) {
-    if (byId(info.connectionId).length > 0)
-      onReceive(info.data, info.connectionId);
-  });
-
-  // When it looks like we've been disconnected, drop the corresponding
-  // connection object from the [connections] global variable.
-  chrome.serial.onReceiveError.addListener(function (info) {
-    if (info.error == "system_error" || info.error == "disconnected" || info.error == "device_lost")
-      connections = connections.filter((x) => x.id != info.connectionId);
-  });
-
-  // Probe serial connections at regular intervals. In case we find an mbed port
-  // we haven't yet connected to, connect to it.
-  setInterval(findNewDevices, 5000);
-  findNewDevices();
-}
-
-document.addEventListener("DOMContentLoaded", main);
--- a/clients/chrome/logo128.png
+++ b/clients/chrome/logo128.png
--- a/clients/chrome/logo48.png
+++ b/clients/chrome/logo48.png
--- a/clients/chrome/manifest.json
+++ b/clients/chrome/manifest.json
@ -1,30 +0,0 @@
-{
-  "app": {
-    "background": {
-      "scripts": [ "background.js" ]
-    }
-  },
-
-  "manifest_version": 2,
-  "name": "pxt.microbit.org",
-  "version": "0.7.0",
-  "author": "Microsoft Corporation",
-  "short_name": "pxt.microbit.org",
-
-  "description": "Extension for https://pxt.microbit.org.",
-  "homepage_url": "https://pxt.microbit.org",
-  "offline_enabled": "true",
-  "icons": {
-    "48": "logo48.png",
-    "128": "logo128.png"
-  },
-
-  "permissions": [
-    "serial",
-    "usb"
-  ],
-
-  "externally_connectable": {
-    "matches": [ "*://localhost/*", "https://pxt.microbit.org/*", "https://*.microbit.org/*" ]
-  }
-}
--- a/clients/chrome/screenshot.png
+++ b/clients/chrome/screenshot.png
--- a/clients/chrome/tsconfig.json
+++ b/clients/chrome/tsconfig.json
@ -1,7 +0,0 @@
-{
-    "compiler-options": {
-        "target": "ES5",
-        "module": "amd",
-        "sourceMap": false
-    }
- }
--- a/clients/electron/.gitignore
+++ b/clients/electron/.gitignore
@ -1,2 +0,0 @@
-node_modules
-projects
--- a/clients/electron/README.md
+++ b/clients/electron/README.md
@ -1,5 +0,0 @@
-# PXT micro:bit Electron app
-
-A very basic wrapper around the web app. To install, copy the contents of this
-directory to somewhere outside the main `pxt-microbit` repository. Then run `npm
-install && npm start`.
--- a/clients/electron/index.html
+++ b/clients/electron/index.html
@ -1,15 +0,0 @@
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="UTF-8">
-    <title>code the micro:bit</title>
-  </head>
-  <body>
-    <webview id="webview" style="position:absolute; left:0; top:0; right:0; bottom:0"/>
-    <script>
-      const webview = document.getElementById("webview")
-      const url = `http://localhost:3232/${window.location.hash}`
-      webview.src = url
-    </script>
-  </body>
-</html>
--- a/clients/electron/main.js
+++ b/clients/electron/main.js
@ -1,39 +0,0 @@
-const {app, BrowserWindow, Menu} = require('electron')
-const pxt = require('pxt-core')
-const path = require('path')
-
-let win
-
-const cliPath = path.join(process.cwd(), "node_modules/pxt-microbit") 
-
-function startServerAndCreateWindow() {
-  pxt.mainCli(cliPath, ["serve", "-no-browser"])
-  createWindow()
-}
-
-function createWindow () {
-  win = new BrowserWindow({
-    width: 800,
-    height: 600,
-    title: "code the micro:bit"
-  })
-  Menu.setApplicationMenu(null)
-  win.loadURL(`file://${__dirname}/index.html#local_token=${pxt.globalConfig.localToken}`)
-  win.on('closed', () => {
-    win = null
-  })
-}
-
-app.on('ready', startServerAndCreateWindow)
-
-app.on('window-all-closed', () => {
-  if (process.platform !== 'darwin') {
-    app.quit()
-  }
-})
-
-app.on('activate', () => {
-  if (win === null) {
-    createWindow()
-  }
-})
--- a/clients/electron/package.json
+++ b/clients/electron/package.json
@ -1,14 +0,0 @@
-{
-  "name"    : "code-the-microbit",
-  "version" : "1.0.0",
-  "description": "Blocks / Javascript editor",
-  "author": "Microsoft",
-  "main"    : "main.js",
-  "scripts": {
-      "start": "node_modules/.bin/electron ."
-  },
-  "devDependencies": {
-      "electron": "*",
-      "pxt-microbit": "*"
-  }
-}
--- a/clients/macuploader/Graphics/appicon.sketch
+++ b/clients/macuploader/Graphics/appicon.sketch
--- a/clients/macuploader/Graphics/export.png
+++ b/clients/macuploader/Graphics/export.png
--- a/clients/macuploader/Graphics/menubar.sketch
+++ b/clients/macuploader/Graphics/menubar.sketch
--- a/clients/macuploader/Microbit
+++ b/clients/macuploader/Microbit
@ -124,7 +124,7 @@
 }

 - (void)launchEditor:(id)sender {
-    [[NSWorkspace sharedWorkspace] openURL:[NSURL URLWithString:@"https://pxt.microbit.org/"]];
+    [[NSWorkspace sharedWorkspace] openURL:[NSURL URLWithString:@"https://makecode.microbit.org/"]];
 }

@end
--- a/clients/macuploader/README.md
+++ b/clients/macuploader/README.md
@ -1,12 +1,12 @@
-# micro:bit uploader for OS X
+# @boardname@ uploader for OS X

 ![](Microbit Uploader/Assets.xcassets/AppIcon.appiconset/icon_256x256.png)

 This project is a clone of the [Windows
-uploader](https://pxt.microbit.org/uploader), but for OS X. Once launched,
+uploader](https://makecode.microbit.org/uploader), but for OS X. Once launched,
 the app runs in your menu bar and will automatically deploy any HEX files to
-your `micro:bit`. Like the Windows version, it is compatible with any browser
-that can run [pxt.microbit.org](http://pxt.microbit.org).
+your `@boardname@`. Like the Windows version, it is compatible with any browser
+that can run @homeurl@.

 ## Install the built version

--- a/clients/winuploader/Microbit.Uploader/MainForm.cs
+++ b/clients/winuploader/Microbit.Uploader/MainForm.cs
@ -32,7 +32,7 @@ namespace Microsoft.MicroBit
        private void openEditor()
        {
            // lanch editor
-            try { Process.Start("https://pxt.microbit.org#uploader"); } catch (Exception) { }
+            try { Process.Start("https://makecode.microbit.org#uploader"); } catch (Exception) { }
        }

        private void initializeFileWatch()
@ -236,7 +236,7 @@ namespace Microsoft.MicroBit
        {
            try
            {
-                Process.Start("https://pxt.microbit.org/uploader");
+                Process.Start("https://makecode.microbit.org/uploader");
            }
            catch (IOException) { }
        }
--- a/cmds/cmds.ts
+++ b/cmds/cmds.ts
@ -1,59 +0,0 @@
-/// <reference path="../node_modules/pxt-core/built/pxt.d.ts"/>
-
-import * as fs from "fs";
-import * as path from "path";
-import * as child_process from "child_process";
-
-let writeFileAsync: any = Promise.promisify(fs.writeFile)
-let execAsync: (cmd: string, options?: { cwd?: string }) => Promise<Buffer> = Promise.promisify(child_process.exec)
-let readDirAsync = Promise.promisify(fs.readdir)
-
-
-export function deployCoreAsync(res: ts.pxtc.CompileResult) {
-    return getBitDrivesAsync()
-        .then(drives => {
-            if (drives.length == 0) {
-                console.log("cannot find any drives to deploy to");
-                return Promise.resolve(0);
-            }
-
-            console.log(`copy ${ts.pxtc.BINARY_HEX} to ` + drives.join(", "));
-
-            let writeHexFile = (filename: string) => {
-                return writeFileAsync(filename + ts.pxtc.BINARY_HEX, res.outfiles[ts.pxtc.BINARY_HEX])
-                    .then(() => console.log("wrote hex file to " + filename));
-            };
-
-            return Promise.map(drives, d => writeHexFile(d))
-                .then(() => drives.length);
-        });
-}
-
-function getBitDrivesAsync(): Promise<string[]> {
-    if (process.platform == "win32") {
-        const rx = new RegExp("^([A-Z]:).* " + pxt.appTarget.compile.deployDrives)
-        return execAsync("wmic PATH Win32_LogicalDisk get DeviceID, VolumeName, FileSystem")
-            .then(buf => {
-                let res: string[] = []
-                buf.toString("utf8").split(/\n/).forEach(ln => {
-                    let m = rx.exec(ln)
-                    if (m) {
-                        res.push(m[1] + "/")
-                    }
-                })
-                return res
-            })
-    }
-    else if (process.platform == "darwin") {
-        const rx = new RegExp(pxt.appTarget.compile.deployDrives)
-        return readDirAsync("/Volumes")
-            .then(lst => lst.filter(s => rx.test(s)).map(s => "/Volumes/" + s + "/"))
-    } else if (process.platform == "linux") {
-        const rx = new RegExp(pxt.appTarget.compile.deployDrives)
-        const user = process.env["USER"]
-        return readDirAsync(`/media/${user}`)
-            .then(lst => lst.filter(s => rx.test(s)).map(s => `/media/${user}/${s}/`))
-    } else {
-        return Promise.resolve([])
-    }
-}
--- a/docfiles/indexhead.html
+++ b/docfiles/indexhead.html
@ -0,0 +1,29 @@
+<meta name="msvalidate.01" content="C458ADC671C51F222A0F655F66596649" />
+<meta property="og:title" content="Microsoft MakeCode" />
+<meta property="og:site_name" content="Microsoft MakeCode" />
+<meta property="og:url" content="https://www.makecode.com">
+<meta property="og:type" content="website" />
+<meta property="og:description" content="Microsoft MakeCode is a free, open-source Block and JavaScript learn-to-code editor that promotes a more inclusive approach to computing education." />
+<meta property="og:image" content="/static/logo/logo-card.png">
+<meta property="fb:app_id" content=""/>
+
+<meta name="msapplication-config" content="/static/logo/favicons/browserconfig.xml">
+<meta name="msapplication-TileImage" content="/static/logo/favicons/mstile-310x310.png">
+<meta name="msapplication-TileColor" content="#b4009e">
+<meta name="application-name" content="MakeCode">
+<link rel="shortcut icon" sizes="16x16 24x24 32x32 48x48" href="/static/logo/favicons/favicon.ico">
+<link rel="icon" type="image/png" sizes="32x32" href="/static/logo/favicons/favicon-32x32.png">
+<link rel="apple-touch-icon" sizes="180x180" href="/static/logo/favicons/apple-touch-icon.png">
+
+<meta name="twitter:card" content="summary"/>
+<meta name="twitter:title" content="Microsoft MakeCode">
+<meta name="twitter:description" content="Microsoft MakeCode is a free, open-source Block and JavaScript learn-to-code editor that promotes a more inclusive approach to computing education.">
+<meta name="twitter:site" content="@MSMakeCode">
+<meta name="twitter:creator" content="@MSMakeCode">
+<meta name="twitter:image" content="/static/logo/logo-card.png"/>
+<link rel="stylesheet" href="/doccdn/semantic.css" />
+<link rel="stylesheet" href="/docfiles/index.css" />
+
+<script src="/doccdn/jquery.js"></script>
+<script src="/static/semantic/semantic.min.js"></script>
+<script src="/docfiles/index.js"></script>
--- a/docs/about.md
+++ b/docs/about.md
@ -1,91 +0,0 @@
-![](/static/mb/device/pano.jpg)
-
-# About
-
-### @description A Blocks / Javascript code editor for the micro:bit, a pocket-size computer with 5x5 display, sensors and Bluetooth.
-
-The [BBC micro:bit](https://www.microbit.co.uk) is a [pocket-size computer](/device) with a 5x5 display of 25 LEDs, Bluetooth and sensors that can be programmed by anyone.
-The BBC micro:bit was made possible by many [partners](https://www.microbit.co.uk/partners).
-
-The micro:bit provides an easy and fun introduction to programming and making – switch on, program it to do something fun – wear it, customize it.
-Just like Arduino, the micro:bit can be connected to and interact with sensors, displays, and other devices. 
-
-* [Read the docs](/docs)
-
-## [Hardware: The Device](/device)
-
-The BBC micro:bit is packaged with sensors, radio and other goodies. Learn about the [hardware components](/device) of the micro:bit to make the most of it!
-
-## Programming: [Blocks](/blocks) or [JavaScript](/javascript)
-
-You can program the micro:bit using [Blocks](/blocks) or [JavaScript](/javascript) in your web browser via the [micro:bit APIs](/reference):
-
-```block
-input.onButtonPressed(Button.A, () => {
-    basic.showString("Hi!");
-})
-```
-```typescript
-input.onButtonPressed(Button.A, () => {
-    basic.showString("Hi!");
-})
-```
-
-The editor work in [most modern browsers](/browsers), work [offline](/offline) once loaded and do not require any installation. 
-
-## [Compile and Flash: Your Program!](/device/usb)
-
-When you have your code ready, you connect your micro:bit to a computer via a USB cable, so it appears as a mounted drive (named MICROBIT). 
-
-Compilation to ARM thumb machine code from [Blocks](/blocks) or [JavaScript](/javascript) happens in the browser. You save the ARM binary 
-program to a file, which you then copy to the micro:bit drive, which flashes the micro:bit device with the new program.
-
-## Simulator: Test Your Code
-
-You can run your code using the micro:bit simulator, all within the confines of a web browser. 
-The simulator has support for the LED screen, buttons, as well as compass, accelerometer, and digital I/O pins.
-
-```sim
-basic.forever(() => {
-  basic.showString("Hi!");
-})
-input.onButtonPressed(Button.A, () => {
-    led.stopAnimation();
-    basic.showLeds(`
-. . . . .
-. # . # .
-. . . . .
-# . . . #
-. # # # .`);
-});
-input.onButtonPressed(Button.B, () => {
-    led.stopAnimation();
-    basic.showLeds(`
-. # . # .
-# . # . #
-# . . . #
-. # . # .
-. . # . .`);
-});
-```
-
-## C++ Runtime
-
-The [C++ micro:bit runtime](http://lancaster-university.github.io/microbit-docs/), created at [Lancaster University](http://www.lancaster.ac.uk/), provides access to the hardware functions of the micro:bit, 
-as well as a set of helper functions (such as displaying a number/image/string on the LED screen). 
-
-The [micro:bit library](/reference) mirrors the functions of the C++ library. 
-When code is compiled to ARM machine code, the calls to JavaScript micro:bit functions are replaced with calls to the corresponding C++ functions.
-
-## [Command Line Tools](/cli)
-
-Looking to use pxt.microbit.org in your favorite editor? Install the [command line tools](/cli) and get rolling!
-
-## [Packages](/packages)
-
-Create, edit and distribute your own blocks and JavaScript using [packages](/packages). Packages are hosted on GitHub and may be written
-using C++, JavaScript and/or ARM thumb.
-
-## [Open Source](/open-source)
-
-The code for the micro:bit is [open source](/open-source) on GitHub. Contributors are welcome!
--- a/docs/blocks.md
+++ b/docs/blocks.md
@ -1,14 +0,0 @@
-# Blocks language
-
-### @description Langugage constructs for the Block editor.
-
-```namespaces
-for (let i = 0;i<5;++i) {}
-if (true){}
-let x = 0;
-Math.random(5);
-```
-
-## See Also
-
-[logic](/blocks/logic), [loops](/blocks/loops), [math](/blocks/math), [variables](/blocks/variables)
--- a/docs/blocks/logic.md
+++ b/docs/blocks/logic.md
@ -1,9 +0,0 @@
-# Logic
-
-```cards
-if(true) {}
-true;
-true && false;
-!true;
-1 != 0;
-```
--- a/docs/blocks/logic/boolean.md
+++ b/docs/blocks/logic/boolean.md
@ -1,102 +0,0 @@
-# Boolean
-
-true or false.
-
-A Boolean has one of two possible values: `true`; `false`.  Boolean (logical) operators (*and*, *or*, *not*) take Boolean inputs and yields a Boolean value. Comparison operators on other types ([numbers](/reference/types/number), [strings](/reference/types/string) yields a Boolean value.
-
-The following blocks represent the true and false Boolean values, which can be plugged in anywhere a Boolean value is expected:
-
-```blocks
-true;
-false;
-```
-
-The next three blocks represent the three Boolean (logic) operators:
-
-```blocks
-true && false;
-true || false;
-!true;
-```
-
-The next six blocks represent comparison operators that yield a Boolean value. Most comparisons you will do involve [numbers](/reference/types/number):
-
-```blocks
-42 == 0;
-42 != 0;
-42 < 0;
-42 > 0;
-42 <= 0;
-42 >= 0;
-```
-
-Boolean values and operators are often used with an [if](/blocks/logic/if) or [while](/blocks/loops/while) statement to determine which code will execute next. For example:
-
-### Functions that return a Boolean
-
-Some functions return a Boolean value, which you can store in a Boolean variable. For example, the following code gets the on/off state of `point (1, 2)` and stores this in the Boolean variable named `on`. Then the code clears the screen if `on` is `true`:
-
-### Boolean operators
-
-Boolean operators take Boolean inputs and evaluate to a Boolean output:
-
-### Conjunction: `A and B`
-
-`A and B` evaluates to `true` if-and-only-if both A and B are true:
-
-```blocks
-false && false == false;
-false && true == false;
-true && false == false;
-true && true == true;
-```
-
-### Disjunction: `A or B`
-
-`A or B` evaluates to `true` if-and-only-if either A is true or B is true:
-
-```blocks
-false || false == false;
-false || true == true;
-true || false == true;
-true || true == true;
-```
-
-### Negation: `not A`
-
-`not A` evaluates to the opposite (negation) of A:
-
-```blocks
-!false == true;
-!true == false;
-```
-
-### Example
-
-This example turns on LED `3 , 3`, if LEDs `1 , 1` and `2 , 2` are both on:
-
-```blocks
-if (led.point(1,1) && led.point(2,2)) {
-   led.plot(3,3)
-}
-```
-
-### Comparisons of numbers and strings
-
-When you compare two Numbers, you get a Boolean value, such as the comparison `x < 5` in the code below:
-
-```blocks
-let x = Math.random(5)
-if(x < 5) {
-   basic.showString("low");
-} else { 
-   basic.showString("high");
-} 
-```
-
-See the documentation on [Numbers](/reference/types/number) for more information on comparing two Numbers. You can also [compare strings](/reference/types/string-functions) using the `equals` function.
-
-### See also
-
-[if](/blocks/logic/if), [while](/blocks/loops/while), [number](/reference/types/number)
-
--- a/docs/blocks/logic/if.md
+++ b/docs/blocks/logic/if.md
@ -1,28 +0,0 @@
-# If
-
-### @parent blocks/language
- 
-
-Conditionally run code depending on whether a [Boolean](/blocks/logic/boolean) condition is true or false.
-
-```blocks
-if(true) {
-}
-```
-
-Click on the dark blue gear icon (see above) to add an *else* or *if* to the current block.
-
-### Example: adjusting screen brightness
-
-```blocks
-if(input.lightLevel()<100){
-    led.setBrightness(255);
-}
-```
-
-If the [light level](/reference/input/light-level) is `< 100`, this code sets the brightness to `255`:
-
-### See also
-
-[while loop](/blocks/loops/while), [for](/blocks/loops/for), [boolean](/blocks/logic/boolean)
-
--- a/docs/blocks/loops.md
+++ b/docs/blocks/loops.md
@ -1,7 +0,0 @@
-# Loops
-
-```cards
-for(let i = 0;i<5;i++) {}
-while(true) {}
-basic.forever(() => {});
-```
--- a/docs/blocks/loops/for.md
+++ b/docs/blocks/loops/for.md
@ -1,20 +0,0 @@
-# For
-
-### @parent blocks/language
- 
-Run part of the program the number of times you say.
-
-### Example: Count to 4
-
-This program will show the numbers 0, 1, 2, 3, and 4 one after another on the LED screen.
-
-```blocks
-for(let i = 0; i < 5; ++i) {
-basic.showNumber(i)
-}
-```
-
-### See also
-
-[repeat](/blocks/loops/repeat), [while](/blocks/loops/while), [if](/blocks/logic/if), [show number](/reference/basic/show-number)
-
--- a/docs/blocks/loops/repeat.md
+++ b/docs/blocks/loops/repeat.md
@ -1,12 +0,0 @@
-# Repeat
-
-Run part of the program the number of times you say.
-
-### Block Editor
-
-![](/static/mb/blocks/contents-0.png)
-
-### See also
-
-[for](/blocks/loops/for), [while](/blocks/loops/while), [if](/blocks/logic/if), [show number](/reference/basic/show-number)
-
--- a/docs/blocks/loops/while.md
+++ b/docs/blocks/loops/while.md
@ -1,29 +0,0 @@
-# While
-
-Repeat code while a [Boolean](/blocks/logic/boolean) `condition` is true.
-
-```blocks
-while(true) {
-}
-```
-
-The while loop has a *condition* that evaluates to a [Boolean](/blocks/logic/boolean) value. After the `do` keyword, add the code that you want to run while the `condition` is `true`. The while loop concludes with `end while`.
-
-The condition is tested before any code runs. Which means that if the condition is false, the code inside the loop doesn't execute.
-
-### Example: diagonal line
-
-The following example uses a while loop to make a diagonal line on the LED screen (points `0, 0`, `1, 1`, `2, 2`, `3, 3`, `4, 4`).
-
-```blocks
-let index = 4;
-while(index >= 0) {
-    led.plot(index, index);
-    index--;
-}
-```
-
-### See also
-
-[on button pressed](/reference/input/on-button-pressed), [for](/blocks/loops/for), [if](/blocks/logic/if), [forever](/reference/basic/forever)
-
--- a/docs/blocks/math.md
+++ b/docs/blocks/math.md
@ -1,36 +0,0 @@
-# Math
-
-### [Numeric](/reference/types/number) values: 0, 1, 2, ...
-
-```block
-0;
-1;
-2;
-```
-
-### Arithmetic binary operation (+, -, *, /)
-
-```block
-0+1;
-0-1;
-1*2;
-3/4;
-```
-
-### Absolute value
-
-```block
-Math.abs(-5);
-```
-
-### Minimum/maximum of two values
-
-```block
-Math.min(0, 1);
-```
-
-### Random value
-
-```block
-Math.random(5);
-```
--- a/docs/blocks/variables.md
+++ b/docs/blocks/variables.md
@ -1,21 +0,0 @@
-# Variables
-
-[Assign](/blocks/variables/assign) (set) a variable's value
-
-```blocks
-let x = 0;
-```
-
-Get a variable's value
-
-```blocks
-let x = 0;
-x;
-```
-
-[Change](/blocks/variables/change-var) a variable's value
-
-```blocks
-let x = 0;
-x+=1;
-```
--- a/docs/blocks/variables/assign.md
+++ b/docs/blocks/variables/assign.md
@ -1,36 +0,0 @@
-# Assignment Operator
-
-Use an equals sign to make a [variable](/blocks/variables/var) store the [number](/reference/types/number) 
-or [string](/reference/types/string) you say.
-
-When you use the equals sign to store something in a variable, the equals sign is called
-an *assignment operator*, and what you store is called a *value*.
-
-### Storing numbers in variables
-
-This program makes the variable `item` equal `5` and then shows it on the [LED screen](/device/screen).
-
-````blocks
-let item = 5
-basic.showNumber(item)
-````
-
-### Storing strings in variables
-
-This program makes the variable `name` equal `Joe` and then shows it on the [LED screen](/device/screen).
-
-````blocks
-let name = "Joe"
-basic.showString(name);
-````
-
-### Notes
-
-You can use the assignment operator with variables of 
-every [type](/reference/types). A *type* is which kind of thing
-a variable can store, like a number or string.
-
-### See also
-
-[variable](/blocks/variables/var), [types](/reference/types)
-
--- a/docs/blocks/variables/change-var.md
+++ b/docs/blocks/variables/change-var.md
@ -1,40 +0,0 @@
-# Change Value
-
-Set the value for local and global variables.
-
-### @parent blocks/change-value
-
-Change the value of a variable
-
-```blocks
-let x = 0
-x += 1
-```
-
-### Declare a variable
-
-Use the assignment operator to set the value of a [variable](/blocks/variables/var). Change the value of a variable from 0 to 1 using the change item block. Like this:
-
-```blocks
-let x = 0
-x += 1
-```
-
-### Example
-
-Use the assignment operator to set the value of a [variable](/blocks/variables/var). Change the value of a variable from 0 to 1 using the change item block. Then display the new value of the variable on the LED screen. Like this:
-
-```blocks
-let x = 0;
-x += 1;
-basic.showNumber(x);
-```
-
-### Notes
-
-* You can use the assignment operator with variables of each of the supported [types](/reference/types).
-
-### See also
-
-[variable](/blocks/variables/var), [types](/reference/types)
-
--- a/docs/blocks/variables/var.md
+++ b/docs/blocks/variables/var.md
@ -1,87 +0,0 @@
-# Local Variables
-
-How to define and use local variables.
-
-### @parent language
-
-A variable is a place where you can store and retrieve data. Variables have a name, a [type](/reference/types), and value:
-
-* *name* is how you'll refer to the variable
-* *type* refers to the kind of data a variable can store
-* *value* refers to what's stored in the variable
-
-### Var statement
-
-Use the Block Editor variable statement to create a variable 
-and the [assignment operator](/blocks/variables/assign) 
-to store something in the variable.
-
-For example, this code stores the number `2` in the `x` variable:
-
-```blocks
-let x = 2;
-```
-Here's how to define a variable in the Block Editor:
-
-1. Click `variables`.
-
-2. Change the default variable name if you like.
-
-3. Drag a block type on the right-side of the [assignment operator](/blocks/variables/assign) and click the down arrow to change the variable name.
-
-A variable is created for the number returned by the [brightness](/reference/led/brightness) function.
-
-```blocks
-let b = led.brightness();
-```
-
-### Using variables
-
-Once you've defined a variable, just use the variable's name whenever you need what's stored in the variable. For example, the following code shows the value stored in `counter` on the LED screen:
-
-```blocks
-let counter = 1;
-basic.showNumber(counter);
-```
-
-To change the contents of a variable use the assignment operator. The following code sets `counter` to 1 and then increments `counter` by 10:
-
-```blocks
-let counter = 1;
-counter = counter + 10;
-basic.showNumber(counter);
-```
-
-### Why use variables?
-
-If you want to remember and modify data, you'll need a variable. 
-A counter is a great example:
-
-```blocks
-let counter = 0;
-input.onButtonPressed(Button.A, () => { 
-  counter = counter + 1;
-  basic.showNumber(counter);
-});
-```
-
-### Local variables
-
-Local variables exist only within the function or block of code where they're defined. For example:
-
-```blocks
-// x does NOT exist here.
-if (led.brightness() > 128) {
-  // x exists here
-  let x = 0;
-}
-```
-
-#### Notes
-
-* You can use the default variable names if you'd like, however, it's best to use descriptive variable names. To change a variable name in the editor, select the down arrow next to the variable and then click "new variable".
-
-### See also
-
-[types](/reference/types), [assignment operator](/blocks/variables/assign)
-
--- a/docs/browsers.md
+++ b/docs/browsers.md
@ -1,103 +0,0 @@
-# Unsupported configuration
-
-Your browser is currently not supported. The following configurations are supported:
-
-## Windows
-
-You need one of these browsers running on Windows 7, Windows 8, Windows 8.1, or
-Windows 10:
-
-* Internet Explorer 11
-* Microsoft Edge
-* Google Chrome
-* Mozilla Firefox
-
-## Mac
-
-You need one of these browsers running on OS X 10.9 Mavericks, OS X 10.10
-Yosemite, OS X 10.11 El Capitan, or macOS 10.12 Sierra:
-
-* Safari
-* Google Chrome
-* Mozilla Firefox
-
-## Linux
-
-If you're using a Raspberry Pi, please see [the documentation
-here](/raspberry-pi).
-
-You need to be running a Linux distribution recent enough to run the most recent
-version of one of the following:
-
-* Google Chrome, or Chromium
-* Mozilla Firefox, Iceweasel, or Seamonkey
-
-## How to check your OS or browser
-
-### Windows
-
-* Click on the Start menu
-* Type 'System'
-* Click on the app called 'System'
-* The version of Windows you are using will be displayed:
-
-![](/static/configurations/windows-version.png)
-
-### Mac
-
-* Click on the Apple icon in the top left
-* Click on 'About this Mac'
-* This window will be displayed:
-
-![](/static/configurations/osx-version.png)
-
-### Internet Explorer
-
-* Click on the Settings icon in the top right
-* Click 'About Internet Explorer'
-* This window will be displayed:
-
-![](/static/configurations/ie-version.png)
-
-### Edge
-
-Edge automatically updates, so you should always be using the latest version
-
-* Click on the menu icon in the top right (three dots)
-* Scroll to the bottom
-* Information similar to the following will be displayed:
-
-![](/static/configurations/edge-version.png)
-
-### Google Chrome
-
-Google Chrome automatically updates, so you should always be using the latest version
-
-* Click on the menu icon in the top right (three dots)
-* Click Help, and About Google Chrome
-* Information similar to the following will be displayed:
-
-![](/static/configurations/chrome-version.png)
-
-### Firefox
-
-Firefox automatically updates, so you should always be using the latest version
-
-* Click on the menu icon in the top right (three horizontal lines)
-* Click the question mark icon (help button)
-* Click 'About Firefox'
-
-![](/static/configurations/firefox-version.png)
-
-### Safari
-
-Safari updates when your operating system updates, so if you are using the
-latest version of OS X then you'll be using the latest version of Safari.
-
-* Click on the Safari menu in the top left
-* Click 'About Safari'
-
-![](/static/configurations/safari-version.png)
-
-IT administrators should check which browser versions are supported
-[here](/browsers/technical).
--- a/docs/browsers/linux.md
+++ b/docs/browsers/linux.md
@ -1,16 +0,0 @@
-# Recommended browser for Linux
-
-As you are using Linux, it is recommended that you use [Mozilla
-Firefox][firefox] or [Google Chrome][chrome].
-
-Please see [here][technical] for technical information on which browsers are
-supported, or [here][versions] to check which version you are using.
-
-[edge]: https://www.microsoft.com/en-us/windows/microsoft-edge
-[ie]: https://www.microsoft.com/en-us/download/internet-explorer.aspx
-[firefox]: https://www.mozilla.org/en-US/firefox/new/
-[chrome]: https://www.google.com/chrome/
-[opera]: https://www.opera.com
-[safari]: http://www.apple.com/safari/
-[technical]: /browsers/technical
-[versions]: /browsers
--- a/docs/browsers/mac.md
+++ b/docs/browsers/mac.md
@ -1,16 +0,0 @@
-# Recommended browser for Mac
-
-As you are using a Mac, it is recommended that you use [Safari][]. Alternatively,
-[Google Chrome][chrome] and [Mozilla Firefox][firefox] are also supported.
-
-Please see [here][technical] for technical information on which browsers are
-supported, or [here][versions] to check which version you are using.
-
-[edge]: https://www.microsoft.com/en-us/windows/microsoft-edge
-[ie]: https://www.microsoft.com/en-us/download/internet-explorer.aspx
-[firefox]: https://www.mozilla.org/en-US/firefox/new/
-[chrome]: https://www.google.com/chrome/
-[opera]: https://www.opera.com
-[safari]: http://www.apple.com/safari/
-[technical]: /browsers/technical
-[versions]: /browsers
--- a/docs/browsers/technical.md
+++ b/docs/browsers/technical.md
@ -1,36 +0,0 @@
-# Technical information about browser support
-
-[pxt.microbit.org][] requires that you use a recent version of a modern
-browser, such as Microsoft Edge, Google Chrome, Mozilla Firefox, Safari, Opera,
-or IE11.  This is because the editor uses modern web technologies such as [web
-workers][] to enable compiling [TypeScript][] in the browser, or the using the
-same [Monaco][] editor that powers [Visual Studio Code][].
-
-[pxt.microbit.org]: https://pxt.microbit.org
-[web workers]: http://www.w3.org/TR/workers/
-[typescript]: http://www.typescriptlang.org
-[monaco]: https://microsoft.github.io/monaco-editor/
-[visual studio code]: http://code.visualstudio.com
-
-Most modern browsers automatically update themselves, but in some environments
-such as schools these automatic updates are disabled for security. **We
-strongly recommend that you use the most recent version of any of these
-browsers**, but if you can't then you must use at least:
-
-| Browser           | Minimum version | Release date   | Windows     | Mac        |
-| ----------------- | --------------- | -------------- | ----------- | ---------- |
-| Edge              | 12              | March 2015     | Windows 10+ | N/A        |
-| Internet Explorer | 11              | October 2013   | Windows 7+  | N/A        |
-| Mozilla Firefox   | 31 ESR          | July 2014      | Windows XP+ | OS X 10.6+ |
-| Google Chrome     | 38              | October 2014   | Windows XP+ | OS X 10.6+ |
-| Safari            | 9               | September 2015 | N/A         | OS X 10.9+ |
-| Opera             | 21              | May 2014       | Windows 7+  | OS X 10.9+ |
-
-
-Please see our information for which browsers are recommended for [Windows][],
-[Mac][], [Linux][], or [Raspberry Pi][].
-
-[Windows]: /browsers/windows
-[Mac]: /browsers/mac
-[Linux]: /browsers/linux
-[Raspberry Pi]: /raspberry-pi
--- a/docs/browsers/windows.md
+++ b/docs/browsers/windows.md
@ -1,18 +0,0 @@
-# Recommended browser for Windows
-
-We recommend [Microsoft Edge][edge] if you are running Windows 10, but users on
-Windows 7 or higher can use [Internet Explorer 11][ie] or recent versions of
-[Mozilla Firefox][firefox], [Google Chrome][chrome], or [Opera][opera].
-
-
-Please see [here][technical] for technical information on which browsers are
-supported, or [here][versions] to check which version you are using.
-
-[edge]: https://www.microsoft.com/en-us/windows/microsoft-edge
-[ie]: https://www.microsoft.com/en-us/download/internet-explorer.aspx
-[firefox]: https://www.mozilla.org/en-US/firefox/new/
-[chrome]: https://www.google.com/chrome/
-[opera]: https://www.opera.com
-[safari]: http://www.apple.com/safari/
-[technical]: /browsers/technical
-[versions]: /browsers
--- a/docs/calliope/examples.md
+++ b/docs/calliope/examples.md
@ -0,0 +1,17 @@
+# Projects
+
+Here are some cool tutorials to get you started with your @boardname@!
+
+## Basic
+
+```codecard
+[
+{
+  "name": "Radio Bridge",
+  "description": "Send radio messages to editor",
+  "url": "/projects/radio-bridge",
+  "imageUrl": "/static/mb/projects/radio-bridge.png",
+  "cardType": "example"
+}
+]
+```
--- a/docs/calliope/experiment/remoteCar.jpg
+++ b/docs/calliope/experiment/remoteCar.jpg
--- a/docs/calliope/experiment/remoteCar_L.jpg
+++ b/docs/calliope/experiment/remoteCar_L.jpg
--- a/docs/calliope/firststeps.md
+++ b/docs/calliope/firststeps.md
@ -0,0 +1,110 @@
+# Projects
+
+Here are some cool tutorials to get you started with your @boardname@!
+
+## Basic
+
+```codecard
+[
+  {
+  "name": "Get Ready",
+  "url":"/calliope/firststeps/firstSteps",
+  "description": "Find out how to start working with the Calliope mini",
+  "imageUrl": "/calliope/firststeps/connecting.jpg",
+  "largeImageUrl": "/calliope/firststeps/firstSteps.jpg",
+  "cardType": "tutorial",
+  "label": "Never seen a mini? Start Here!",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "The 5x5 LED matrix",
+  "url":"/calliope/firststeps/5x5LED",
+  "description": "Learn how to create and show images, numbers or letters on the LED matrix",
+  "imageUrl": "/calliope/firststeps/5x5LED.jpg",
+  "largeImageUrl": "/calliope/firststeps/5x5LED_L.jpg",
+  "cardType": "tutorial",
+  "label": "New? Start Here!",
+  "labelClass": "yellow small ribbon"
+},
+{
+  "name": "Radio",
+  "url":"/calliope/firststeps/Radio",
+  "description": "Find out how to use the radion function and how to send messages from one Calliope mini to another one",
+  "imageUrl": "/calliope/firststeps/Radio.jpg",
+  "largeImageUrl": "/calliope/firststeps/Radio_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "orange small ribbon"
+},
+{
+  "name": "Loops",
+  "url":"/calliope/firststeps/Loops",
+  "description": "Loops are important to be able to execute program instructions multiple times",
+  "imageUrl": "/calliope/firststeps/Loops.jpg",
+  "largeImageUrl": "/calliope/firststeps/Loops_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Mathematics",
+  "url":"/calliope/firststeps/Mathematics",
+  "description": "The Calliope mini can become your little math helper",
+  "imageUrl": "/calliope/firststeps/Mathematics.jpg",
+  "largeImageUrl": "/calliope/firststeps/Mathematics_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Inputs",
+  "url":"/calliope/firststeps/Inputs",
+  "description": "Use conditions for different actions",
+  "imageUrl": "/calliope/firststeps/Inputs.jpg",
+  "largeImageUrl": "/calliope/firststeps/Inputs_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Sensors",
+  "url":"/calliope/firststeps/Sensors",
+  "description": "Measure temperature, light and orientation",
+  "imageUrl": "/calliope/firststeps/Sensors.jpg",
+  "largeImageUrl": "/calliope/firststeps/Sensors_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Output",
+  "url":"/calliope/firststeps/Output",
+  "description": "Audio, light and motion",
+  "imageUrl": "/calliope/firststeps/Output.jpg",
+  "largeImageUrl": "/calliope/firststeps/Output_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Decisions",
+  "url":"/calliope/firststeps/Decisions",
+  "description": "If..., then it happens... or it happens...",
+  "imageUrl": "/calliope/firststeps/Decisions.jpg",
+  "largeImageUrl": "/calliope/firststeps/Decisions_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+},
+{
+  "name": "Variables",
+  "url":"/calliope/firststeps/Variables",
+  "description": "A variable is not a static value, it’s what you determine it to be.",
+  "imageUrl": "/calliope/firststeps/Variables.jpg",
+  "largeImageUrl": "/calliope/firststeps/Variables_L.jpg",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "green small ribbon"
+}
+]
+```
--- a/docs/calliope/firststeps/5x5LED.jpg
+++ b/docs/calliope/firststeps/5x5LED.jpg
--- a/docs/calliope/firststeps/5x5LED.md
+++ b/docs/calliope/firststeps/5x5LED.md
@ -0,0 +1,58 @@
+# ERSTE SCHRITTE: The 5X5 LED MATRIX
+
+## Introduction @unplugged
+
+Amongst other things, the Calliope mini comes with 25 red LEDs that can be turned on and off individually. If, for example, you wanted to display your name, you could program individual LEDs to light up in sequence so as to display the letters of your name one after the other. As this would be rather complex, you can also enter the character string into a text field and the Calliope Mini will light up the necessary LEDs in the correct order for you.
+
+## Step 1 @fullscreen
+
+
+### DISPLAYING A CHARACTER STRING
+To show your chosen sting of characters on the LED matrix, select the show string block from the Basic menu. Next, drag and attach this block to the Start block in the main screen. The text contained within the inverted commas will now be displayed on the Calliope mini when the program is started.
+
+```blocks
+basic.showString("hi!")
+```
+
+## Step 2 @fullscreen
+
+### DISPLAYING NUMBERS
+If you’d prefer to show a number instead of text, replace the text block in the main screen with the show number block from the Basic menu.
+
+```blocks
+basic.showNumber(0)
+```
+
+## Step 3 @fullscreen
+
+### DISPLAYING IMAGES
+To display a heart, a smiley or even a duck on your Calliope mini, Choose the show iconn block from the Basic menu and select any number of different images by simply clicking on the picture in the block.
+
+```blocks
+basic.showIcon(IconNames.Heart)
+```
+
+## Step 4 @fullscreen
+
+You can also create your very own images:
+Just select this block from the Basic menu and click in the boxes to create your very own image.
+
+```blocks
+basic.showLeds(`
+    . . . . .
+    . . . . .
+    . . . . .
+    . . . . .
+    . . . . .
+    `)
+```
+
+## Step 4 @fullscreen
+
+Wenn du keine Pause zwischen 2 Bildern festlegst, zeigt der Calliope mini das erste Bild null Sekunden lang, also gar nicht. Den Warte ms Block findest du im Menü Kontrolle.
+
+```blocks
+basic.showIcon(IconNames.Heart)
+basic.pause(100)
+basic.showIcon(IconNames.Yes)
+```
--- a/docs/calliope/firststeps/5x5LED_L.jpg
+++ b/docs/calliope/firststeps/5x5LED_L.jpg
--- a/docs/calliope/firststeps/Decisions.jpg
+++ b/docs/calliope/firststeps/Decisions.jpg
--- a/docs/calliope/firststeps/Decisions.md
+++ b/docs/calliope/firststeps/Decisions.md
@ -0,0 +1,23 @@
+# ERSTE SCHRITTE: DAS 5X5 LED RASTER
+
+## Introduction @unplugged
+
+Options within a program can be made dependent not only on inputs, but also on other conditions. For example, you can create an oracle that randomly shows a sad or a happy smiley:
+
+## Step 1 @fullscreen
+
+### If – then do relationship
+The actions below the "then“ are only executed if the condition before is fulfilled.
+In this case, the heart will not be visible on the LED grid, as the decision variable is not equal to 1. You can find the if…then block in the Logic section.
+
+## Step 2 @fullscreen
+
+### And on we go
+After the if…then block the program continues in any case, no matter whether the condition was fulfilled before or not.
+
+## Step 3 @fullscreen
+
+### If – then – else
+If you expand the if…then block, the first if condition is checked first, if it is not fulfilled the second if condition is checked. Only those actions are triggered for which the associated condition is fulfilled.
+
+Click on the + on the bottom of the block to unfold the if…then block. The probability to display either a happy or a sad smiley on the LED grid is 50/50.
--- a/docs/calliope/firststeps/Decisions_L.jpg
+++ b/docs/calliope/firststeps/Decisions_L.jpg
--- a/docs/calliope/firststeps/Inputs.jpg
+++ b/docs/calliope/firststeps/Inputs.jpg
--- a/docs/calliope/firststeps/Inputs.md
+++ b/docs/calliope/firststeps/Inputs.md
@ -0,0 +1,32 @@
+# FIRST STEPS: INPUTS
+
+## Introduction @unplugged
+
+So far all the programmed text, numbers and images have been displayed on the LED matrix immediately after being loaded onto the Calliope mini. However, if you would prefer to have an event take place after a specific input, you need to use the one of the main blocks from the Input section. In this case we are using the "on button A pressed“ block. By using this block, the Calliope mini will wait until your chosen condition is met before anything is displaying.
+
+## Step 1 @fullscreen
+
+### Buttons
+The Calliope mini has two input buttons: Button A (in red) and Button B (in blue). When one of the buttons is pressed, the circuit is completed.
+By using the "on button A pressed“ block from Input, you can display your output as soon as button A has been pressed.
+
+## Step 2 @fullscreen
+
+### Shake
+You can request the position and movement of the Calliope mini and run an action once a change of the values has been detected.
+Use the "on shake“ block from the Input section. Add an "show string Hi!" block from the Basic section and change the content of the string.Your text will be displayed when you shake the Calliope mini. The gesture can be changed by using the dropdown menu to choose the condition.
+
+## Step 3 @fullscreen
+
+### Pins
+The Calliope mini has five rounded corners: -, +, 0 , 1, 2, and 3. If you place one finger on the – corner and another finger on one of the numbered corners, a small electrical current will flow through your body and back to the Calliope mini, thus closing the electrical circuit.
+
+Use the „on pin Pin0 pressed" block from Input. Use the "show string Hi!" block from the basic section.
+Your text will be displayed when pin – and pin 0 are both pressed at the same time.
+
+## Step 4 @fullscreen
+
+### Various input
+You can program the Calliope mini to respond to more than one input. There are two possible ways of doing this:
+You can use indiviual events separated from each other with different actions to run after that condition is met.
+Nevertheless, you can also use an "if" or "while" condition (from the Logic and Loops sections) and wait for your inputs to be met.
--- a/docs/calliope/firststeps/Inputs_L.jpg
+++ b/docs/calliope/firststeps/Inputs_L.jpg
--- a/docs/calliope/firststeps/Loops.jpg
+++ b/docs/calliope/firststeps/Loops.jpg
--- a/docs/calliope/firststeps/Loops.md
+++ b/docs/calliope/firststeps/Loops.md
@ -0,0 +1,18 @@
+# FIRST STEPS: LOOPS
+
+## Introduction @unplugged
+
+As you may have noticed in previous exercises, your program was executed only once by Calliope mini. To change this, you can use loops. Use an infinite loop so that the text runs over the LED grid of your Calliope mini infinitely often.  
+
+## Step 1 @fullscreen
+
+### Infinite loop
+The simplest way is to use a foverever block, from the basic section.
+Everything inside will be repeated forever.
+
+## Step 2 @fullscreen
+
+Of course, you can also specify how often something should be repeated:
+
+### Repeat block
+Use the „on start“ block or any other block that usually initiates a one time cycle. Take the "Repeat 4 times" block from the Loops section and enter the desired number in the number field. Whatever task is within this block will be executed for the number of times you entered within the “Repeat …“ number.
--- a/docs/calliope/firststeps/Loops_L.jpg
+++ b/docs/calliope/firststeps/Loops_L.jpg
--- a/docs/calliope/firststeps/Mathematics.jpg
+++ b/docs/calliope/firststeps/Mathematics.jpg
--- a/docs/calliope/firststeps/Mathematics.md
+++ b/docs/calliope/firststeps/Mathematics.md
@ -0,0 +1,17 @@
+# FIRST STEPS: MATHEMATICS
+
+## Introduction @unplugged
+
+Calliope mini offers you the possibility to use different mathematical operations. You can calculate numbers, create random numbers and save your results in variables.
+
+## Step 1 @fullscreen
+
+### Calculation of numbers
+The Calliope mini is able to perform the 4 basic arithmetic operations addition, subtraction, multiplication and division out of the box:
+
+You can find the required block in the menu Math. From the block's drop-down list you can choose between the four basic arithmetic operations and the exponentiation. To see the result of your calculation, you have to put the block inside a „show number" block from the Basic section. The Calliope mini displays the result of your calculation on the LED grid.
+
+## Step 2 @fullscreen
+
+### Random numbers
+You can have Calliope mini create a random number: You can find the corresponding block in the menu Math ("pick random 0 to 10"). By changing the two numbers within the block, you determine how small or how large the random number is allowed to become.
--- a/docs/calliope/firststeps/Mathematics_L.jpg
+++ b/docs/calliope/firststeps/Mathematics_L.jpg
--- a/docs/calliope/firststeps/Output.jpg
+++ b/docs/calliope/firststeps/Output.jpg
--- a/docs/calliope/firststeps/Output.md
+++ b/docs/calliope/firststeps/Output.md
@ -0,0 +1,23 @@
+# ERSTE SCHRITTE: DAS 5X5 LED RASTER
+
+## Introduction @unplugged
+
+As well as the red LED matrix the Calliope mini also has a built-in loudspeaker (or piezo speaker to be more precise) that allows you to play different tones and an LED with which you can display a huge variety of different colours.
+
+## Step 1 @fullscreen
+
+### The RGB-LED
+The white square under the LED matrix is the RGB-LED. Itworks in exactly the same way as watercolours do. Within this LED there are three smaller LEDs: one red, one green and one blue. When you select a colour in your programming environment, the Calliope mini will automatically display this colour by mixing the three base colours together,
+
+Within the Basic section you select the "set led to red“ block and 
+
+## Step 2 @fullscreen
+
+### Light sensor
+The light is measured by the LED matrix. You can select the light sensor by dragging the block from the Input section into the number block. With this block you can change the colour you want to display. Simply click on the red tap and choose another colour from the menu.
+To turn the LED off, you can use the "turn build-in led off“ block or put the value "0“ on the name of the color.
+
+## Step 3 @fullscreen
+
+### The speaker
+You can play individual notes or music pieces. Simply open the Music section and drag the "play tone 262 Hz for 1 beat“ and chance the value of the tone to see how you can adjust the height of the note.
--- a/docs/calliope/firststeps/Output_L.jpg
+++ b/docs/calliope/firststeps/Output_L.jpg
--- a/docs/calliope/firststeps/Radio.jpg
+++ b/docs/calliope/firststeps/Radio.jpg
--- a/docs/calliope/firststeps/Radio.md
+++ b/docs/calliope/firststeps/Radio.md
@ -0,0 +1,25 @@
+# FIRST STEPS: RADIO
+
+## Introduction @unplugged
+
+There is a Radio module built into the Calliope Mini. This allows for several Calliope mini to communicate with each other and transmit information. To try this out yourself, you will need at least two Calliope mini.
+
+
+## Step 1 @fullscreen
+
+### Allocating a channel
+Firstly you must decide on a channel to use. Only those Calliope mini that are using the same channel will be able to exchange messages with each other. A Calliope mini will not be able to transmit or receive over several channels at the same time. To be able to send information, you must open the radio block and use the radio set group block.
+Please ensure that the channel number you select is between 0 and 255.
+
+## Step 2 @fullscreen
+
+### Sending a message
+To send a message you should select the "radio send string“ block. Now you can enter the string that will be sent on the channel.
+
+## Step 3 @fullscreen
+
+###Receive a message
+Set the same channel as on the sending Calliope mini one.
+Use the "on radio received receivedString“ block to look for data.
+Include the "show string receivedString“ inside.
+Let’s try with two (or more) Calliope mini!
--- a/docs/calliope/firststeps/Radio_L.jpg
+++ b/docs/calliope/firststeps/Radio_L.jpg
--- a/docs/calliope/firststeps/Sensors.jpg
+++ b/docs/calliope/firststeps/Sensors.jpg
--- a/docs/calliope/firststeps/Sensors.md
+++ b/docs/calliope/firststeps/Sensors.md
@ -0,0 +1,30 @@
+# ERSTE SCHRITTE: DAS 5X5 LED RASTER
+
+## Introduction @unplugged
+
+The Calliope mini is equipped with a number of sensors: It has a temperature sensor, a light sensor, a compass as well as a microphone.
+
+## Step 1 @fullscreen
+
+### Displaying sensor data
+In order to display data from your sensors on the Calliope mini’s LED matrix, you need to select a sensor (value). To do so go to the Basic section and select the "show number 0“ block. Within the number you can now change the "0“ to the value of a sensor.
+
+## Step 2 @fullscreen
+
+### Acceleration sensor
+You can select the acceleration values by dragging the block from the Input section and place it on top of the "0“ (which will disappear).
+
+## Step 3 @fullscreen
+
+### Light sensor
+The light is measured by the LED matrix. You can select the light sensor by dragging the block from the Input section into the number block.
+
+## Step 4 @fullscreen
+
+### Compass
+The built in magnetometer allows the Calliope mini to tell in which direction it is facing. This sensor will provide a value between 0 and 360 degrees. The compass will need to be calibrated before use. Follow the instructions on the Calliope mini and tilt it in a circular fashion to display a complete circle. You can start using it by dragging the block from the Input section into the number block.
+
+## Step 4 @fullscreen
+
+### Temperature sensor
+You can select the temperature sensor by dragging the block from the Input section into the number block.
--- a/docs/calliope/firststeps/Sensors_L.jpg
+++ b/docs/calliope/firststeps/Sensors_L.jpg
--- a/docs/calliope/firststeps/Variables.jpg
+++ b/docs/calliope/firststeps/Variables.jpg
--- a/docs/calliope/firststeps/Variables.md
+++ b/docs/calliope/firststeps/Variables.md
@ -0,0 +1,20 @@
+# ERSTE SCHRITTE: DAS 5X5 LED RASTER
+
+## Introduction @unplugged
+
+As in a football match, where the number of goals scored during the match can change, the value of a variable can also change during a running program.
+
+By clicking on the Variables section and then on the "Make a variable…“ button within this section you will generate a new variable. Now you can determine the name.
+
+## Step 1 @fullscreen
+
+By clicking on the Variables section and then on the "Make a variable…“ button within this section you will generate a new variable. Now you can determine the name.
+
+## Step 2 @fullscreen
+
+You can find a separate block for each variable, which you can use to display its value on the LED grid of Calliope mini by selecting the "show number 0“ block and use the "set variable to 0“ block from the Variables section and add this on a line before. if you change this number, the number on the grid will change accordingly.
+
+## Step 3 @fullscreen
+
+### Count your score
+By combining what you have learned so far, you can program a simple score counter: When button A is pressed, the number of goals variable is increased by one numerical value and then displayed. Have a try!
--- a/docs/calliope/firststeps/Variables_L.jpg
+++ b/docs/calliope/firststeps/Variables_L.jpg
--- a/docs/calliope/firststeps/connecting.jpg
+++ b/docs/calliope/firststeps/connecting.jpg
--- a/docs/calliope/firststeps/firstSteps.jpg
+++ b/docs/calliope/firststeps/firstSteps.jpg
--- a/docs/calliope/firststeps/firstSteps.md
+++ b/docs/calliope/firststeps/firstSteps.md
@ -0,0 +1,61 @@
+# First Steps
+
+## Introduction @unplugged
+
+### 1) Connecting
+
+Connect your mini to your computer via a micro USB cable or Bluetooth. Macs, PCs, Chromebooks, Linux systems, Smartphones and Tablets are supported.
+
+Your Calliope mini will show up on your computer as a drive called 'MINI'.
+
+Open your favourite browser and head to our website and select Editor in the main navigation.
+
+For example drag and drop some blocks and try your program on the Simulator within the editor.
+
+Click the Download button in the editor. This will download a 'hex' file, which is a compact format of your program that your mini can read. Once the file has been downloaded, just copy it to your Calliope mini just like copying a file to a USB stick.
+
+![Connecting Image](/calliope/firststeps/connecting.jpg)
+
+
+## Introduction @unplugged
+
+### 2) Power it Up
+
+The Calliope mini requires a power source to work. You can either connect your Calliope mini directly to a computer using a Micro USB cable or you can power it using a battery pack.
+Here are the instructions on how to connect the battery pack to your Calliope mini:
+
+The supplied battery pack requires two AAA batteries.
+
+Carefully insert the small white plastic connector from the battery pack into the board’s battery socket.
+
+Be careful to insure that the ridge on the plug is facing upwards.
+
+If the plug slides easily into the socket then you are attaching it correctly. Otherwise, turn the plug round and re-insert it into the socket. Slide it to "on“ and your Calliope mini is powered by the batteries.
+
+![Powering Image](/calliope/firststeps/powerItUp.png)
+
+
+## Introduction @unplugged
+
+### 3) Play!
+
+You can now play arround or try some of our other guided first-steps tutorials...
+
+[Learn how to write your name on the LED-Matrix](#tutorial:/calliope/firststeps/5x5LED)
+
+[Play with colors and sound](#tutorial:/calliope/firststeps/Output)
+
+[See how to Controll your mini with the buttons and pins](#tutorial:/calliope/firststeps/Inputs)
+
+
+## Step 1
+
+Play!
+
+You can now play arround or try some of our other guided first-steps tutorials...
+
+[Learn how to write your name on the LED-Matrix](#tutorial:/calliope/firststeps/5x5LED)
+
+[Play with colors and sound](#tutorial:/calliope/firststeps/Output)
+
+[See how to Controll your mini with the buttons and pins](#tutorial:/calliope/firststeps/Inputs)
--- a/docs/calliope/firststeps/powerItUp.png
+++ b/docs/calliope/firststeps/powerItUp.png
--- a/docs/calliope/links.md
+++ b/docs/calliope/links.md
@ -0,0 +1,47 @@
+# Projects
+
+Here are some cool tutorials to get you started with your @boardname@!
+
+## Basic
+
+```codecard
+[
+{
+  "name": "Shop",
+  "url":"https://shop.calliope.cc",
+  "description": "You can get the mini at the official calliope store.",
+  "imageUrl": "/calliope/links/thumbnail_shop.gif",
+  "largeImageUrl": "",
+  "label": "",
+  "buttonLabel": "Open Calliope Shop",
+  "labelClass": "green small ribbon"
+}, {
+  "name": "Projects",
+  "url":"https://calliope.cc/en/projekte",
+  "description": "A collection of calliope mini projects",
+  "imageUrl": "/calliope/links/thumbnail_projects.gif",
+  "largeImageUrl": "",
+  "label": "",
+  "buttonLabel": "View Projects",
+  "labelClass": "green small ribbon"
+}, {
+  "name": "Teaching materials",
+  "url":"https://calliope.cc/schulen/schulmaterial",
+  "description": "",
+  "imageUrl": "/calliope/links/thumbnail_didactic_material.gif",
+  "largeImageUrl": "",
+  "label": "",
+  "buttonLabel": "View",
+  "labelClass": "green small ribbon"
+}, {
+  "name": "Forum",
+  "url":"https://forum.calliope.cc",
+  "description": "Be a part of our comunity",
+  "imageUrl": "/calliope/links/thumbnail_community.gif",
+  "largeImageUrl": "",
+  "label": "",
+  "buttonLabel": "Open Forum",
+  "labelClass": "green small ribbon"
+}
+]
+```
--- a/docs/calliope/links/thumbnail_community.gif
+++ b/docs/calliope/links/thumbnail_community.gif
--- a/docs/calliope/links/thumbnail_didactic_material.gif
+++ b/docs/calliope/links/thumbnail_didactic_material.gif
--- a/docs/calliope/links/thumbnail_projects.gif
+++ b/docs/calliope/links/thumbnail_projects.gif
--- a/docs/calliope/links/thumbnail_shop.gif
+++ b/docs/calliope/links/thumbnail_shop.gif
--- a/docs/calliope/tutorials.md
+++ b/docs/calliope/tutorials.md
@ -0,0 +1,74 @@
+# Projects
+
+Here are some cool tutorials to get you started with your @boardname@!
+
+## Basic
+
+```codecard
+[{
+  "name": "Flashing Heart",
+  "url":"/projects/flashing-heart",
+  "description": "Make an animated flashing heart.",
+  "imageUrl": "/calliope/tutorials/01_flashing_heart.gif",
+  "largeImageUrl": "",
+  "cardType": "tutorial",
+  "label": "",
+  "labelClass": "purple ribbon large"
+}, {
+  "name": "Name Tag",
+  "description": "Scroll your name on the screen",
+  "imageUrl": "/calliope/tutorials/02_nametag.gif",
+  "url": "/projects/name-tag",
+  "cardType": "tutorial"
+}, {
+  "name": "Smiley Buttons",
+  "url":"/projects/smiley-buttons",
+  "description": "Show different smiley images by pressing the buttons.",
+  "imageUrl": "/calliope/tutorials/03_smiley_button.gif",
+  "largeImageUrl": "",
+  "cardType": "tutorial"
+}, {
+  "name": "Dice",
+  "url":"/projects/dice",
+  "description": "Shake the dice and see what number comes up!",
+  "imageUrl": "/calliope/tutorials/04_dice.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Love Meter",
+  "url":"/projects/love-meter",
+  "description": "The @boardname@ is feeling the love, see how much!",
+  "imageUrl":"/calliope/tutorials/05_love_meter.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Mini Chat",
+  "url":"/projects/mini-chat",
+  "description": "Build your own social network made of minis.",
+  "imageUrl": "/calliope/tutorials/06_mini_chat.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Rock Paper Scissors",
+  "url":"/projects/rock-paper-scissors",
+  "description": "Make the Rock-Paper-Scissors game on your @boardname@ and challenge your friends.",
+  "imageUrl":"/calliope/tutorials/07_stone_paper_scissors.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Coin Flipper",
+  "url":"/projects/coin-flipper",
+  "description": "Guess the coin toss and see if you're lucky.",
+  "imageUrl": "/calliope/tutorials/08_coin_flipper.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Snap the dot",
+  "url": "/projects/snap-the-dot",
+  "description": "Use the game blocks to create a skill game",
+  "imageUrl": "/calliope/tutorials/09_snap_the_dot.gif",
+  "cardType": "tutorial"
+}, {
+  "name": "Multi Dice",
+  "url": "/projects/multi-dice",
+  "description": "Compete with multiple dices",
+  "imageUrl": "/calliope/tutorials/10_multi_dice.gif",
+  "cardType": "tutorial"
+}
+]
+```
--- a/docs/calliope/tutorials/01_flashing_heart.gif
+++ b/docs/calliope/tutorials/01_flashing_heart.gif
--- a/docs/calliope/tutorials/01_flashing_heart_animation.gif
+++ b/docs/calliope/tutorials/01_flashing_heart_animation.gif
--- a/docs/calliope/tutorials/02_nametag.gif
+++ b/docs/calliope/tutorials/02_nametag.gif
--- a/docs/calliope/tutorials/02_nametag_animation.gif
+++ b/docs/calliope/tutorials/02_nametag_animation.gif
--- a/Show More
+++ b/Show More