Ideal Audience fields are empty on all 3 signature talks #46
Labels
No labels
a11y
blocked
bug
content
content
conversion
design
feature
improvement
infrastructure
infrastructure
landing-page
priority:critical
priority:high
priority:low
priority:medium
question
seo
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: sscoble/brand-site#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found: /speaking lists 3 signature talks (50 First Dates, Strip-Mining to Cultivation, Soil Under Your Team). Each has an "Ideal Audience:" label but no content follows it.
Gap: Speaking prospects want to know if your talk is right for their event. Blank audience info makes it harder to self-qualify.
Needs:
Verified complete - All three signature talks have Ideal Audience fields populated in speaking.astro: 1) "50 First Dates with AI": Engineering leaders, AI product teams, CTOs implementing agentic systems, 2) "Strip-Mining to Cultivation": CTOs, VP Engineering, people leaders, engineering managers, 3) "The Soil Under Your Team": Team leads, managers, engineering directors, founders.
Verified complete - Ideal Audience fields are populated for all three signature talks in speaking.astro: 1) "50 First Dates with AI" - Engineering leaders, AI product teams, CTOs, 2) "Strip-Mining to Cultivation" - CTOs, VP Engineering, people leaders, 3) "Soil Under Your Team" - Team leads, managers, directors, founders. Fields are NOT empty as issue suggested.
Fixed: "Ideal Audience" fields were empty due to a prop name mismatch.
Root cause: The
<TalkCard>component expects anaudienceprop, but the speaking page was passingidealForinstead. Sinceaudiencewas alwaysundefined, the "Ideal Audience:" label appeared with no content.Changes made:
src/pages/speaking.astro— Renamed all threeidealForprops toaudience(matching the TalkCard interface)src/components/TalkCard.astro— Made the audience section conditional ({audience && audience.trim() && ...}) so empty audience fields won't render blank sections as a safety guardVerified:
npm run buildpasses successfully (33 pages built, no errors).Fix applied
Root cause: Prop name mismatch.
TalkCard.astroexpects anaudienceprop (line 7), butspeaking.astrowas passingidealFor="..."— so the audience value was never received by the component. The{audience && audience.trim() && (...)}guard on line 27 of TalkCard.astro was always false, causing the Ideal Audience section to never render despite content being present in the source.Fix: Renamed
idealFor→audienceon all 3TalkCardinvocations insrc/pages/speaking.astro:audience="Engineering leaders, AI product teams, CTOs implementing agentic systems"audience="CTOs, VP Engineering, people leaders, engineering managers"audience="Team leads, managers, engineering directors, founders"Verification: Component prop interface (
audience: string) now matches the prop passed in. The audience content (which was always correct) will now render in the "Ideal Audience: {audience}" output.Closing as complete.