Merge branch 'master' of github.com:corrode/corrode.github.io

Author: mre

.github/workflows/deploy.yml

@@ -3,10 +3,17 @@ name: Zola
 on:
   push:
     branches:
-      - master 
+      - master
   pull_request:
   workflow_dispatch:
 
+# Serialize deploys so concurrent runs can't race when force-pushing to
+# gh-pages, which can leave the GitHub Pages deployment wedged. Queue rather
+# than cancel, so a half-finished push is never interrupted.
+concurrency:
+  group: pages-${{ github.ref }}
+  cancel-in-progress: false
+
 jobs:
   build:
     name: Build
@@ -20,7 +27,7 @@ jobs:
           BUILD_DIR: .
           BUILD_ONLY: true
           BUILD_FLAGS: --drafts
-          
+
   deploy:
     name: Deploy
     runs-on: ubuntu-latest

content/blog/bugs-rust-wont-catch/index.md

@@ -376,10 +376,4 @@ The type system can encode many things, but it cannot encode conditions outside
 
 Idiomatic Rust, then, is not just code that the borrow checker accepts or that `clippy` leaves alone. It is code whose types, names, and control flow tell the *truth* about the system they run in. And that truth is sometimes ugly. It could mean using file descriptors instead of paths, `OsStr` instead of `String`, [`?` instead of `unwrap`](/blog/pitfalls-of-safe-rust/), and bug-for-bug compatibility over clean semantics. None of it is as pretty as the version you would write on a whiteboard. But it is more honest.
 
-{% info(title="Need Help Hardening Your Rust Codebase?", icon="crab") %}
-
-Is your team shipping Rust into production and want to make sure you're not falling into the same traps?
-I offer Rust consulting services, from code reviews and security-focused audits to training your team on the patterns that the compiler won't enforce for you.
-[Get in touch](/#contact) to learn more.
-
-{% end %}
+{{ next_steps(context="Shipping Rust to production and want to make sure you're not falling into the traps the compiler won't catch?") }}

content/blog/cpp-rust-interop/index.md

@@ -103,13 +103,7 @@ Here are some key takeaways from Tyler's experiences with Rust and C++:
 
 As Tyler's experiences illustrate, the benefits of Rust often become most apparent in the "day two operations" of software development – in code reviews, refactoring, and managing complexity.
 
-{% info(title="Make the most of Rust", icon="crab") %}
-
-Is your company considering to migrate from C++ to Rust? 
-I offer consulting services to get you up to speed with your Rust projects, from training your team to code reviews and architecture consulting. 
-Check out my [services page](/services) to learn more.
-
-{% end %}
+{{ next_steps(context="Moving a C++ codebase to Rust? Getting the interop boundaries right is exactly the kind of decision that pays off with a second pair of eyes.") }}
 
 ## Recommended Reading
 

content/blog/hiring-rust-engineers/index.md

@@ -141,11 +141,5 @@ work with your hiring manager to help them understand how to hire more Rust devs
 
 Good luck with your Rust hiring process!
 
-{% info(title="Is your company adopting Rust?", icon="crab") %}
-
-Let me help you make the most of Rust.
-I offer consulting services to get you up to speed with your Rust projects, from training your team to code reviews and architecture consulting. 
-Check out my [services page](/services) to learn more.
-
-{% end %}
+{{ next_steps(context="Building out a Rust team and want to set them up for long-term success?") }}
 

content/blog/long-term-rust-maintenance/index.md

@@ -577,11 +577,7 @@ tooling, and active community.
 By following the principles outlined in this post, you can
 ensure that your codebase remains robust and maintainable for years to come.
 
-{% info(title="Supercharge Your Rust Adoption", icon="radio") %}
-
 If you want to learn from top companies that have successfully adopted Rust,
-consider subscribing to the [Rust In Production Podcast](/podcast).
-
-In case your company is considering to adopt Rust for a new project, feel free to reach out for a [consultation](/#contact).
+consider subscribing to the [Rust in Production Podcast](/podcast).
 
-{% end %}
+{{ next_steps(context="Planning Rust for the long haul and want a codebase that stays maintainable for years?") }}

content/blog/memory-safety/index.md

@@ -55,14 +55,6 @@ This is a **global, bipartisan, cross-sector consensus** that memory-unsafe code
 
 The direction is clear. The question is not _whether_ your organization will need to address this, it's _when_, and whether you'll do so on your own terms or under external pressure.
 
-{% info(title="Where Does Your Organization Stand?", icon="warning") %}
-
-If your software touches critical infrastructure, handles sensitive data, or ships into regulated markets, the regulatory direction above applies to you. Most organizations I work with underestimate how long it takes to build internal Rust expertise and draft a credible memory safety roadmap.
-
-I help companies close that gap, typically saving months of trial and error. **[Book a free assessment call](/#contact)** and let's figure out your exposure before deadlines set the pace.
-
-{% end %}
-
 ## Memory Safety Vulnerabilities Are Everywhere
 
 Before we talk about regulation, let's talk about the problem.
@@ -253,48 +245,13 @@ At a minimum:
 4. Interim mitigations for code that won't be migrated soon (compiler hardening, fuzzing, static analysis).
 5. A timeline with milestones showing a credible, prioritized reduction of memory safety vulnerabilities.
 
-This is exactly the kind of work I do with my clients at [corrode](/services/). We've helped organizations across industries, from 
-cloud infrastructure to embedded devices to backend services, develop practical Rust adoption strategies (see our [case studies](/learn/case-studies/) for real-world examples).
-
 (For a complete guide on the organizational side, see our [Rust Business Adoption Checklist](/blog/successful-rust-business-adoption-checklist/).)
 
 ## You Don't Have to Do This Alone
 
-Making this transition on your own, on top of an already overwhelming workload, is hard.
-But here's the good news: **you don't need to figure this out from scratch**.
-
-The Rust ecosystem is mature, the tooling is excellent, and there is a growing body of industry experience to draw from. What most organizations lack is not motivation. It's **guidance**.
-
-That's where I come in.
-
-At [corrode](/) I provide Rust consulting and training specifically designed for organizations navigating this transition. I've helped teams:
-
-- Evaluate whether Rust is the right fit for their specific use case.
-- Build memory safety roadmaps aligned with CISA and EU CRA requirements.
-- Train existing C/C++ developers to become productive in Rust.
-- Architect interoperability layers between legacy C/C++ and new Rust code.
-- Review and audit Rust codebases for production readiness.
-- Hire and grow Rust teams (see our guide on [hiring Rust engineers](/blog/hiring-rust-engineers/)).
-
-I've also spent years documenting real-world Rust adoption through the [**Rust in Production podcast**](/podcast/), where companies like [Microsoft](/podcast/s04e01-microsoft/), [Cloudflare](/podcast/s05e03-cloudflare/), [1Password](/podcast/s04e06-1password/), [Volvo](/podcast/s03e08-volvo/), and [many others](/podcast/) share their experiences.
-
-I write about the practicalities of long-term Rust adoption on this blog, from [flattening the learning curve](/blog/flattening-rusts-learning-curve/) to [long-term maintenance strategies](/blog/long-term-rust-maintenance/) to understanding [Rust for foundational software](/blog/foundational-software/).
+Making this transition on your own, on top of an already overwhelming workload, is hard. But the Rust ecosystem is mature, the tooling is excellent, and there is a growing body of industry experience to draw from.
 
-## The Cost of Inaction Far Exceeds the Cost of Action
-
-Let me put it in business terms.
-
-Engaging a Rust consultant is an **insurance** policy for your organization.
-The cost of a consulting engagement is a rounding error compared to:
-
-- A single critical CVE in production ($150,000+ per Microsoft's estimate).
-- A regulatory non-compliance penalty under the EU Cyber Resilience Act.
-- An emergency scramble to produce a memory safety roadmap when your government customer asks for one.
-- The reputational damage of a headline-grabbing breach traced to a buffer overflow in 2026.
-
-**Starting now means you control the timeline, the budget, and the scope.** You choose which components to migrate first. You train your team at a sustainable pace. You build institutional knowledge before you _need_ it.
-
-Waiting means someone else, a regulator, a customer, a competitor, dictates the terms.
+I've documented real-world Rust adoption through the [**Rust in Production podcast**](/podcast/), where companies like [Microsoft](/podcast/s04e01-microsoft/), [Cloudflare](/podcast/s05e03-cloudflare/), [1Password](/podcast/s04e06-1password/), [Volvo](/podcast/s03e08-volvo/), and [many others](/podcast/) share their experiences. I also write about long-term Rust adoption on this blog, from [flattening the learning curve](/blog/flattening-rusts-learning-curve/) to [long-term maintenance strategies](/blog/long-term-rust-maintenance/) to [Rust for foundational software](/blog/foundational-software/).
 
 ## Next Steps
 
@@ -309,17 +266,7 @@ Here's what I recommend:
 
 I'd love to help you with any or all of the above.
 
-{% info(title="Let's Talk About Your Memory Safety Strategy", icon="crab") %}
-
-If you're evaluating Rust or need to build a memory safety roadmap for compliance, [reach out for a free initial consultation](/#contact).
-
-I work with organizations of all sizes, from startups to Fortune 500 companies, to make Rust adoption practical, sustainable, and aligned with regulatory requirements.
-
-Let's make sure your organization is ahead of the curve, not behind it.
-
-**[Get in touch →](/#contact)**
-
-{% end %}
+{{ next_steps(context="Evaluating Rust or building a memory safety roadmap for compliance?") }}
 
 ## Frequently Asked Questions
 

content/blog/pitfalls-of-safe-rust/index.md

@@ -914,10 +914,4 @@ That's why testing, linting, and fuzzing are still important in Rust.
 For maximum robustness, combine Rust's safety guarantees with strict checks and
 strong verification methods.
 
-{% info(title="Let an Expert Review Your Rust Code", icon="crab") %}
-
-I hope you found this article helpful!
-If you want to take your Rust code to the next level, consider a code review by an expert.
-I offer code reviews for Rust projects of all sizes. [Get in touch](/services/) to learn more.
-
-{% end %}
+{{ next_steps(context="Want a second pair of expert eyes on your Rust code before it ships?") }}

content/blog/rust-learning-resources-2026/index.md

@@ -142,12 +142,4 @@ All the material is open source and free. You can browse the [full workshop cata
 You can go through the material on your own to see if it fits your needs.
 Once you're ready, feel free to reach out about tailoring the content for you and your team.
 
-{% info(title="Speed Up Your Learning Process", icon="crab") %}
-
-Is your company considering a switch to Rust? 
-
-Rust is known for its steep learning curve, but with the right resources and guidance, you can become proficient in a matter of weeks. I offer hands-on workshops and training for teams and individuals who want to accelerate their learning process. 
-
-Check out my [services page](/services) or [send me an email](mailto:hi@corrode.dev?subject=Rust%20Workshops) to learn more.
-
-{% end %}
+{{ next_steps(context="Want to accelerate past Rust's learning curve with hands-on guidance?") }}

content/blog/rust-prevents-data-races-not-race-conditions/index.md

@@ -357,9 +357,4 @@ Rust holds an enormous amount for you, and what remains is the part that lives i
 
 If you want to go deeper on the concurrency side of this, read [Rust Atomics and Locks](https://mara.nl/atomics/) by Mara Bos. It's free online.
 
-{% info(title="Want to get concurrency right in your Rust codebase?", icon="crab") %}
-
-I offer Rust consulting, from code reviews and audits to training your team on the patterns the compiler won't enforce for you, including the concurrency traps in this post.
-[Get in touch](/#contact) to learn more.
-
-{% end %}
+{{ next_steps(context="Want to get concurrency right in your Rust codebase, including the traps covered in this post?") }}

content/blog/successful-rust-business-adoption-checklist/index.md

@@ -451,9 +451,4 @@ By acknowledging the challenges and following these strategies, you can ensure a
 
 Check out our ['Rust in Production' podcast](/podcast/) for insights from industry experts on how their teams successfully adopted Rust in production. 
 
-{% info(title="Need Help with Your Rust Project?") %}
-
-If you're considering adopting Rust for your next project, I can help you get started.
-[Reach out for a free consultation](/#contact) if you need help with your Rust project. I'm happy to help you get the most out of Rust and guide you through the process.
-
-{% end %}
+{{ next_steps(context="Considering Rust for your next project and want guidance from someone who's done it before?") }}