✦ LAMBDA CHI ALPHA β€’ HOUSE DINING SETUP

ADMIN MODE: THE SETUP GUIDE πŸ‘©β€πŸ³

One-time setup for the house dining site. Once connected, approved admins can update meals directly on the website and everyone will see the changes.

STEP 1

Create your free Firebase project

Visit Firebase Console β†’ Create project. Name it something like Lambda Eats. You can skip Google Analytics.

Inside your project, click the Web (</>) icon to register a web app. Give it any nickname. Firebase shows a code snippet containing const firebaseConfig = { ... }. Keep that tab open.

You do not need to enable Firebase Hosting; Netlify will host the website.

STEP 2

Enable the database and paste the security rules

  1. Firebase Console β†’ Build / Databases & Storage β†’ Firestore Database β†’ Create database. Choose Production mode (not test mode) and a region.
  2. Open Firestore's Rules tab.
  3. Open the included firestore.rules file from this ZIP in Notepad, copy all the text, paste it into the Rules editor, and click Publish.
πŸ”’ Critical: Don't use β€œallow read, write: if true”. Only approved Firebase admin accounts can edit meals. The included security rules enforce this.
STEP 3

Create an admin account

  1. Firebase Console β†’ Authentication β†’ Get started β†’ Sign-in method β†’ enable Email/Password and save.
  2. Go to Authentication β†’ Users β†’ Add user. Enter the chef's email and a strong password.
  3. In that Users list, copy the new account's User UID (long string of letters and numbers).
  4. Go to Firestore Database β†’ Data. Create a collection named admins (all lowercase). Add a document where the Document ID is exactly the UID you copied. Add any field, e.g. name = string Chef. Save.
βœ… Now that account can edit. Anyone else (even if they have an account) cannot edit unless you add their UID as another document in admins.

Need two admins? Create another user, then add their UID as another doc in admins.

STEP 4

Paste Firebase configuration here (no code editing)

Copy the firebaseConfig object from Firebase Console β†’ Project settings βš™οΈ β†’ General β†’ Your apps β†’ Web app β†’ SDK setup and configuration β†’ Config. Paste the whole snippet into the box.

This is the public web app configuration only (fields like apiKey, projectId, authDomain and appId). Never paste service-account JSON or private keys.

After clicking the button, Windows downloads a file called firebase-config.js. Move that file into the extracted website folder and choose Replace the file in the destination when Windows asks.

STEP 5

Publish the website as a real link

  1. Open Netlify Drop and sign in.
  2. On Windows, extract the ZIP first. After replacing firebase-config.js, drag the Lambda_Eats folder (the folder containing index.html) into Netlify Drop. Drag the extracted folder, not just the HTML file.
  3. Netlify gives you a link ending in .netlify.app. That's the link you send to the fraternity.
  4. If Firebase needs it, in Firebase Authentication β†’ Settings β†’ Authorized domains, add your your-site.netlify.app domain.

If you already have a Lambda Eats Netlify site, use that site's Deploys area to upload the new folder. That keeps the existing website address.

STEP 6

Log in and update a meal πŸŽ‰

  1. Visit your .netlify.app link.
  2. When the top badge says ● LIVE MENU, click πŸ” Admin.
  3. Sign in with the email and password you created in Firebase.
  4. Click any Monday–Friday lunch or dinner card, make your change, and press Publish update.
  5. Have another brother refresh the site (or leave it open β€” updates appear automatically). They can view the menu without logging in.

Existing file-only edits from the old website do not automatically transfer. The Nov 16–20 meals from your photographed menu are already built in as the starting menu. New edits go to Firestore.