Repository navigation
fix(podcast-docs): share interview questions with guests, keep internal prep staff-only - #493
Merged
Merged
Conversation
…g internal prep staff-only
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
interviewQuestionsout of the internalrun-sheetsection into a shared guest-visible section (7) Interview Questions,tab: 'guest') on thepodcasttemplate inbackend/src/sponsorDocs/templates.ts.coldOpen,introScript,closingScript), episode plan (goal,audience,keyMessages), and research/host notes (sourceLinks,keyInsights,openQuestions,hostNotes) strictly staff-only (tab: 'internal',internal: true).## Interview Questionsin the shared Markdown export (guest + staff) while keeping## Run Sheet,## Event Description & Episode Plan, and## Internal Research & Host Notes (Staff Only)staff-only.#sponsor-field-interviewQuestionslives.content.interviewQuestionsat the top level ofdoc.content, so all existing docs immediately show their questions to guests after deploy with zero data loss.Testing
npm --prefix backend run typechecknode --test frontend/test/podcast-doc-tabs.test.mjs frontend/test/sponsor-docs.test.mjs(22/22 passed)backend/tests/podcast-guest-form.test.ts&backend/tests/sponsor-docs.test.ts(30/30 passed)npx playwright test e2e/podcast-guest-form.spec.js(4/4 passed)npm --prefix backend run build(runtime boundary & frontend artifact verified)