fix

.gitignore

@@ -1,3 +1,4 @@
 public/
 resources/
 pages.git/
+.hugo_build.lock

assets/sass/overrides.scss

@@ -1,6 +1,8 @@
-$primary-color: #ABC9E3;
+//$primary-color: #ABC9E3;
+$primary-color: #115c9e;
 $hover-color: #5E7191;
 
+
 html, body {
 	border-top-color: $primary-color;
 }
@@ -72,3 +74,58 @@ h5 {
   clear: both;
   display: table;
 }
+
+/* Projects page styling */
+.project-card {
+  background: #fff;
+  border: 1px solid #e8e8e8;
+  border-radius: 8px;
+  padding: 1.5rem;
+  height: 100%;
+  transition: box-shadow 0.3s ease, transform 0.2s ease;
+  display: flex;
+  flex-direction: column;
+}
+
+.project-card:hover {
+  box-shadow: 0 4px 12px rgba(0,0,0,0.1);
+  transform: translateY(-2px);
+}
+
+.project-header {
+  display: flex;
+  align-items: center;
+  margin-bottom: 1rem;
+}
+
+.project-icon {
+  font-size: 1.8rem;
+  color: $primary-color;
+  margin-right: 1rem;
+  min-width: 2rem;
+  text-align: center;
+}
+
+.project-title {
+  margin: 0;
+  flex: 1;
+}
+
+.project-title a {
+  color: $primary-color;
+  text-decoration: none;
+  font-weight: 600;
+}
+
+.project-title a:hover {
+  color: $hover-color;
+  text-decoration: none;
+}
+
+.project-description {
+  color: #666;
+  line-height: 1.6;
+  margin: 0;
+  flex: 1;
+  text-align: left;
+}

content/posts/joining-resolvex-technical-advisor-crisis-response.md

@@ -0,0 +1,57 @@
+---
+title: 'Joining ResolveX as a Technical Advisor: Infrastructure and Crisis Response'
+description: "I've joined ResolveX as a technical advisor to help scale their crisis response software. Working on infrastructure, security, and scaling decisions for 988 suicide prevention lines and mental health crisis centers."
+date: 2025-08-08T10:17:20-04:00
+draft: false
+categories: ['consulting', 'social-impact']
+tags: ['crisis-response', 'mental-health', 'infrastructure', 'advisory', 'resolvex', '988']
+---
+
+I'm excited to share that I've joined [ResolveX](https://resolvex.com) as a technical advisor. ResolveX
+builds software and data solutions for crisis call centers—988 suicide
+prevention lines, domestic violence hotlines, and other critical mental health
+resources.
+
+## Why This Matters
+
+Mental health crisis response has significant gaps that technology can help address. ResolveX builds tools to make crisis counselors more effective and help researchers understand patterns that could prevent crises.
+
+They serve 988 operators—resource-constrained nonprofits handling life-or-death situations. The technical requirements are unique: rock-solid reliability, security for sensitive mental health data, and cost-effectiveness for organizations that measure impact in lives saved.
+
+## The Technical Challenge
+
+ResolveX is hitting the classic startup infrastructure inflection point—scaling from scrappy solutions to supporting a primary mental health data warehouse without over-engineering.
+
+My role: provide neutral perspective on infrastructure, security, and scaling decisions. Lightweight advisory rather than hands-on implementation, helping spot issues early and suggest practical solutions within their budget and mission.
+
+## What I'm Doing
+
+The immediate priorities are pretty straightforward:
+
+- **Infrastructure & Security Audit**: Review current hosting, architecture, and configurations. Light security testing and access review.
+
+- **Ongoing Advisory**: Lightweight consultation (~5 hours/week) for feedback and neutral oversight on scaling decisions.
+
+- **Content Collaboration**: Educational content that benefits both crisis response and broader tech communities.
+
+## The Bigger Picture
+
+This isn't just consulting work—I've been getting into emergency response volunteering (CERT, amateur radio) and care deeply about how we handle mental health crises. ResolveX has potential to become an open-source-friendly, public-impact organization changing mental health data collection and analysis.
+
+## Technical Philosophy
+
+The constraints make this engaging: high reliability and security requirements, minimal budget, maximum impact. Every architectural decision must justify real value to crisis counselors and those they help.
+
+This requires "appropriate technology"—sophisticated enough for requirements but simple enough to maintain and afford. Systems engineering with purpose, not hope-based engineering.
+
+## Looking Forward
+
+I'll write follow-ups about specific technical challenges as this develops. Infrastructure engineering for social impact deserves more attention.
+
+If you're working on mission-driven technology or considering how your skills could have broader social impact, reach out. **There's more of this work that needs doing.**
+
+---
+
+If you're interested in similar advisory or consulting work, you can reach me
+through [my consulting practice](https://shrugpw.com) or find me on the usual places around the
+internet.

content/projects/_index.md

@@ -3,4 +3,5 @@ categories: ["projects"]
 date: "2016-10-02T22:55:05-04:00"
 tags: ["projects"]
 title: "Projects"
+layout: "projects"
 ---

data/projects.yml

@@ -1,6 +1,30 @@
 name: Projects
 source:
-  - icon: fa fa-github
+  - icon: fa-solid fa-building
+    name: Rocky Enterprise Software Foundation
+    description: Board member for the non-profit foundation behind Rocky Linux. Focus on strategic governance, financial oversight, and advancing the mission of community-driven enterprise Linux distribution development.
+    url: https://rockylinux.org/about
+  - icon: fa-brands fa-github
     name: Rocky Linux
-    description: All the infrastructure for Rocky Linux, from soup to nuts. Work with a team of professionals to architect, design, and implement secure systems and proceudres to write Infrastructure as Code to provide systems for the various teams within the Rocky Enterprise Software Foundation, especially Rocky Linux as it gets off the ground. Also work closely with Release Engineering on building next generation Build Automation pipeline tools and ensuring reliability and security in the supply chain.
+    description: Infrastructure architect and core team member for Rocky Linux. Built and maintain all infrastructure from bare metal to cloud services, including CI/CD pipelines, build systems, and supply chain security. Work closely with Release Engineering on next-generation build automation and ensuring security throughout the software supply chain.
     url: https://github.com/rocky-linux/
+  - icon: fa-solid fa-code-branch
+    name: OpenELA
+    description: Technical Steering Committee member for OpenELA, the Open Enterprise Linux Association. Help guide technical strategy and governance for collaborative development of enterprise Linux distributions, focusing on open source supply chain transparency and community collaboration.
+    url: https://openela.org/
+  - icon: fa-solid fa-heart
+    name: ResolveX
+    description: Board member and technical advisor for ResolveX, building software and data solutions for crisis call centers including 988 suicide prevention lines and mental health resources. Provide strategic guidance on scaling infrastructure and technology decisions for mission-critical systems.
+    url: https://resolvex.com/
+  - icon: fa-solid fa-handshake
+    name: Shrug PW Consulting
+    description: Founder and Principal Consultant providing infrastructure architecture, DevOps automation, and technical advisory services. Specialize in scaling systems for mission-driven organizations, supply chain security, and building reliable infrastructure on constrained budgets.
+    url: https://shrugpw.com/
+  - icon: fa-brands fa-fedora
+    name: Fedora Project
+    description: Active contributor to Fedora RISC-V SIG and Community Operations (CommOps). Work on infrastructure, packaging ecosystem, build systems, and community tooling. Focus on RISC-V architecture support and community infrastructure reliability.
+    url: https://fedoraproject.org/
+  - icon: fa-solid fa-cloud
+    name: OpenStack
+    description: Core reviewer for OpenStack-Ansible and contributor to OpenStack-Kolla projects. Support OpenStack integration with Rocky Linux and work in CentOS NFV and Cloud SIGs. Focus on deployment automation, bare metal provisioning, and enterprise Linux integration.
+    url: https://openstack.org/

hugo.toml

@@ -23,9 +23,11 @@ theme = "hugo-sustain"
 
 [params.social]
   Github        = "NeilHanlon"
-  Email         = "neil@shrug.pw.com"
-  Twitter       = "NeilHanlon"
+  Email         = "neil@shrug.pw"
+  Bluesky       = "@shrug.pw"
   LinkedIn      = "hanlonneil"
+  Signal        = "hScowCEn-H1GKkCrare0m_xOEPqTWxt51pW9SI2bU5TlXrMW9QFD6qHBLqG1jDq9"
+  Keybase       = "nhanlon"
   #Stackoverflow = "username"
   #Medium        = "hanlon.neil"
   Instagram     = "noellathekitty"

layouts/_default/projects.html

@@ -0,0 +1,25 @@
+{{ define "main" }}
+  <!-- Header -->
+  {{ partial "header" . }}
+
+  <div class="container">
+    <section id="projects">
+      <h4 class="my-5">{{ .Site.Data.projects.name }}</h4>
+      <div class="row">
+        {{ range $el := .Site.Data.projects.source }}
+          <div class="col-md-6 mb-4">
+            <div class="project-card">
+              <div class="project-header">
+                <i class="{{ .icon }} project-icon"></i>
+                <h5 class="project-title">
+                  <a href="{{ .url }}" target="_blank">{{ $el.name }}</a>
+                </h5>
+              </div>
+              <p class="project-description">{{ $el.description }}</p>
+            </div>
+          </div>
+        {{ end }}
+      </div>
+    </section>
+  </div>
+{{ end }}

themes/hugo-sustain

@@ -1 +1 @@
-Subproject commit 9aeb8712e1fede18ef41b7d02540249a3dbe51a7
+Subproject commit 4331b32265105a584dc387a349e92d3eabca7606