Site updated at 2017-10-29 13:20:31 UTC

blog/index.html

@@ -67,6 +67,37 @@
     <div class="grid-wrapper">
       <div class="grid grid-center">
         <div class="grid__item two-thirds lap-one-whole palm-one-whole">
+  <article class="listing">
+    <header>
+  <h1 class="beta">
+    <a href="/blog/2017/10/28/demo/">Home Assistant Demo</a>
+  </h1>
+  <div class="meta clearfix">
+    <time datetime="2017-10-28T08:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> October 28, 2017</time>
+    <span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
+    <span><i class='icon-time'></i> four minutes reading time</span>
+    <span>
+    <i class="icon-tags"></i>
+    <ul class="tags unstyled">
+        <li>How-To</li>
+    </ul>
+  </span>
+      <a class='comments'
+         href="/blog/2017/10/28/demo/#disqus_thread"
+         >Comments</a>
+  </div>
+</header>
+  <div class="entry-content clearfix">
+    <p>If you are planning to host a Home Assistant meetup or doing a talk, then you probably want to show Home Assistant to an audience. You could use a Wireless router, bulbs, switches, and a single board computer to do a realistic demo. For a workshop, this is what I usually do because I think that working with physical hardware is more fun for the participants. The issue is that you need time to set up, power and space. For a talk or in a location, where you only have a beamer and a table or a lectern, the physical hardware approach is not very convenient.</p>
+<p>The simplest way to show Home Assistant to others is the online demo at <a href="https://home-assistant.io/demo/">https://home-assistant.io/demo/</a></p>
+<p class="img">
+  <img src="/images/blog/2017-10-interactive-demo/online-demo.png" />
+  Home Assistant’s online demo
+</p>
+      <a class="btn pull-right" href="/blog/2017/10/28/demo/#read-more">Read on &rarr;</a>
+  </div>
+  </article>
+  <hr>
   <article class="listing">
     <header>
   <h1 class="beta">
@@ -444,53 +475,6 @@
   <li><a href="http://www.duckdns.org/">DuckDNS</a></li>
   <li><a href="https://letsencrypt.org/">Let’s Encrypt</a></li>
 </ul>
-  </div>
-  </article>
-  <hr>
-  <article class="listing">
-    <header>
-  <h1 class="beta">
-    <a href="/blog/2017/09/26/new-hassio-build-system/">Improved Hass.io build system</a>
-  </h1>
-  <div class="meta clearfix">
-    <time datetime="2017-09-26T03:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> September 26, 2017</time>
-    <span class="byline author vcard"><i class='icon-user'></i> Pascal Vizeli</span>
-    <span><i class='icon-time'></i> two minutes reading time</span>
-    <span>
-    <i class="icon-tags"></i>
-    <ul class="tags unstyled">
-        <li>Technology</li>
-    </ul>
-  </span>
-      <a class='comments'
-         href="/blog/2017/09/26/new-hassio-build-system/#disqus_thread"
-         >Comments</a>
-  </div>
-</header>
-  <div class="entry-content clearfix">
-    <p class="note">
-This is going to be a technical post for Hass.io add-on developers and people that run locally build add-ons (not the default).
-</p>
-<p>Two months ago we <a href="/blog/2017/07/25/introducing-hassio/">introduced Hass.io</a>, allowing our users to easily install, update and manage their Home Assistant installation. In this short time we’ve seen great adoption from the community. Around 20% of our users are choosing Hass.io as their method of running Home Assistant today. We’ve also seen many add-ons being made available on <a href="https://community.home-assistant.io/tags/hassio-repository">the forums</a>. There are currently 14 reposities full of add-ons being shared!</p>
-<p>Hass.io is built on top of Docker, a container runtime. One thing that Docker did not support was dynamic build environements. That was annoying for Hass.io because by supporting multiple CPU architectures, that was exactly what we needed! Luckily this feature has been added in Docker 17.05. By moving to Docker 17.05 as the minimum supported version we will be able to replace our templated Dockerfile approach with standard Dockerfiles that work out of the box. Thanks to <a href="https://github.com/frenck">Frenck</a> for notifying us of this new build feature.</p>
-<p>This change only impacts people that build add-ons or use add-ons that are built locally. You can check if your add-on is building locally on the detail page of add-ons.</p>
-<p class="note">
-If you are an add-on developer, read <a href="/developers/hassio/addon_publishing/#custom-add-ons">the documentation</a> on how to publish your add-ons to Docker Hub. This will greatly improve the user experience.
-</p>
-<h3><a class="title-link" name="template-changes" href="#template-changes"></a> Template changes</h3>
-<p>As an add-on developer, you will only have to change one line in your template to make it compatible with the new system. If you wish, you can also change the default build options for your image using the new <a href="/developers/hassio/addon_config/#add-on-extended-build"><code class="highlighter-rouge">build.json</code></a> file.</p>
-<p>Old:</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>FROM %%BASE_IMAGE%%
-</code></pre>
-</div>
-<p>New:</p>
-<div class="highlighter-rouge"><pre class="highlight"><code>ARG BUILD_FROM
-FROM $BUILD_FROM
-</code></pre>
-</div>
-<h3><a class="title-link" name="when" href="#when"></a> When</h3>
-<p>The new system will become active with Hass.io 0.64 and Host OS 1.1. Host OS 1.1 is available today. Navigate to Advanced Settings in the Hass.io panel to start the OTA update.</p>
-<p>We have also updated our build scripts and replaced it with a <a href="https://github.com/home-assistant/hassio-build/tree/master/builder">builder docker engine</a>. This builder makes deploying Hass.io components very easy. All basic functionality is supported. If you want more functionality, check out <a href="https://github.com/hassio-addons/build-env">the builder by the Community Hass.io Add-ons project</a>.</p>
   </div>
   </article>
   <hr>