From d1b7ba9699c7865750e13f0f7b4dbcfb1f3e8a51 Mon Sep 17 00:00:00 2001 From: Gaurav Shah Date: Tue, 7 Jul 2026 23:17:10 -0400 Subject: [PATCH 1/2] Rename Content Strategist role to Marketing Director 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 --- constants/role-specific-questions.json | 2 +- src/app/roles/page.tsx | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/constants/role-specific-questions.json b/constants/role-specific-questions.json index 10f0ed0d..608612d9 100644 --- a/constants/role-specific-questions.json +++ b/constants/role-specific-questions.json @@ -107,7 +107,7 @@ }, { "id": "6", - "role": "Content Strategist", + "role": "Marketing Director", "questions": [ { "question": "What do you see as the purposes of content within the user experience of an app?", diff --git a/src/app/roles/page.tsx b/src/app/roles/page.tsx index e1c70705..ebff9137 100644 --- a/src/app/roles/page.tsx +++ b/src/app/roles/page.tsx @@ -145,7 +145,7 @@ const EXECUTIVE_TEAM: RoleItem[] = [ description: "The Graphic Designer will support External Directors and the design team to create visual assets for marketing and project teams.", responsibilities: [ - "Work closely with Content Strategists to create effective cross-platform marketing for Blueprint.", + "Work closely with Marketing Directors to create effective cross-platform marketing for Blueprint.", "Build and support UW Blueprint's brand through brand assets, graphics, and polished collateral (banners, website design, slideshows, etc.).", "Use Figma and/or other design tools to produce graphic designs, illustrations, and motion design materials.", ], @@ -156,9 +156,9 @@ const EXECUTIVE_TEAM: RoleItem[] = [ ], }, { - title: "Content Strategist", + title: "Marketing Director", description: - "Collaborate with Graphic Designers and marketing team members to develop cohesive cross platform content for Blueprint.", + "The Marketing Director is in charge of Blueprint's brand image across the community, whether that's through our social channels, in-person events, or marketing to students, non-profits, and companies.", responsibilities: [ "Plan, write, and manage content across social platforms, newsletters, and marketing materials.", "Develop content calendars and campaign ideas that highlight Blueprint's projects, events, and community impact.", From fc1d4efa3bd603f8fe784bf9d6ebe0342e78def6 Mon Sep 17 00:00:00 2001 From: Gaurav Shah Date: Tue, 7 Jul 2026 23:32:35 -0400 Subject: [PATCH 2/2] Fix CI build failure on fork PRs: guard Firebase init `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 --- utils/firebase.ts | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/utils/firebase.ts b/utils/firebase.ts index c93b9e17..638434b4 100644 --- a/utils/firebase.ts +++ b/utils/firebase.ts @@ -13,10 +13,17 @@ import { STORAGE_BUCKET, } from "@utils/secrets"; +// Placeholders keep Firebase initialization (`getAuth`/`getDatabase`) from +// throwing at import time during `next build` when these env vars are absent — +// e.g. CI runs on fork PRs, which GitHub does not expose repository secrets to, +// so the build would otherwise crash while collecting page data. Real +// deployments build with the real values injected, so the fallbacks are unused +// there. export const firebaseConfig = { - apiKey: API_KEY, + apiKey: API_KEY || "placeholder-api-key", authDomain: AUTH_DOMAIN, - databaseURL: DATABASE_URL, + databaseURL: + DATABASE_URL || "https://uw-blueprint-placeholder.firebaseio.com", projectId: PROJECT_ID, storageBucket: STORAGE_BUCKET, messagingSenderId: MESSAGING_SENDER_ID,