Rename Project Lead role to Technical Lead

constants/role-specific-questions.json

@@ -82,7 +82,7 @@
   },
   {
     "id": "4",
-    "role": "Project Lead",
+    "role": "Technical Lead",
     "questions": [
       {
         "question": "Tell us about a challenging technical problem that you've worked on in the past and how you solved it.",
@@ -226,16 +226,6 @@
       }
     ]
   },
-  {
-    "id": "16",
-    "role": "Internal Director",
-    "questions": [
-      {
-        "question": "What would an ideal member experience look like to you?",
-        "maxLength": 1000
-      }
-    ]
-  },
   {
     "id": "16",
     "role": "Sponsorships Director",

src/app/roles/page.tsx

@@ -180,9 +180,9 @@ const PROJECT_TEAM: RoleItem[] = [
     responsibilities: [
       "Write, test, and maintain code in line with the team's best practices and technical standards.",
       "Participate in code reviews, both giving and receiving feedback to improve code quality and personal growth.",
-      "Collaborate with the Project Lead and other developers to break down tasks, estimate work, and meet project milestones.",
+      "Collaborate with the Technical Lead and other developers to break down tasks, estimate work, and meet project milestones.",
       "Communicate progress, blockers, and questions proactively during team meetings and check-ins.",
-      "Continuously learn and develop technical skills, taking advantage of mentorship from the Project Lead and other senior members.",
+      "Continuously learn and develop technical skills, taking advantage of mentorship from the Technical Lead and other senior members.",
     ],
     note: "Open to all experience levels; a great opportunity to gain hands-on experience in a team setting.",
   },
@@ -227,9 +227,9 @@ const PROJECT_TEAM: RoleItem[] = [
     note: "Generally a senior, internal-hire preferred role.",
   },
   {
-    title: "Project Lead",
+    title: "Technical Lead",
     description:
-      "The Project Lead (or Technical Lead) is responsible for leading the team and driving the technical direction of the project, providing support and mentorship to developers on the team and working with the product manager to run the team effectively.",
+      "The Technical Lead is responsible for leading the team and driving the technical direction of the project, providing support and mentorship to developers on the team and working with the product manager to run the team effectively.",
     responsibilities: [
       "Organizing best code practices, performing code reviews, mentoring developers, planning tasks, making key technical decisions and software architecture design.",
       "Provide leadership, mentorship, and project execution skills as the overall success of the team is largely self guided.",
@@ -239,7 +239,7 @@ const PROJECT_TEAM: RoleItem[] = [
     ],
     link: {
       href: "https://medium.com/uw-blueprint/member-spotlight-project-lead-anne-chung-1ca9f22c9db3",
-      label: "Member Spotlight — Project Lead",
+      label: "Member Spotlight — Technical Lead",
     },
     note: "Generally a senior, internal-hire preferred role.",
   },

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,