From 16d28628aca9b2d356de31c319f5e7bc0f5b2b02 Mon Sep 17 00:00:00 2001
From: Bradley Taunt <bt@btxx.org>
Date: Sat, 8 Jun 2024 13:43:37 -0400
Subject: Remove incorrectly generated files, fix up markdown articles

---
 build/chromebook-web-dev/index.html | 23 ++---------------------
 1 file changed, 2 insertions(+), 21 deletions(-)

(limited to 'build/chromebook-web-dev')
diff --git a/build/chromebook-web-dev/index.html b/build/chromebook-web-dev/index.html
index 9c4ddac..0d67ba1 100644
--- a/build/chromebook-web-dev/index.html
+++ b/build/chromebook-web-dev/index.html
@@ -3,11 +3,12 @@
 <head>
 	<meta charset="utf-8">
 	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<meta name="color-scheme" content="dark light">
 	<link rel="icon" href="data:,">
 	<title>Web Development on a $200 Chromebook</title>
 	<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
 	<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
-<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
 </head>
 
 <nav>
@@ -16,36 +17,23 @@
 
 <main>
 <h1 id="web-development-on-a-200-chromebook">Web Development on a $200 Chromebook</h1>
-
 <p>2020-01-07</p>
-
 <p><em>This blog post was written, edited and tested locally</em> on a cheap $200 Chromebook. The article draft was composed in Sublime Text. Jekyll (the SSG this website uses) was generated via the Linux Beta Terminal running alongside Chrome OS. It was then pushed to the Github repo from the same Terminal and published automatically to Netlify. But more on that later.</p>
-
 <p>First, we need to ask an important question: why use a Chromebook for web development? Maybe a better question might be: why not?</p>
-
 <h2 id="mild-interest-turned-into-an-experiment">Mild interest turned into an experiment</h2>
-
 <p>Looking from the outside, I always liked the concept of the Chrome OS ecosystem. It had a solid list of features that appealed to me, specifically:</p>
-
 <ul>
 <li>Blazingly fast boot times</li>
 <li>Long lasting battery life (roughly 8 hours with consistent usage)</li>
 <li>Extremely cheap entry point for &#8220;low-end&#8221; devices</li>
 <li>And, more recently, support for Android &#38; Linux apps</li>
 </ul>
-
 <p>The obvious downside to using a Chromebook is the lack of a &#8220;real&#8221; operating system. A Windows, Mac or Linux machine will always have more flexibility and depth than a simple Chromebook. But I&#8217;ve found that simple is all I need - or want.</p>
-
 <p><strong>Side note:</strong> <em>I wrote an article not to long ago about <a href="https://uglyduck.ca/stop-crawling-google/">blocking Google from my website</a> and I can see how this current post may come across as hypocritical. Since the search&#47;AMP teams are not that same as the Chrome OS &#47; Chromebook development team, I can view each of those projects based on their own merits. If you still view me as a hypocrite, that&#8217;s fine</em> :)</p>
-
 <h2 id="my-use-case-ymmv">My use case (YMMV)</h2>
-
 <p>I ended up grabbing the <a href="https://amzn.to/2Xvx20q">Acer 11 N7 Chromebook</a> off of Amazon for $200 (on sale and in Canuck bucks). It comes packed with 4GB of RAM with an Intel Celeron (1.6GHz) and 32GB of storage. Fairly barebones stuff.</p>
-
 <p>My day-to-day use cases are fairly straightforward. I work with git, static site generators, WordPress locally and on staging servers, edit documents, send emails and watch stupid YouTube videos. You know, the basics. My dirt-cheap Chromebook handles all of these things with ease.</p>
-
 <p>My Chromebook setup is as follows:</p>
-
 <ul>
 <li>Linux Beta (ships with <code>git</code>, etc)</li>
 <li>Sublime Text (you can always use VSCode if you prefer)</li>
@@ -53,19 +41,12 @@
 <li>Local by Flywheel (local WordPress development)</li>
 <li>Figma in Chrome (UI design &#47; mockups)</li>
 </ul>
-
 <p>That&#8217;s it. I understand other developers may require a lot more than this, but with Linux running in a container alongside Chrome OS you can pretty much run anything you could possibly need (excluding exclusive Mac &#38; Windows apps, of course).</p>
-
 <h2 id="can-a-200-chromebook-be-your-next-web-dev-machine">Can a $200 Chromebook be your next web dev machine?</h2>
-
 <p>For me? Yes. For you? Maybe.</p>
-
 <p>I mean, it really just depends on what you need your machine to accomplish. If you can be productive and the apps you use are just as fast and responsive as they would be on a more robust OS - then I say go for it. You don&#8217;t even need to be a cheapo like me, instead you can snag a fancier Chromebook or Google&#8217;s own Pixelbook. There are a ton of options when it comes to Chrome OS based devices.</p>
-
 <p>If you wanted to experiment to see if the Chrome OS ecosystem could work with your development flow, you can always check out something like <a href="https://www.neverware.com/freedownload">CloudReady</a> to test on your current machine before pulling the trigger.</p>
-
 <p>In the end, it doesn&#8217;t matter what operating system or apps you use to get your development work done - so long as it is productive and easy-to-use.</p>
-
 <p>For my current situation, all I need is my cheap little Chromebook.</p>
 <footer role="contentinfo">
     <h2>Menu Navigation</h2>
-- 
cgit v1.2.3-54-g00ecf

