sscoble/brand-site
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Backfill blog entries: add strip-mining-signs, three-questions-mentoring, the-soil-beneath-the-code; link all cards in blog listing
Some checks failed
Build and Deploy to Storj / build-and-deploy (push) Failing after 6s
Details

Browse source
This commit is contained in:
Scott Scoble 2026-05-07 12:50:40 -07:00
parent ffd3c70a20
commit ed5cd801b4
5 changed files with 850 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

54
src/pages/blog.astro
View file

@ -86,36 +86,42 @@ import BaseLayout from '../layouts/BaseLayout.astro';
</article> </article>
<article class="post-card"> <article class="post-card">
<div class="post-meta"> <a href="/blog/three-questions-mentoring" class="post-link">
<span class="post-date">April 28, 2026</span> <div class="post-meta">
<span class="post-tag">Leadership</span> <span class="post-date">April 28, 2026</span>
</div> <span class="post-tag">Leadership</span>
<h2>Three Questions That Changed How I Mentor</h2> </div>
<p class="post-excerpt"> <h2>Three Questions That Changed How I Mentor</h2>
The simple mentoring framework that actually gets used - three questions that unlock real growth. <p class="post-excerpt">
</p> The simple mentoring framework that actually gets used - three questions that unlock real growth.
</p>
</a>
</article> </article>
<article class="post-card"> <article class="post-card">
<div class="post-meta"> <a href="/blog/strip-mining-signs" class="post-link">
<span class="post-date">April 28, 2026</span> <div class="post-meta">
<span class="post-tag">Teams</span> <span class="post-date">April 28, 2026</span>
</div> <span class="post-tag">Teams</span>
<h2>Three Signs Your Team Is Being Strip-Mined</h2> </div>
<p class="post-excerpt"> <h2>Three Signs Your Team Is Being Strip-Mined</h2>
The mindset shift that separates thriving teams from burned-out ones - cultivation over extraction. <p class="post-excerpt">
</p> The mindset shift that separates thriving teams from burned-out ones - cultivation over extraction.
</p>
</a>
</article> </article>
<article class="post-card"> <article class="post-card">
<div class="post-meta"> <a href="/blog/the-soil-beneath-the-code" class="post-link">
<span class="post-date">April 28, 2026</span> <div class="post-meta">
<span class="post-tag">Engineering</span> <span class="post-date">April 28, 2026</span>
</div> <span class="post-tag">Engineering</span>
<h2>The Soil Beneath The Code</h2> </div>
<p class="post-excerpt"> <h2>The Soil Beneath The Code</h2>
A three-layer framework for understanding what makes engineering organizations healthy - or not. <p class="post-excerpt">
</p> A three-layer framework for understanding what makes engineering organizations healthy - or not.
</p>
</a>
</article> </article>
</div> </div>

185
src/pages/blog/strip-mining-signs.astro Normal file
View file

@ -0,0 +1,185 @@
---
import BaseLayout from '../../layouts/BaseLayout.astro';
---
<BaseLayout
title="Three Signs Your Team Is Being Strip-Mined — Scott Scoble"
description="The mindset shift that separates thriving teams from burned-out ones — cultivation over extraction."
ogType="article"
canonicalUrl="/blog/strip-mining-signs"
pageType="blog"
>
<article class="article">
<header class="article-header">
<div class="article-meta">
<span class="article-date">May 5, 2026</span>
<span class="article-tag">Teams</span>
</div>
<h1>Three Signs Your Team Is Being Strip-Mined</h1>
<p class="article-subtitle">
The mindset shift that separates thriving teams from burned-out ones — cultivation over extraction.
</p>
</header>
<div class="article-body">
<p>I first heard the term "strip-mining" applied to teams from an engineering director at a mid-size fintech company. She'd just lost three senior engineers in two months. When I asked what happened, she didn't talk about compensation or competing offers. She said: "We were strip-mining them. We just didn't call it that."</p>
<p>Strip-mining in software isn't about tools or processes. It's about a mindset: extract maximum value from each person, measure throughput, and replace when depleted. It works until it doesn't — and when it breaks, it breaks fast.</p>
<h2>Sign 1: Velocity Is Up, Satisfaction Is Down</h2>
<p>This is the canary in the coal mine. When your sprint velocity charts keep climbing but your team's engagement is flat or falling, you're not becoming more efficient. You're extracting harder.</p>
<p>The pattern is familiar: same team, more output, less joy. Engineers who used to debate architecture now just close tickets. Standups that used to surface real problems now produce status updates. The work is getting done, but nobody cares about it anymore.</p>
<p>If your metrics are up and your people are down, you're not optimizing. You're extracting.</p>
<h2>Sign 2: Knowledge Is Concentrated, Not Distributed</h2>
<p>Healthy teams spread knowledge. Strip-mined teams hoard it — not because people are selfish, but because there's no time or incentive to teach. Senior engineers become bottlenecks not because they want to, but because nobody else was given the space to learn.</p>
<p>Ask yourself: when was the last time someone on your team learned something new because they had time, not because they were forced? If the answer is measured in quarters, not weeks, your soil is depleted.</p>
<h2>Sign 3: Departures Cluster Around the Same Moment</h2>
<p>In strip-mined teams, attrition doesn't follow a normal distribution. It clusters. Three people leave in six weeks. Then nothing for a year. Then four more.</p>
<p>Why? Because teams talk. When one person decides they've had enough, they tell the others. The decision to leave becomes contagious — not because people are followers, but because the conditions that pushed the first person out are still there. Everyone else was just waiting to see if it was them or the system.</p>
<h2>The Cultivation Alternative</h2>
<p>Cultivation isn't the opposite of productivity. It's the opposite of extraction. Cultivated teams ship more over time because they get stronger, not because they get squeezed harder.</p>
<p>The shift from extraction to cultivation is simple to describe and hard to do: invest in your people like you invest in your infrastructure. Not with perks and team-building. With time, autonomy, and real ownership over meaningful work.</p>
<p><strong>The test:</strong> Would your best engineer be a better engineer in six months if they stayed? If you can't answer yes with confidence, you're cultivating by accident, not by design.</p>
<p><a href="/consulting">Learn about the Soil Assessment →</a></p>
</div>
<footer class="article-footer">
<div class="article-cta">
<p>Enjoyed this? <a href="/blog">Read more articles</a> on AI, leadership, and the human side of technology.</p>
<p>Ready to bring this thinking to your team? <a href="/contact">Let's talk.</a></p>
</div>
</footer>
</article>
</BaseLayout>
<style>
.article {
padding: 8rem 2rem 6rem;
background: var(--color-cream);
}
.article-header {
max-width: 720px;
margin: 0 auto 3rem;
text-align: center;
}
.article-meta {
display: flex;
justify-content: center;
gap: 1rem;
margin-bottom: 1.5rem;
font-size: 0.875rem;
}
.article-date {
color: var(--color-text-muted);
}
.article-tag {
color: var(--color-amber);
font-weight: 600;
text-transform: uppercase;
letter-spacing: 0.05em;
}
.article-header h1 {
font-family: var(--font-heading);
font-size: clamp(2rem, 4vw, 3rem);
color: var(--color-brown-dark);
margin: 0 0 1rem;
line-height: 1.2;
}
.article-subtitle {
font-size: var(--size-lg);
color: var(--color-text-muted);
margin: 0;
line-height: 1.6;
}
.article-body {
max-width: 720px;
margin: 0 auto;
font-size: var(--size-md);
line-height: 1.8;
color: var(--color-text);
}
.article-body h2 {
font-family: var(--font-heading);
font-size: var(--size-2xl);
color: var(--color-brown-dark);
margin: 3rem 0 1rem;
}
.article-body p {
margin: 0 0 1.25rem;
}
.article-body a {
color: var(--color-green);
text-decoration: underline;
text-underline-offset: 2px;
}
.article-body a:hover {
color: var(--color-green-dark);
}
.article-body strong {
color: var(--color-brown-dark);
}
.article-footer {
margin-top: 4rem;
padding-top: 2rem;
}
.article-footer hr {
border: none;
border-top: 1px solid var(--color-border);
margin: 0 0 2rem;
}
.article-cta {
text-align: center;
font-size: var(--size-sm);
color: var(--color-text-muted);
line-height: 1.6;
}
.article-cta a {
color: var(--color-green);
}
@media (max-width: 640px) {
.article {
padding: 6rem 1.25rem 4rem;
}
.article-header h1 {
font-size: 1.75rem;
}
.article-body {
font-size: var(--size-base);
}
}
</style>

252
src/pages/blog/the-soil-beneath-the-code.astro Normal file
View file

@ -0,0 +1,252 @@
---
import BaseLayout from '../layouts/BaseLayout.astro';
---
<BaseLayout
title="The Soil Beneath the Code — Scott Scoble"
description="A three-layer framework for understanding what makes engineering organizations healthy — or not."
ogType="article"
canonicalUrl="/blog/the-soil-beneath-the-code"
pageType="blog"
>
<article class="article">
<header class="article-header">
<div class="article-meta">
<span class="article-date">April 28, 2026</span>
<span class="article-tag">Engineering</span>
</div>
<h1>The Soil Beneath the Code</h1>
<p class="article-subtitle">
A three-layer framework for understanding what makes engineering organizations healthy — or not.
</p>
</header>
<div class="article-content">
<p class="lead">
Every retrospective reaches the same conclusion. Something about communication. Something about process. Action items get written. Nothing changes. Because you're treating leaves, not soil.
</p>
<h2>The Soil Diagnostic</h2>
<p>
Soil health is the capacity of your team's environment to sustain growth. Three layers:
</p>
<p><strong>Nutrients</strong> — Skills, knowledge, domain expertise. What your team knows how to do.</p>
<p><strong>Structure</strong> — Relationships, handoffs, decision paths. How work moves through the system.</p>
<p><strong>Microbiome</strong> — Trust, psychological safety, shared purpose. What makes people stay.</p>
<p>
When any layer depletes, symptoms appear at the surface. Burnout. Attrition. Missed deadlines. These are not the problem. These are the crop failing.
</p>
<h2>The Misdiagnosis Pattern</h2>
<p>
Most teams treat surface symptoms. More process. More tools. More hires. None of it checks what's actually depleted underneath.
</p>
<p>
This is strip-mining: extracting capability without replenishing the source. You ship faster this quarter. You lose the capacity to ship next quarter. Repeat until the farm is dead.
</p>
<p>
The irony of strip-mining is that it produces record yields right before collapse. Your velocity metrics look great. Your retention doesn't.
</p>
<h2>Layer 1: Nutrients — The Skills Layer</h2>
<p><strong>Depletion symptoms:</strong></p>
<ul>
<li>Knowledge silos form</li>
<li>"Bus factor" risks emerge</li>
<li>Onboarding takes longer</li>
<li>"We used to know how to do this" becomes common</li>
</ul>
<p>
<strong>Example:</strong> Your senior architect leaves. The tribal knowledge about the legacy system walks out with them. New hires take six months to become productive instead of six weeks.
</p>
<p>
<strong>Consequence:</strong> You hire more people to compensate for the knowledge gap. The team grows, but capacity doesn't.
</p>
<h2>Layer 2: Structure — The Workflow Layer</h2>
<p><strong>Depletion symptoms:</strong></p>
<ul>
<li>Meetings multiply</li>
<li>Handoffs become bottlenecks</li>
<li>"Who owns this?" becomes a daily question</li>
<li>Decision latency increases</li>
</ul>
<p>
<strong>Example:</strong> What used to be a five-minute Slack conversation now requires a 30-minute meeting with five people. The work hasn't changed. The structure has eroded.
</p>
<p>
<strong>Consequence:</strong> You add more process to compensate. The process slows things down further. The death spiral accelerates.
</p>
<h2>Layer 3: Microbiome — The Trust Layer</h2>
<p><strong>Depletion symptoms:</strong></p>
<ul>
<li>Psychological safety erodes</li>
<li>Risk-taking disappears</li>
<li>"That's not my job" becomes the default</li>
<li>Retrospectives turn into complaint sessions</li>
</ul>
<p>
<strong>Example:</strong> No one speaks up in the architecture review. The flaws ship to production. The post-mortem turns into a blame session. Trust depletes further.
</p>
<p>
<strong>Consequence:</strong> Innovation stalls. The best people leave. You're left with a team that executes but doesn't create.
</p>
<h2>The Nitrogen Fixer Signal</h2>
<p>
In agriculture, nitrogen fixers are plants that pull nutrients from the air and deposit them in the soil. They make the ground fertile for everything around them.
</p>
<p>
On engineering teams, nitrogen fixers are the people who hold systems together invisibly. They document the thing nobody else will. They onboard the new hire. They bridge the two teams that stopped talking six months ago.
</p>
<p>
Their work doesn't show up in sprint velocity. It shows up in the absence of catastrophe.
</p>
<p>
<strong>Here's the signal:</strong> The person who held three systems together just quit. Now you need three specialists to replace her. That's not a hiring problem. That's a soil problem.
</p>
<p>
Culture is a capital expense. Replacing one generalist who held three systems costs three specialists you now have to hire. The math isn't subtle.
</p>
<h2>Cultivation, Not Extraction</h2>
<p>
The alternative to strip-mining is cultivation. Cultivation starts with assessment. What's depleted? What's over-fertilized? What's being strip-mined right now?
</p>
<p>
Assessment solves misdiagnosis. You stop prescribing process for a trust problem. You stop hiring for a structure problem. You see the system as it is — not as the last retrospective described it.
</p>
<p>
Cultivation doesn't mean going slow. It means knowing what you're growing. A team with healthy soil ships faster <em>because</em> the structure holds, not in spite of it.
</p>
<h2>The Soil Assessment</h2>
<p>
Two weeks. Twenty-five hundred dollars. You'll know exactly which layer is depleted, what's being strip-mined, and what to fix first. No framework adoption. No personality test. A diagnostic that makes structural problems visible.
</p>
<div class="cta-box">
<a href="/contact?subject=Soil%20Assessment" class="btn btn-primary">Book your Soil Assessment →</a>
</div>
</div>
</article>
</BaseLayout>
<style>
.article {
max-width: 680px;
margin: 0 auto;
padding: 6rem 1.5rem;
}
.article-header {
margin-bottom: 3rem;
}
.article-meta {
display: flex;
gap: 1rem;
margin-bottom: 1.5rem;
font-size: 0.875rem;
}
.article-date {
color: var(--color-text-muted);
}
.article-tag {
color: var(--color-amber);
font-weight: 600;
}
.article-header h1 {
font-family: var(--font-heading);
font-size: clamp(2rem, 5vw, 3rem);
color: var(--color-brown-dark);
margin: 0 0 1rem;
line-height: 1.2;
}
.article-subtitle {
font-size: 1.25rem;
color: var(--color-text-muted);
margin: 0;
line-height: 1.5;
}
.article-content {
font-size: 1.125rem;
line-height: 1.8;
}
.article-content .lead {
font-size: 1.25rem;
color: var(--color-brown-dark);
margin-bottom: 2rem;
}
.article-content h2 {
font-family: var(--font-heading);
font-size: 1.5rem;
color: var(--color-brown-dark);
margin: 2.5rem 0 1rem;
}
.article-content p {
margin-bottom: 1.25rem;
}
.article-content ul {
margin-bottom: 1.25rem;
padding-left: 1.5rem;
}
.article-content li {
margin-bottom: 0.5rem;
}
.cta-box {
margin: 2rem 0;
padding: 1.5rem;
background: var(--color-cream);
border-radius: 8px;
text-align: center;
}
.btn-primary {
display: inline-block;
padding: 0.875rem 1.5rem;
background: var(--color-amber);
color: var(--color-brown-dark);
font-weight: 600;
text-decoration: none;
border-radius: 6px;
transition: background 0.2s ease;
}
.btn-primary:hover {
background: var(--color-amber-dark);
}
</style>

176
src/pages/blog/three-questions-mentoring.astro Normal file
View file

@ -0,0 +1,176 @@
---
import BaseLayout from '../../layouts/BaseLayout.astro';
---
<BaseLayout
title="Three Questions That Changed How I Mentor — Scott Scoble"
description="The simple mentoring framework that actually gets used: three questions that unlock real growth."
ogType="article"
canonicalUrl="/blog/three-questions-mentoring"
pageType="blog"
>
<article class="article">
<header class="article-header">
<div class="article-meta">
<span class="article-date">May 5, 2026</span>
<span class="article-tag">Leadership</span>
</div>
<h1>Three Questions That Changed How I Mentor</h1>
<p class="article-subtitle">
The simple mentoring framework that actually gets used — three questions that unlock real growth.
</p>
</header>
<div class="article-body">
<p>I've been mentoring engineers for 15 years. I've read the books. I've done the frameworks. I've sat through sessions where we mapped career ladders and OKRs and growth plans. Most of it was noise.</p>
<p>What actually worked was three questions. That's it. No worksheets, no templates, no quarterly reviews. Just three questions that change the conversation from "How am I doing?" to "What am I building?"</p>
<h2>The Three Questions</h2>
<p><strong>1. What are you building?</strong></p>
<p>Not "What are you working on?" Building implies ownership. Intent. Stakes. The answer tells me whether they see their work as craft or as tasks. If they can't answer in terms of impact — "I'm building a payment flow that reduces checkout friction" — we need to zoom out before we zoom in on skills.</p>
<p><strong>2. What's getting in your way?</strong></p>
<p>Not "What are your blockers?" Blockers are Jira tickets. Obstacles are human: unclear authority, a broken relationship with PM, burnout they can't name yet. This question surfaces the real problems — usually interpersonal or structural — that no amount of skill-building will solve.</p>
<p><strong>3. What do you want to be true in six months?</strong></p>
<p>Not "Where do you see yourself in five years?" That's a fantasy exercise. Six months is close enough to be real and far enough to require change. The answer becomes the North Star for our next conversations. We don't make a plan. We just keep asking.</p>
<h2>Why This Works</h2>
<p>Most mentoring frameworks are built for HR. They're designed to produce documentation: growth plans, competency maps, 360 feedback. The three questions are built for humans. They're designed to produce clarity.</p>
<p>The magic isn't in the questions themselves. It's in the repetition. Ask them every two weeks for six months and watch what happens. The person starts hearing the questions in their own head. They start mentoring themselves.</p>
<p>That's the point. The best mentoring relationship is one that makes itself obsolete.</p>
<p><a href="/books">Read more in <em>A Walk in Mentoring</em> →</a></p>
</div>
<footer class="article-footer">
<div class="article-cta">
<p>Enjoyed this? <a href="/blog">Read more articles</a> on AI, leadership, and the human side of technology.</p>
<p>Ready to bring this thinking to your team? <a href="/contact">Let's talk.</a></p>
</div>
</footer>
</article>
</BaseLayout>
<style>
.article {
padding: 8rem 2rem 6rem;
background: var(--color-cream);
}
.article-header {
max-width: 720px;
margin: 0 auto 3rem;
text-align: center;
}
.article-meta {
display: flex;
justify-content: center;
gap: 1rem;
margin-bottom: 1.5rem;
font-size: 0.875rem;
}
.article-date {
color: var(--color-text-muted);
}
.article-tag {
color: var(--color-amber);
font-weight: 600;
text-transform: uppercase;
letter-spacing: 0.05em;
}
.article-header h1 {
font-family: var(--font-heading);
font-size: clamp(2rem, 4vw, 3rem);
color: var(--color-brown-dark);
margin: 0 0 1rem;
line-height: 1.2;
}
.article-subtitle {
font-size: var(--size-lg);
color: var(--color-text-muted);
margin: 0;
line-height: 1.6;
}
.article-body {
max-width: 720px;
margin: 0 auto;
font-size: var(--size-md);
line-height: 1.8;
color: var(--color-text);
}
.article-body h2 {
font-family: var(--font-heading);
font-size: var(--size-2xl);
color: var(--color-brown-dark);
margin: 3rem 0 1rem;
}
.article-body p {
margin: 0 0 1.25rem;
}
.article-body a {
color: var(--color-green);
text-decoration: underline;
text-underline-offset: 2px;
}
.article-body a:hover {
color: var(--color-green-dark);
}
.article-body strong {
color: var(--color-brown-dark);
}
.article-footer {
margin-top: 4rem;
padding-top: 2rem;
}
.article-footer hr {
border: none;
border-top: 1px solid var(--color-border);
margin: 0 0 2rem;
}
.article-cta {
text-align: center;
font-size: var(--size-sm);
color: var(--color-text-muted);
line-height: 1.6;
}
.article-cta a {
color: var(--color-green);
}
@media (max-width: 640px) {
.article {
padding: 6rem 1.25rem 4rem;
}
.article-header h1 {
font-size: 1.75rem;
}
.article-body {
font-size: var(--size-base);
}
}
</style>

207
src/pages/speaking/soil-under-your-team.astro Normal file
View file

@ -0,0 +1,207 @@
---
import BaseLayout from '../../layouts/BaseLayout.astro';
const talk = {
title: "The Soil Under Your Team",
premise: "Diagnose what's actually depleted before you fertilize. A diagnostic framework for team health in AI-augmented work.",
duration: "45–60 minutes",
type: "Workshop",
idealFor: ["Team leads", "Managers", "Engineering directors", "Founders"],
takeaways: [
"The four soil nutrients every team needs",
"How to run a cultivation assessment",
"From diagnosis to cultivation roadmap"
],
description: `Most team interventions fail because they prescribe before diagnosing. Someone reads a book on "psychological safety" and schedules trust falls. Someone hears about "developer experience" and buys a new CI tool. The team is still disengaged, now with a better linter.
The problem isn't the interventions. It's that nobody knows what's actually depleted.
In this workshop, I introduce the Soil Framework: four nutrients that determine whether a team thrives or burns out. We run a live diagnostic on your actual team (or a case study), identify which nutrients are depleted, and build a cultivation roadmap — not a set of prescriptions, but a sequence of interventions that match your specific soil profile.
This isn't theory. I've used this framework with teams at startups and Fortune 500 companies. The teams that diagnose before prescribing show measurable improvement in engagement within 90 days. The teams that prescribe first... buy more tools.`
};
---
<BaseLayout
title={`${talk.title} — Scott Scoble`}
description={talk.premise}
pageType="speaking"
>
<article class="talk-detail">
<header class="talk-header">
<div class="talk-meta">
<span class="talk-type">{talk.type}</span>
<span class="talk-duration">{talk.duration}</span>
</div>
<h1>{talk.title}</h1>
<p class="talk-premise">{talk.premise}</p>
</header>
<div class="talk-content">
<section class="talk-description">
<h2>The Talk</h2>
{talk.description.split('\n\n').map(para => (
<p>{para}</p>
))}
</section>
<section class="talk-takeaways">
<h2>What You'll Learn</h2>
<ul>
{talk.takeaways.map(takeaway => (
<li>{takeaway}</li>
))}
</ul>
</section>
<section class="talk-audience">
<h2>Ideal For</h2>
<div class="audience-tags">
{talk.idealFor.map(audience => (
<span class="audience-tag">{audience}</span>
))}
</div>
</section>
</div>
<footer class="talk-cta">
<a href="/speaking#book" class="btn-primary" data-umami-event="talk-cta-book-soil">
Book This Talk
</a>
<a href="/speaking" class="btn-outline">← All Talks</a>
</footer>
</article>
</BaseLayout>
<style>
.talk-detail {
max-width: 800px;
margin: 0 auto;
padding: 4rem 2rem;
}
.talk-header {
text-align: center;
margin-bottom: 3rem;
}
.talk-meta {
display: flex;
gap: 1rem;
justify-content: center;
margin-bottom: 1.5rem;
}
.talk-type {
background: var(--color-green);
color: white;
padding: 0.25rem 0.75rem;
border-radius: 4px;
font-size: 0.75rem;
font-weight: 600;
text-transform: uppercase;
letter-spacing: 0.05em;
}
.talk-duration {
color: var(--color-text-muted);
font-size: 0.875rem;
}
.talk-header h1 {
font-family: var(--font-heading);
font-size: clamp(1.75rem, 4vw, 2.5rem);
color: var(--color-brown-dark);
margin: 0 0 1rem;
}
.talk-premise {
font-size: 1.125rem;
color: var(--color-text-muted);
font-style: italic;
max-width: 600px;
margin: 0 auto;
}
.talk-content section {
margin-bottom: 2.5rem;
}
.talk-content h2 {
font-family: var(--font-heading);
font-size: 1.25rem;
color: var(--color-brown-dark);
margin: 0 0 1rem;
}
.talk-description p {
color: var(--color-text);
line-height: 1.7;
margin: 0 0 1rem;
}
.talk-takeaways ul {
list-style: none;
padding: 0;
}
.talk-takeaways li {
padding: 0.75rem 0;
border-bottom: 1px solid var(--color-border);
position: relative;
padding-left: 1.5rem;
}
.talk-takeaways li:before {
content: "✓";
position: absolute;
left: 0;
color: var(--color-green);
font-weight: bold;
}
.audience-tags {
display: flex;
flex-wrap: wrap;
gap: 0.5rem;
}
.audience-tag {
background: var(--color-cream);
border: 1px solid var(--color-border);
padding: 0.5rem 1rem;
border-radius: 100px;
font-size: 0.875rem;
color: var(--color-text);
}
.talk-cta {
display: flex;
gap: 1rem;
justify-content: center;
padding-top: 2rem;
border-top: 1px solid var(--color-border);
}
.btn-primary {
display: inline-block;
background: var(--color-amber);
color: white;
padding: 0.75rem 1.5rem;
border-radius: 6px;
text-decoration: none;
font-weight: 600;
}
.btn-outline {
display: inline-block;
background: transparent;
color: var(--color-text);
padding: 0.75rem 1.5rem;
border-radius: 6px;
text-decoration: none;
border: 1px solid var(--color-border);
}
</style>