From 83ff618f8a9581f95adfbe312b788ecec22df59c Mon Sep 17 00:00:00 2001 From: bt Date: Tue, 12 Dec 2023 11:11:16 -0500 Subject: --- posts/chromebook-web-dev.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'posts') diff --git a/posts/chromebook-web-dev.md b/posts/chromebook-web-dev.md index 4d3214a..95b76a8 100644 --- a/posts/chromebook-web-dev.md +++ b/posts/chromebook-web-dev.md @@ -1,6 +1,5 @@ -# Web Development on a $200 Chromebook - -2020-01-07 +[[!meta title="Web Development on a $200 Chromebook"]] +[[!meta date="2020-01-07"]] *This blog post was written, edited and tested locally* 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. @@ -10,7 +9,7 @@ First, we need to ask an important question: why use a Chromebook for web develo 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: -- Blazingly fast boot times +- Blazing fast boot times - Long lasting battery life (roughly 8 hours with consistent usage) - Extremely cheap entry point for "low-end" devices - And, more recently, support for Android & Linux apps -- cgit v1.2.3-54-g00ecf