<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo on Camping Coder</title><link>https://www.campingcoder.com/series/hugo/</link><description>Recent content in Hugo on Camping Coder</description><generator>Hugo</generator><language>en-US</language><copyright>All rights reserved</copyright><lastBuildDate>Wed, 16 May 2018 00:00:00 -0500</lastBuildDate><atom:link href="https://www.campingcoder.com/series/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugo and droppy, Chromebook friends</title><link>https://www.campingcoder.com/2018/05/hugo-and-droppy-chromebook-friends/</link><pubDate>Wed, 16 May 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/05/hugo-and-droppy-chromebook-friends/</guid><description>&lt;p&gt;&lt;figure class="image-figure"&gt;&lt;img src="https://www.campingcoder.com/post/20180510-droppy.svg" alt="droppy logo" loading="lazy" decoding="async"&gt;&#10; &#10; &#10; &lt;figcaption&gt;droppy logo&lt;/figcaption&gt;&#10; &#10; &#10;&lt;/figure&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;If you read the post on &lt;a href="https://www.campingcoder.com/2018/02/hugo---gulp--chromebook-awesomeness/" target="_blank" rel="noopener noreferrer"&gt;Hugo + gulp = Chromebook awesomeness&lt;/a&gt; then you know that there are a lot of steps in it, and a lot of parts moving to make the solution work. While it does meet the need I noticed that it&amp;rsquo;s a little much for daily use. That&amp;rsquo;s really where &lt;a href="https://github.com/silverwind/droppy" target="_blank" rel="noopener noreferrer"&gt;droppy&lt;/a&gt; comes into the picture. It runs on Raspberry Pi&amp;rsquo;s, so its light weight, and has a great interface - best of all it has a code editor built right in!&lt;/p&gt;</description></item><item><title>Hugo + SHH - gulp = a new workflow</title><link>https://www.campingcoder.com/2018/05/hugo---shh---gulp--a-new-workflow/</link><pubDate>Thu, 03 May 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/05/hugo---shh---gulp--a-new-workflow/</guid><description>&lt;p&gt;If you ready the post on &lt;a href="https://www.campingcoder.com/2018/02/hugo---gulp--chromebook-awesomeness/" target="_blank" rel="noopener noreferrer"&gt;Hugo + gulp = Chromebook awesomeness&lt;/a&gt; you&amp;rsquo;ll know that I&amp;rsquo;ve been adjusting my workflow to get Hugo to live reload on Chrome OS. While that solution worked okay, there were a few issues with it.&lt;/p&gt;&#10;&lt;p&gt;First off, the process required that a gulp task be setup to &lt;strong&gt;sync&lt;/strong&gt; the files with the Termux. This isn&amp;rsquo;t a big deal, but as a project grows there&amp;rsquo;s more to sync, which causes the process to slow down. Additionally, it stores a duplicate of the files, which digs into the precious limited space on many Chromebooks.&lt;/p&gt;</description></item><item><title>Adding search to Hugo with elasticlunr</title><link>https://www.campingcoder.com/2018/04/adding-search-to-hugo-with-elasticlunr/</link><pubDate>Thu, 12 Apr 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/04/adding-search-to-hugo-with-elasticlunr/</guid><description>&lt;p&gt;Well, it finally happened. Shortly after our &lt;a href="https://www.campingcoder.com/2018/04/post-number-50/" target="_blank" rel="noopener noreferrer"&gt;50th post&lt;/a&gt;, we realized without using google or in current post links it was becoming harder to &lt;strong&gt;find&lt;/strong&gt; articles that had been written in the past. It&amp;rsquo;s not a secret that we use &lt;a href="http://gohugo.io/" target="_blank" rel="noopener noreferrer"&gt;Hugo&lt;/a&gt;, and it is a great platform for static sites, just not for search. After &lt;strong&gt;searching&lt;/strong&gt; on search for &lt;a href="http://gohugo.io/" target="_blank" rel="noopener noreferrer"&gt;Hugo&lt;/a&gt; we&amp;rsquo;ve finally implemented a solution that works for us without the need for outside services.&lt;/p&gt;</description></item><item><title>Serverless dynamic content with Hugo and JavaScript</title><link>https://www.campingcoder.com/2018/03/serverless-dynamic-content-with-hugo-and-javascript/</link><pubDate>Thu, 08 Mar 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/03/serverless-dynamic-content-with-hugo-and-javascript/</guid><description>&lt;p&gt;Wow that&amp;rsquo;s a $10 title, but it&amp;rsquo;s really the goal of this post - to show you how you can use Hugo and still retain all of the JavaScript goodies for dynamic content. For those who don&amp;rsquo;t know, in general for dynamic content you will typically require having a server with a database somewhere which allows you to request data. With Hugo there is no database, or place to pull the content, at least at first glance.&lt;/p&gt;</description></item><item><title>Hugo + gulp = Chromebook awesomeness</title><link>https://www.campingcoder.com/2018/02/hugo---gulp--chromebook-awesomeness/</link><pubDate>Thu, 15 Feb 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/02/hugo---gulp--chromebook-awesomeness/</guid><description>&lt;p&gt;One of my favorite things about writing code is that you can learn or fail fast - typically the failures teach you a lot more too. The quick iterations really are fun and when they make your day just an increment better, you get a sense of accomplishment. If you&amp;rsquo;ve read my&#10;&lt;a href="https://www.campingcoder.com/2017/11/running-hugo-on-chromebook/" target="_blank" rel="noopener noreferrer"&gt;initial running Hugo on a Chromebook&lt;/a&gt; post which was followed by the &lt;a href="https://www.campingcoder.com/2018/01/resetting-my-chromebook-back-to-stock/" target="_blank" rel="noopener noreferrer"&gt;Hugo on 100% stock Chromebook&lt;/a&gt; you&amp;rsquo;ll get a sense of how the &lt;em&gt;little&lt;/em&gt; iterations make a difference.&lt;/p&gt;</description></item><item><title>Resetting My Chromebook Back to Stock</title><link>https://www.campingcoder.com/2018/01/resetting-my-chromebook-back-to-stock/</link><pubDate>Mon, 29 Jan 2018 00:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2018/01/resetting-my-chromebook-back-to-stock/</guid><description>&lt;p&gt;With all the news coverage of the Meltdown, Spectre and whatever name exploits in the media, when I received the chance to upgrade to the newest version of Chrome OS, I jumped on it. This particular version for my &lt;a href="https://www.campingcoder.com/2017/12/thinkpad-chromebook-a-year-later/" target="_blank" rel="noopener noreferrer"&gt;ThinkPad Chromebook&lt;/a&gt; also included a firmware upgrade, which to me meant something new - I have not seen a firmware update in Chrome OS until then. The downside of the update is that it required a &amp;lsquo;Power wash&amp;rsquo; of Chrome OS, essentially resetting the machine back to stock. I thought about it for a little and decided to take it a step further and take the machine out of developer mode and see if with Android apps if I could mitigate the need for the elevated permissions on Chrome OS.&lt;/p&gt;</description></item><item><title>Running Hugo on Chromebook</title><link>https://www.campingcoder.com/2017/11/running-hugo-on-chromebook/</link><pubDate>Sun, 12 Nov 2017 14:00:00 -0500</pubDate><guid>https://www.campingcoder.com/2017/11/running-hugo-on-chromebook/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; I&amp;rsquo;ve made a few adjustments to the process in my &lt;a href="https://www.campingcoder.com/2018/01/resetting-my-chromebook-back-to-stock/" target="_blank" rel="noopener noreferrer"&gt;Resetting My Chromebook Back to Stock&lt;/a&gt; post. Mainly script cleanup and a way to do this without being in developer mode. This post still has the basics and a lot of good info not covered in the new post.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;&lt;figure class="image-figure"&gt;&lt;img src="https://www.campingcoder.com/post/2017-11-12_General_Run-Hugo-on-Chromebook-1.jpeg" alt="Termux and hugo" loading="lazy" decoding="async"&gt;&#10; &#10; &#10; &lt;figcaption&gt;Termux and hugo&lt;/figcaption&gt;&#10; &#10; &#10;&lt;/figure&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;If you read any of my post on &lt;a href="https://www.campingcoder.com/post/android-apps-arrive-on-thinkpad-chromebook-13/" target="_blank" rel="noopener noreferrer"&gt;Android apps on on Thinkpad Chromebook&lt;/a&gt; then you know that my primary machine is a &lt;a href="https://www.amazon.com/gp/product/B01HBJ60ME/ref=as_li_tl?ie=UTF8&amp;amp;tag=campingcoder-20&amp;amp;camp=1789&amp;amp;creative=9325&amp;amp;linkCode=as2&amp;amp;creativeASIN=B01HBJ60ME&amp;amp;linkId=28454eafed263b6d543f593806107216" target="_blank" rel="noopener noreferrer"&gt;Thinkpad 13 Chromebook&lt;/a&gt;. This was an artificially imposed restriction on my end, to make me do more with less. While the experience has be very pleasant there have been a few places where a &amp;rsquo;little&amp;rsquo; more power or options would be welcomed - that&amp;rsquo;s where Termux comes into play.&lt;/p&gt;</description></item></channel></rss>