Site updated at 2016-05-21 22:00:31 UTC

This commit is contained in:
Travis CI 2016-05-21 22:00:31 +00:00
parent 1399856378
commit cc19822b04
328 changed files with 7619 additions and 978 deletions

View file

@ -189,6 +189,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -212,12 +218,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -195,6 +195,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -218,12 +224,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -203,6 +203,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -226,12 +232,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -187,6 +187,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -210,12 +216,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -204,6 +204,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -227,12 +233,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -222,6 +222,12 @@
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -245,12 +251,6 @@
</li>
<li class="post">
<a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/">iBeacons: Making presence detection work better (part I)</a>
</li>
</ul>
</section>

View file

@ -313,6 +313,12 @@ For example, my wife works next door - and I couldnt detect whether shes a
<ul class="divided">
<li class="post">
<a href="/blog/2016/05/21/release-020/">0.20: Roku, Last.FM, AWS, Twilio</a>
</li>
<li class="post">
<a href="/blog/2016/05/18/why-we-use-polymer/">Why we use web components and Polymer</a>
</li>
@ -336,8 +342,6 @@ For example, my wife works next door - and I couldnt detect whether shes a
</li>
</ul>
</section>