<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Projects |</title><link>https://isaacneibaur.com/projects/</link><atom:link href="https://isaacneibaur.com/projects/index.xml" rel="self" type="application/rss+xml"/><description>Projects</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Sun, 19 May 2024 00:00:00 +0000</lastBuildDate><image><url>https://isaacneibaur.com/media/icon_hu_da05098ef60dc2e7.png</url><title>Projects</title><link>https://isaacneibaur.com/projects/</link></image><item><title>Cloudflare Governance &amp; Remediation Platform</title><link>https://isaacneibaur.com/projects/cloudflare-governance-platform/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://isaacneibaur.com/projects/cloudflare-governance-platform/</guid><description>&lt;p&gt;Cloud automation project for auditing Cloudflare domain security posture and managing repeatable governance workflows through code.&lt;/p&gt;
&lt;p&gt;The system combines Python, Terraform, GitHub Actions, and the Cloudflare API to check configuration state, validate policy expectations, and optionally remediate drift. The work emphasizes Infrastructure as Code, scheduled audits, secure secret handling, automated validation, and repository governance patterns that support reliable cloud operations.&lt;/p&gt;
&lt;div class="project-action-row"&gt;
&lt;a class="project-action" href="https://github.com/neibaur/cloudflare_IaC" target="_blank" rel="noopener"&gt;View GitHub Repository&lt;/a&gt;
&lt;/div&gt;
&lt;div class="project-tech-list"&gt;
&lt;span&gt;Python&lt;/span&gt;
&lt;span&gt;Terraform&lt;/span&gt;
&lt;span&gt;GitHub Actions&lt;/span&gt;
&lt;span&gt;Cloudflare API&lt;/span&gt;
&lt;span&gt;Infrastructure as Code&lt;/span&gt;
&lt;span&gt;DevSecOps&lt;/span&gt;
&lt;span&gt;Secret Management&lt;/span&gt;
&lt;span&gt;Scheduled Audits&lt;/span&gt;
&lt;/div&gt;
&lt;p&gt;Current focus areas:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Cloudflare security posture audits using Python and the Cloudflare API&lt;/li&gt;
&lt;li&gt;Terraform workflows for repeatable Infrastructure as Code validation&lt;/li&gt;
&lt;li&gt;GitHub Actions pipelines for scheduled audits and CI checks&lt;/li&gt;
&lt;li&gt;Secure secret handling for automation workflows&lt;/li&gt;
&lt;li&gt;Optional remediation workflows for configuration drift correction&lt;/li&gt;
&lt;li&gt;DevSecOps practices including Dependabot, CodeQL, branch protection, linting, and test checks&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Design notes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Audit workflows run automatically, while remediation remains intentionally gated.&lt;/li&gt;
&lt;li&gt;Terraform and Python separate declarative infrastructure validation from API-driven audit logic.&lt;/li&gt;
&lt;li&gt;Secrets and real configuration inputs stay out of mock validation paths.&lt;/li&gt;
&lt;li&gt;CodeQL, Dependabot, Gitleaks, and branch protection support repository governance and operational reliability.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>100DayDash Engineering Blog</title><link>https://isaacneibaur.com/projects/100daydash-engineering-blog/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://isaacneibaur.com/projects/100daydash-engineering-blog/</guid><description>&lt;p&gt;Public engineering documentation project showing how cloud automation, DevSecOps, data platforms, and dashboard systems evolve through iterative delivery.&lt;/p&gt;
&lt;p&gt;100DayDash documents independent engineering work across cloud infrastructure, CI/CD, DevSecOps, observability, API-driven data workflows, and dashboard development. The site also serves as a public record of design decisions, implementation tradeoffs, and repeatable delivery patterns.&lt;/p&gt;
&lt;div class="project-action-row"&gt;
&lt;a class="project-action" href="https://github.com/neibaur/100daydash.blog" target="_blank" rel="noopener"&gt;View GitHub Repository&lt;/a&gt;
&lt;/div&gt;
&lt;div class="project-tech-list"&gt;
&lt;span&gt;Astro&lt;/span&gt;
&lt;span&gt;Hugo&lt;/span&gt;
&lt;span&gt;Python&lt;/span&gt;
&lt;span&gt;GitHub Actions&lt;/span&gt;
&lt;span&gt;Cloudflare&lt;/span&gt;
&lt;span&gt;DevSecOps&lt;/span&gt;
&lt;span&gt;Technical Writing&lt;/span&gt;
&lt;span&gt;Analytics Engineering&lt;/span&gt;
&lt;/div&gt;
&lt;p&gt;Current focus areas:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Public documentation of engineering decisions, tradeoffs, and implementation lessons&lt;/li&gt;
&lt;li&gt;Cloud automation and Infrastructure as Code project notes&lt;/li&gt;
&lt;li&gt;DevSecOps workflow documentation for CI/CD, repository governance, and secret scanning&lt;/li&gt;
&lt;li&gt;Dashboard engineering with Power BI, Looker Studio, Hugo, Astro, and Python-based visualization&lt;/li&gt;
&lt;li&gt;Data platform development using APIs, PostgreSQL/Supabase patterns, and modeled analytical outputs&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Design notes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Posts emphasize design decisions and operational tradeoffs, not only finished screenshots.&lt;/li&gt;
&lt;li&gt;The project documents reusable delivery patterns across cloud automation, data engineering, and dashboard development.&lt;/li&gt;
&lt;li&gt;The blog acts as a public accountability system for sustained engineering practice.&lt;/li&gt;
&lt;li&gt;The site is also a working example of static-site delivery, CI/CD, and content governance.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>NHTSA Vehicle Data Platform</title><link>https://isaacneibaur.com/projects/nhtsa-recall-intelligence/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://isaacneibaur.com/projects/nhtsa-recall-intelligence/</guid><description>&lt;p&gt;API-driven vehicle safety data project focused on turning NHTSA public recall data into repeatable, dashboard-ready analytical outputs.&lt;/p&gt;
&lt;p&gt;The project is scoped around practical data engineering work: ingesting recall records from the public API, shaping them into medallion-style analytical tables, and preparing relational outputs for trend, manufacturer, component, and campaign-level reporting.&lt;/p&gt;
&lt;div class="project-action-row"&gt;
&lt;a class="project-action" href="https://github.com/neibaur/portfolio-NHTSA" target="_blank" rel="noopener"&gt;View GitHub Repository&lt;/a&gt;
&lt;/div&gt;
&lt;div class="project-tech-list"&gt;
&lt;span&gt;Python&lt;/span&gt;
&lt;span&gt;NHTSA API&lt;/span&gt;
&lt;span&gt;PostgreSQL&lt;/span&gt;
&lt;span&gt;Supabase&lt;/span&gt;
&lt;span&gt;ETL&lt;/span&gt;
&lt;span&gt;Medallion Modeling&lt;/span&gt;
&lt;span&gt;Power BI&lt;/span&gt;
&lt;span&gt;Data Engineering&lt;/span&gt;
&lt;/div&gt;
&lt;p&gt;Current focus areas:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;NHTSA public recall API ingestion&lt;/li&gt;
&lt;li&gt;Repeatable cleaning and normalization of recall records&lt;/li&gt;
&lt;li&gt;Medallion-style modeling for analytical datasets&lt;/li&gt;
&lt;li&gt;PostgreSQL/Supabase-ready relational structures&lt;/li&gt;
&lt;li&gt;Dashboard-ready outputs for recall, manufacturer, component, and campaign analysis&lt;/li&gt;
&lt;li&gt;Documentation of data design decisions during the 100DayDash challenge&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Design notes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;API ingestion and transformation are separated so raw records can be preserved while modeled tables evolve.&lt;/li&gt;
&lt;li&gt;Medallion-style layers provide a clear path from raw recall data to curated analytical outputs.&lt;/li&gt;
&lt;li&gt;Relational structures support dashboard tools without locking the project to one BI platform.&lt;/li&gt;
&lt;li&gt;Documentation captures tradeoffs and implementation decisions as the project matures.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>