Skip to content

Rename Content Strategist role to Marketing Director - #284

Open
GauravShah123 wants to merge 2 commits into
uwblueprint:mainfrom
GauravShah123:role/marketing-director
Open

Rename Content Strategist role to Marketing Director#284
GauravShah123 wants to merge 2 commits into
uwblueprint:mainfrom
GauravShah123:role/marketing-director

Conversation

@GauravShah123

Copy link
Copy Markdown
Collaborator

What

Renames the Content Strategist role to Marketing Director on the roles page (/roles) and the application page (/apply), and refocuses the role description on owning Blueprint's brand image across the community.

Changes

  • src/app/roles/page.tsx
    • Renamed the role title Content StrategistMarketing Director.
    • Updated the description to focus on being in charge of Blueprint's brand image across the community — through social channels, in-person events, and marketing to students, non-profits, and companies.
    • Updated the Graphic Designer responsibility that referenced "Content Strategists" so it points to "Marketing Directors".
  • constants/role-specific-questions.json
    • Renamed the role from Content StrategistMarketing Director, which updates the role option and role-specific questions on the application form. (The apply form matches applicants to questions by this role string, so the label and matching stay in sync.)

Scope / out of scope

Kept the change minimal and limited to the /roles and /apply surfaces. Intentionally left existing team member listings (constants/members.json, constants/headshot-constants.ts) and the /students page untouched, since those reflect current members' actual titles rather than the open-role definitions.

🤖 Generated with Claude Code

gauravshah-betterup and others added 2 commits July 7, 2026 23:17
Rename the Content Strategist role to Marketing Director on the /roles
and /apply pages, and refocus its description on owning Blueprint's brand
image across the community (social channels, in-person events, and
marketing to students, non-profits, and companies). Also update the
Graphic Designer responsibility that references the role by name.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`next build` evaluates pages/_app during "Collecting page data", which
imports utils/firebase and calls getAuth()/getDatabase() at module load.
When the NEXT_PUBLIC_* Firebase env vars are absent, these throw
("Cannot parse Firebase url", "auth/invalid-api-key") and the build fails.

This happens on every fork PR: GitHub does not expose repository secrets
to pull_request workflows from forks, so the secret-backed env vars are
empty. Give apiKey and databaseURL valid-format placeholder fallbacks so
initialization succeeds during the build. Real deployments build with the
real values injected, so the placeholders are never used there.

Verified: `next build` with all Firebase env vars unset now completes
successfully (previously failed while collecting page data).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants