updating for new public render

cv.adoc

@@ -11,9 +11,11 @@ Last updated {localdatetime}
 :imagesdir: images
 :sectlinks:
 ifeval::["{doctype}" != "article"]
+ifeval::["{filetype}" != "pdf"]
 :toc: preamble
 :toc2: left
 endif::[]
+endif::[]
 :idprefix:
 :toclevels: 7
 :source-highlighter: highlightjs
@@ -22,7 +24,7 @@ endif::[]
 :techexp: cv.adoc[]#technical_experience
 //:techexp: #technical_experience
 
-include::includes/header.adoc[]
+//include::includes/header.adoc[]
 
 include::includes/intro.adoc[]
 (If you are looking for my résumé instead, which is much more succinct, that can be found <<resume.adoc#, here>>.)

includes/comm.involv.adoc

@@ -1,8 +1,10 @@
 === Community Involvement
 
-* Hosts and runs a Systems Operations podcast, https://sysadministrivia.com[Sysadministrivia^], for 6 years ongiong
+* Hosts and runs a Systems Operations podcast, https://sysadministrivia.com[Sysadministrivia^], for 6 years ongoing
 ** Maintains accompanying community of other IT professionals
 
 * Engineered, maintained NOC and designed firmware for a community/volunteer-driven city-wide WiFi project (Project.Phree) for 1 year (now defunct)
 
 * Have volunteered for/participated in and raised funds for the https://www.extra-life.org/[Extra Life] children's health charity in 2013, 2015, 2016, 2017, and 2020.
+
+* Have volunteed Systems Support for the https://tasgiving.org/[2020 TASGiving^] charity event (benefiting https://www.nami.org/Home[NAMI^])

includes/header.adoc

@@ -1,6 +1,9 @@
+
+[.center]
 ifeval::["{filetype}" == "pdf"]
 mailto:bts@square-r00t.net[bts@square-r00t.net,About your {ftypef}...] | +1 (504) 338-1513 | Lehigh Valley area, PA
 endif::[]
 ifeval::["{filetype}" != "pdf"]
 mailto:bts@square-r00t.net[bts@square-r00t.net,About your {ftypef}...] | +1 (504) 338-1513 | Lehigh Valley area, PA
-endif::[]
+endif::[]
+

includes/hobbies.adoc

@@ -1,7 +1,9 @@
 === Hobbies
 
+////
 [quote, Ralph Wiggum, The Simpsons (Season 4 Episode 15)]
 So... Do you like... stuff?
+////
 
 ifeval::["{ftype}" == "cv"]
 _A list of interests and hobbies (*outside* of technology) in no particular order, should it make sifting through {ftypef}s more amusing for you._

includes/skills.adoc

@@ -32,3 +32,6 @@ to see technical specifics.
 ** Root cause determination
 ** Future mitigation design
 * Incorporating best practices to ensure interoperability, safety/security, stability
+** Implementing RFC recommendations (e.g. `MUST` and `MAY` directives)
+** Seeking current advisement from upstream documentation and notices
+** Applying new security discoveries as applicable to already deployed projects

includes/values.adoc

@@ -1,17 +1,30 @@
 == Values
 
-In my professional environment, I value the following:
+In my professional environment, I value and demonstrate the following:
 
-* Security, safety, privacy (for both employees/coworkers and customers)
+=== "SSP" ===
-* Accurate and followed deadlines
+*Security*, *safety*, and *privacy*.
-* Quality first, quantity second, "quickness" third
+
-** Reduce/avoid technical debt
+These concepts are paramount for both employees/coworkers/clients and customers. By holding these concepts in mind during all stages of a project or product's lifecycle, I believe that other areas (flexibility, economic growth, etc.) become much more achievable.
-*** Deploy correctly the first time
+
-*** Extensive planning
+=== Timing ===
-*** Future-proofing
+*Deadlines* should be _accurate_ and _followed_. This allows for a smoother development, deployment, and consumer satisfaction level.
-** Separate Dev, Test/Staging, Production environments
+
-** Scalability
+When determining deadlines and when developing or deploying *quality* comes first, *quantity* second, and *"quickness"* third. Efficiency is not efficient if it creates more work down the road at the cost of speed.
-* Stability and availability over (individual) uptime
+
-** Balancing
+=== Do it Right, Do it Once ===
-** Failover
+By following a procedure and policy that allow for *testing* during development and deployment and by implementing *automation* into that cycle, it allows for *reducing/avoiding technical debt* by paving the road for:
-* Clear communication with customers when affected
+
+* Deploying correctly the first time
+* Extensive planning
+* Future-proofing
+
+This is accomplished by a strong focus on:
+
+* *Separate* _Dev_, _Test/Staging_, and _Production_ environments
+** *Scalability*
+
+=== Stability ===
+In the modern technological world of failover and redundancy, *stability* and *availability* of a service hold priority over individual machines' uptime.
+
+Because of this, I value *balancing* load/resources, deploying *strong failover procedures*, clear *priority levels/SLA* and *clear communication with consumers* when affected.

render.sh

@@ -2,20 +2,16 @@
 
 if [[ $(id -u) == 0 ]];
 then
-	# asciidoctor -B /opt/dev/resume -D /tmp/resume -n /opt/dev/resume/cv.adoc
+	DESTDIR=/srv/http/resume
-	#asciidoctor -D /srv/http/resume -n cv.adoc
-	#asciidoctor -D /srv/http/resume -n resume.adoc
-	asciidoctor -D /srv/http/resume -o cv.html -n cv.adoc
-	asciidoctor -D /srv/http/resume -o resume.html -n resume.adoc
-	
-	asciidoctor-pdf -a filetype=pdf -D /srv/http/resume/pdf -n -d article cv.adoc
-	asciidoctor-pdf -a filetype=pdf -D /srv/http/resume/pdf -n -d article resume.adoc
 else
-	#asciidoctor -D /tmp/cv.html -n cv.adoc
+	DESTDIR=/tmp/resume
-	#asciidoctor -D /tmp/resume.html -n resume.adoc
-	asciidoctor -D /tmp/resume -o cv.html -n cv.adoc
-	asciidoctor -D /tmp/resume -n -o resume.html resume.adoc
-	
-	asciidoctor-pdf -a filetype=pdf -D /tmp -n -d article cv.adoc
-	asciidoctor-pdf -a filetype=pdf -D /tmp -n -d article resume.adoc
 fi
+
+# Use -n to number sections.
+
+asciidoctor -D ${DESTDIR} -o cv.html cv.adoc
+asciidoctor -D ${DESTDIR} -n -o resume.html resume.adoc
+
+#asciidoctor-pdf -a filetype=pdf -D ${DESTDIR} -d article cv.adoc
+asciidoctor-pdf -a filetype=pdf -D ${DESTDIR} cv.adoc
+asciidoctor-pdf -a filetype=pdf -D ${DESTDIR} -d article resume.adoc

resume.adoc

@@ -11,9 +11,11 @@ Last updated {localdatetime}
 :imagesdir: images
 :sectlinks:
 ifeval::["{doctype}" != "article"]
+ifeval::["{filetype}" != "pdf"]
 :toc: preamble
 :toc2: left
 endif::[]
+endif::[]
 :idprefix:
 :toclevels: 7
 :source-highlighter: highlightjs