removed preview images, read more link, mobile nav height

Makefile

@@ -45,7 +45,7 @@ ifdef DELETE
 	S3_DELETE=--delete
 endif
 S3_CACHE_CONTROL?=86400
-S3_CMD=s3 sync ${S3_DRYRUN} ${S3_DELETE} --cache-control max-age=${S3_CACHE_CONTROL} --acl "public-read" --sse "AES256"
+S3_CMD=s3 sync ${S3_DRYRUN} ${S3_DELETE} --metadata-directive REPLACE --cache-control max-age=${S3_CACHE_CONTROL},public --acl "public-read" --sse "AES256"
 S3_CMD_WEB=${S3_CMD} public/ s3://${WEB_BUCKET}
 S3_CMD_STATIC=${S3_CMD} static/ s3://${STATIC_BUCKET}
 CLOUDFRONT_PATHS?='/*'

config.yaml

@@ -72,12 +72,14 @@ params:
 
   # paginate of archives, tags and categories
   archivePaginate: 20
-  # show 'xx Posts In Total' in archive page ?
+  # show 'xx Posts In Total' in archive page
   showArchiveCount: true
   # The date format to use; for a list of valid formats, see https://gohugo.io/functions/format/
   dateFormatToUse: "2006-01-02"
-  # show word count and read time ?
-  moreMeta: false
+  # show word count and read time
+  moreMeta: true
+  # show "read more" link on post summary
+  readMoreEnabled: false
   postMetaInFooter: true   # contain author, lastMod, markdown link, license
   linkToMarkDown: true    # Only effective when hugo will output .md files.
   contentCopyright: '<a rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc/4.0/80x15.png" /></a>'

content/post/aperture-study.md

@@ -12,10 +12,11 @@ deminishing returns. Simply put: it makes the image look "soft", or otherwise
 out-of-focus. In this post I aim to find out find the best *acceptable* aperture
 setting for a specific lens.
 
+<!--more-->
+
 {{< thumb src="/static/img/aperture-study/f17-f40-comp.jpg"
     sub="f/1.7 vs. f/4.0"
     alt="Photo comparing aperture depth-of-field of f/1.7 versus f/4.0 (sharper)" >}}
-<!--more-->
 
 # The Setup
 

content/post/emacs_clang_libopencm3.md

@@ -12,12 +12,12 @@ images:
 With some minor dependencies, it's fairly straightforward in setting up your
 Emacs workflow to include IntelliSense-like auto-completion!
 
+<!--more-->
+
 {{< img src="/static/img/emacs-clang-libopencm3/header-completion.png"
     sub="Header Completion"
     alt="Screenshot showing auto-completion for C header files in emacs" >}}
 
-<!--more-->
-
 # Dependencies
 
 ## System

content/post/headphone-fix.md

@@ -10,9 +10,10 @@ images:
 A colleague offered a pair of Bern Bluetooth drop-in headphones to me fore free,
 with the catch being: _I had to fix them_
 
+<!--more-->
+
 {{< thumb src="/static/img/headphone-fix/IMG_7505.jpg"
     alt="Photo of Bern brand headphones under magnifying glass" >}}
-<!--more-->
 
 # Don't Turn It On, Take It Apart
 

content/post/lineageos_pixel3a.md

@@ -10,12 +10,19 @@ hideHeaderAndFooter: false
 images:
   - "/static/img/lineageos-pixel3a/lineage-settings.png"
 ---
+{{< admonition warning "Out of Date" >}}
+This guide is now out of date since LineageOS officially supports the Pixel 3a,
+see more here: <https://wiki.lineageos.org/devices/sargo/install>
+{{< /admonition >}}
+
 In this post I aim to highlight my findings in deciding to go through  the
 process of installing LineageOS on my Pixel 3a. Currently, LineageOS does not
 officially support the Pixel 3a. However, InvisibleK (Dan Pasanen) does host
 updated versions of his unofficial LineageOS build for the Pixel 3a complete
 with a custom recovery to utilize for this purpose!
 
+<!--more-->
+
 {{< thumbgallery >}}
     {{< thumb src="/static/img/lineageos-pixel3a/lineage-settings.png"
         alt="Screenshot showing the LineageOS version and other LineageOS settings on the Pixel 3a" >}}
@@ -23,12 +30,6 @@ with a custom recovery to utilize for this purpose!
         alt="Screenshot showing the LineageOS Trust feature" >}}
 {{< /thumbgallery >}}
 
-<!--more-->
-{{< admonition warning "Out of Date" >}}
-This guide is now out of date since LineageOS officially supports the Pixel 3a,
-see more here: <https://wiki.lineageos.org/devices/sargo/install>
-{{< /admonition >}}
-
 # Thank You
 
 Before going on any further, I'd like to take a moment to give my sincere thanks

content/post/stm32-part0.md

@@ -12,11 +12,11 @@ images:
 One of the simplest projects to get started with the STM32 microcontroller
 series: turn on the lights!
 
+<!--more-->
+
 {{< thumb src="/static/img/stm32-examples/part0/stm32-basic-gpio-leds.jpeg"
     alt="Photo of STM32 discovery board with illuminated green and blue LEDs" >}}
 
-<!--more-->
-
 {{< admonition warning "Windows Users" >}}
 This series of write-ups assumes the reader is on a Linux operating
 system. Windows users _can_ utilize the [**Windows Subsystems for

content/post/stm32-part1.md

@@ -16,11 +16,11 @@ LED. However, it is my belief that this leads to confusion for beginners and
 only opens the door to misunderstandings. That being said, we will be using
 timers and their associated GPIO ports with Alternate Function modes.
 
+<!--more-->
+
 {{< img src="/static/img/stm32-examples/part1/blinky.gif"
     alt="Animated picture showing alternating blinking green and blue LEDs" >}}
 
-<!--more-->
-
 # Straight to the Chase
 
 For those that want to cut to the chase and save time, here is the full source

content/post/thinkpad_usb_fix.md

@@ -12,10 +12,11 @@ port nearest to the SD card reader had been broken. The pad (_or bolster_) was
 missing, along with 3 out of 4 pins having been completely broken off. Needless
 to say this required fixing.
 
+<!--more-->
+
 {{< thumb src="/static/img/thinkpad-usb-fix/DSC04781.jpg"
     sub="Final result"
     alt="Photo showing fixed USB receptacle on ThinkPad laptop" >}}
-<!--more-->
 
 # Damage Assessment