Admin Help & FAQ

Everything admins need to keep the site running. Use the tabs to filter by category, the alphabet rail to jump by starting letter, or the search box to find a topic.

📋 Overview — what the site depends on

Your website is static (GitHub Pages) but pulls live data from a few services. If something on the site looks wrong, one of these is usually why.

🗓️ Ministry Operations Schedule

This is the working rhythm for admin stewardship — who does what, when, and on which platform. It ensures consistency across every channel we serve.

📅 Daily (Monday–Friday)

2️⃣ Mid-Week (every 2–3 days)

📚 Study Saturdays — Discipleship

⛪️ Sundays — Fellowship Focus

🖼️ Updating images on the website

Some parts of the site display images that admins manage directly (team photos, ministry highlights, homepage featured slides, hero backgrounds). Replacing these is done through GitHub's web interface — no coding, no terminal. Here's the full walkthrough.

Step 1 — Sign in to GitHub

1. Open github.com/login in your browser.
2. Enter your GitHub username/email and password. (If you use two-factor, enter the code too.)
3. Once signed in, go to the repo: github.com/seedtheword/seedtheword

Step 2 — Know which folder to go to

Images are organized by how they're used on the site. Pick the folder that matches what you're updating:

Step 3 — Replace an existing image (keeping the same filename)

Easiest case: you want to swap out a photo but keep everything on the page pointing to the same file.

1. In the repo, navigate to the folder (e.g., assets/images/team/).
2. Click the file you want to replace (e.g., Vanessa.jpg).
3. Near the top right, click the pencil icon (🖊 Edit this file) — if the pencil is missing for image files, look for a button labeled "..." or "Replace".
4. On the file page, there should be an option "Replace this file". Click it.
5. Drag your new image into the upload box. The new file must have the same filename as the old one or the site won't find it.
6. At the bottom of the page, add a short commit message like "Update Vanessa's photo" and click Commit changes.
7. Wait about 30–60 seconds, then hard-refresh the live site (Ctrl+Shift+R / Cmd+Shift+R) to see the new image.

Step 4 — Add a brand-new image to a folder

Use this when you want to add (not replace) a photo — for example, adding a new team member or a new ministry-highlights photo.

1. Navigate to the correct folder in the repo (see Step 2).
2. Near the top right, click "Add file" → "Upload files".
3. Drag your image(s) into the upload area. Multiple files at once is fine.
4. Before you drag: make sure the filename is descriptive and uses only letters, numbers, and dashes. Avoid spaces, emojis, and unusual characters. Example good names: pack-ship-april-2026.jpg, easter-worship.jpg, youth-outreach-may.jpg.
5. Add a commit message like "Add April pack & ship photos" at the bottom.
6. Click Commit changes.

Step 5 — Update a specific spot on the site

Step 6 — How to tell if your change went live

1. After clicking Commit changes, you'll see a small progress indicator at the top of the page. Wait for it to finish.
2. Go to the repo's Actions tab. There'll be a new workflow run named "pages build and deployment" — wait for its green check (usually 30–60 seconds).
3. Open the live website and hard-refresh (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac). Normal refresh may serve a cached old version.
4. If the change still isn't visible after 2 minutes + hard refresh, check the Actions tab for a red X — that means the build failed. Screenshot it and ping the dev.

🎧 Managing "What We're Listening To" & Partner Ministries

Both sections on the Community page read from a simple list in one JavaScript file. Adding or removing items is a small, guided edit — no images to upload, no styling to touch.

// Fill out the form above to generate a JSON block.

Add a Spotify episode to "What We're Listening To"

1. Open the Spotify episode or show in your browser. Copy the full URL from the address bar.
2. Scroll up to the Recommendations builder tool above. Make sure the Spotify tab is selected.
3. Paste the URL into the Spotify URL field. The ID and type (episode/show) are extracted automatically. Fill in the title, source, and note fields. Check the live preview — if it plays, it'll play on the site.
4. Click 📋 Copy JSON.
5. Open assets/data/recommendations.json on GitHub and click the pencil to edit.
6. Paste the JSON block inside the "listening" array. Put a comma after the previous block's closing }. The last item in the array should not have a trailing comma.
7. Commit. The card appears on the Community page within 60 seconds.

Add a YouTube video

Same workflow, but use kind: 'youtube' and use the video's ID (the string after v= in a YouTube URL).

{
  kind: 'youtube',
  id: 'dQw4w9WgXcQ',
  title: 'Video title',
  source: 'Channel name',
  note: "Why this stood out.",
},

Add a plain link (article, sermon on another site)

{
  kind: 'link',
  url: 'https://example.com/full-url',
  title: 'Article or sermon title',
  source: 'Author or ministry',
  note: "Why it matters.",
  image: 'assets/images/featured/some-image.jpg', // optional thumbnail
},

Remove an item

Delete its full block (the curly braces { ... } and the comma after) from the array. Commit. Card disappears.

Reorder items

Cut and paste the blocks into a new order. The order in the array is the order on the page.

Add a Partner Ministry

1. If you have a partner logo, upload it first to assets/images/partners/ (create the folder if it doesn't exist — github.com's web UI lets you do this while uploading a file).
2. Scroll up to the Recommendations builder tool and pick the 🤝 Partner Ministry tab. Fill in the name, website URL, optional logo path, and optional description.
3. Click 📋 Copy JSON.
4. Open assets/data/recommendations.json on GitHub and click the pencil to edit.
5. Paste the JSON block inside the "partners" array, with a comma after the previous block's closing }. The last item in the array should not have a trailing comma.
6. Commit. The partner card appears on the Community page within 60 seconds.

🖼️ Managing bundle slideshow images (store.html)

Each of the three bundle cards on the Store page has a rotating slideshow at the top of the card. The photos are pulled from three dedicated folders in the repo, and each folder has a tiny manifest file (images.json) that tells the site which photos to show and what caption to put on them. This is designed so you can keep the store feeling fresh without touching any HTML or CSS.

Add a new photo to a bundle slideshow

1. Resize and compress your photo first. Aim for 1600×900 px (16:9) and under 300 KB. A free tool like squoosh.app handles this in one step.
2. Rename the file with a numeric prefix so the order is obvious — for example 03-group-study.jpg. Use lowercase and dashes. No spaces, no apostrophes, no weird characters.
3. In the GitHub repo, navigate into the right bundle folder (e.g. assets/images/bundles/lifegroup/) and click Add file → Upload files. Drag your photo in. Commit.
4. In that same folder, open images.json and click the pencil icon to edit. Add a new block inside the "images" array:

   {
     "file": "03-group-study.jpg",
     "caption": "Friday night life group at Riverside"
   }

5. Important: put a comma after the previous block's closing } so the JSON stays valid. The last block in the array should not have a trailing comma.
6. Commit with a message like "Add group study photo to life group bundle." Hard-refresh the store page — the new slide rotates in automatically.

Replace a photo

Upload the replacement with the same filename, overwrite the existing one when GitHub asks, and commit. The caption in images.json stays the same. That's it.

Remove a photo

1. Delete the image file from the bundle folder (click the file in GitHub → trash icon → commit).
2. Open images.json in the same folder and delete the matching block (including its surrounding curly braces and the comma).
3. Commit. The slide is gone.

Reorder the slides

The order of blocks in "images" is the order they appear. Cut and paste them into whatever order you want, commit, done. Renaming the file prefixes (01-, 02-, etc.) is a courtesy for future admins but not required for the rotation to work.

Change a caption

Open images.json, edit the "caption" field on the right block, keep the double quotes around the new text, commit. Captions can be empty ("caption": "") — the caption strip just won't show on that slide.

Test everything at once

1. Go to store.html and hard-refresh (Ctrl+Shift+R / Cmd+Shift+R).
2. You should see each bundle card rotating through its photos every ~5.5 seconds, with dots at the bottom of each slideshow.
3. Hover over a card — the rotation pauses. Click a dot — it jumps to that slide.
4. If a slideshow doesn't appear at all, open the console (F12) and look for a "could not load manifest" warning — usually it's a JSON typo.

📤 Team media drop (how the team shares photos/videos)

We don't have a separate upload page. Instead, we use an encouragement call-out inside the "Ministry Outreach & Highlights" section on news.html — the "Your story belongs here too" card. When assets/data/media-drop.json is configured, a 📤 Share Photos & Videos button appears next to "Submit a Testimony" and "Share on Telegram", and it opens our Google Form. Every submission lands in our ministry Google account with the uploader's name, caption, and the files themselves — plus a row in a Responses spreadsheet. Admins review from there and push the good stuff to the site.

First-time setup — Google Form (recommended)

This is the cleanest path. Every upload arrives with who sent it, what caption they gave it, when, plus a row in a Responses spreadsheet. All files live in our own Google Drive.

1. Sign in to forms.google.com with the ministry Google account (seedthewordministry@gmail.com).
2. Click Blank form. Title it "Share Photos & Videos — Seed the Word".
3. Add these questions (use the + button to add each one):
   • Your name — Short answer, required
   • Your email — Short answer, required, enable Response validation → Email
   • Where was this taken? — Short answer, optional (e.g. "UW Seattle outreach" or "Saturday study")
   • Tell us about it — Paragraph, optional
   • Upload photos & videos — File upload, required. Allow any file type. Set max file size to 10 MB (or higher if your storage allows) and max number of files to 10.
4. Click the Settings tab:
   • Leave "Collect email addresses" unchecked (you already ask in a question, and this setting would force a Google login for verified email).
   • Under Responses, enable "Restrict to users in..." → OFF so non-ministry-account users can submit.
   • Turn ON "Allow response editing" so uploaders can fix typos.
   Note: File upload questions require the uploader to sign in to any Google account. This is a Google policy we can't disable, but most phones are already signed in so it's invisible to them.
5. Click the Responses tab → Link to Sheets → create a new spreadsheet. This is your review queue.
6. Click the Send button (top right) → the link icon tab → check "Shorten URL" → Copy.
7. In the repo, open assets/data/media-drop.json and paste that URL into the "formUrl" field, replacing REPLACE_WITH_YOUR_FORM_ID.
8. Commit. Hard-refresh news.html — the 📤 Share Photos & Videos button now appears on the "Your story belongs here too" call-out.

Admin review flow

1. Open the Form's Responses tab (or the linked Google Sheet) to see a table of every submission — uploader name, email, caption, links to files.
2. Click a file link to preview it in Drive.
3. For media you want to publish, download, resize/compress, and commit to the right folder in the repo (outreach, ministry-highlights, team, etc.). Flowcharts earlier in this page walk through each destination.
4. Leave the rest in Drive as an archive. Nothing has to be deleted.

Alternative: direct Drive folder (less recommended)

If you'd rather skip the Google sign-in step and let anyone with the link drop files straight into a shared folder (no name, no caption, no accountability), you can use a plain Drive folder instead of a Form:

1. Create a Drive folder. Right-click → Share → "Anyone with the link" → Editor.
2. Paste the share URL into "uploadUrl" in media-drop.json (leave "formUrl" blank or as the placeholder).
3. Commit.

Turn the upload button off or swap targets

• Switch to a different Form or folder: paste the new URL into "formUrl" or "uploadUrl", commit. The call-out button updates without any HTML changes.
• Turn the upload button off temporarily: set "enabled": false in media-drop.json. The button hides; "Submit a Testimony" and "Share on Telegram" stay visible.
• Leave it unconfigured: if both URLs still contain REPLACE_WITH_..., the button stays hidden automatically — nothing looks broken on the site.

🙌 Managing Ministry Outreach cards (news.html)

The "Ministry Outreach & Highlights" section on the News page leads with up to 3 outreach cards, each with its own rotating slideshow of photos and videos. Each card represents one real outreach (a date, a location, a short write-up, an optional testimony). New events are added by dropping a new folder of media in and appending one entry to a master index — no HTML edits needed.

Add a new outreach card

1. In the repo, open assets/images/ministry-outreach/. Click Add file → Create new file and type a folder path like bellevue-park-july-2026/images.json (GitHub creates the folder for you as you type the slash).
2. Upload your photos and videos into that new folder. Prep guidelines:
   • Photos: 1600×1200 or similar 4:3, under ~300 KB each. Rename to 01.jpg, 02.jpg, 03.jpg … for predictable ordering.
   • Videos: MP4, vertical or horizontal both fine. Keep under ~10 MB each; compress on freeconvert.com if needed. Name them video-01.mp4, video-02.mp4.
3. Open the images.json file you just created and paste this template (adjust filenames to match what you uploaded):

   {
     "media": [
       { "file": "01.jpg", "type": "photo", "caption": "" },
       { "file": "02.jpg", "type": "photo", "caption": "" },
       { "file": "video-01.mp4", "type": "video", "caption": "Moment from the outreach" },
       { "file": "03.jpg", "type": "photo", "caption": "" }
     ]
   }

   Order is play order. Photos hold for ~5.5 seconds; videos play their full length before advancing. Captions are optional — leave "" to hide the caption strip.
4. Now open assets/data/ministry-outreach.json and add a new entry at the top of the events array (most-recent first):

   {
     "folder": "bellevue-park-july-2026",
     "title": "Summer Park Evangelism",
     "date": "July 12, 2026",
     "location": "Downtown Park, Bellevue",
     "body": "A short paragraph about the outreach — who we partnered with, what you handed out, how the day felt.",
     "testimony": ""
   },

   Put a comma after the closing } if there are other entries below it.
5. Commit both changes with a message like "Add July 12 Bellevue park outreach card." Hard-refresh news.html and the new card appears at the front of the outreach row.

Add a testimony to an existing outreach

Open assets/data/ministry-outreach.json, find the right event, and fill in the "testimony" field with a 1-3 sentence first-person quote. Keep the double quotes around it. Example:

"testimony": "Aliosha handed me a pocket New Testament and said he'd pray for my studies. I hadn't opened a Bible in 10 years. Two weeks later, I'm still reading."

Commit. The quote appears in a gold-bordered block on the card.

Change the order of outreach cards

The order of the events array is the display order. Cut and paste the blocks to reorder. Only the top 3 appear on the page — the rest sit archived in the file for later.

Remove an outreach from the page

Two options:

• Temporary hide — move the event's block further down in the events array (below position 3).
• Permanent delete — delete the event's block from ministry-outreach.json, then delete its folder from assets/images/ministry-outreach/.

🏠 Managing the Homepage

The homepage is intentionally tight: Hero → Featured From Our Ministry (Showcase Carousel) → Walking the Path of Light → Footer. The Showcase Carousel does all the rotating-content heavy lifting, and the daily verse, tips, and featured highlights are integrated into it.

Add a new verse to the rotation

1. Open assets/data/daily-verses.json in the repo and click the pencil icon to edit.
2. Inside the "verses" array, add a new block at the end:

   { "text": "Full verse text here.", "ref": "Book 1:1", "version": "KJV" }

3. Put a comma after the previous block's closing } so the JSON stays valid. The last block should NOT have a trailing comma.
4. Commit. The new verse joins the rotation. It may not land on today's screen — that depends on the day-of-year math.

What the Showcase Carousel rotates

• Featured ministry highlights — editorial slides defined in assets/js/showcase-carousel.js (Study Saturday Live, Pack & Ship Nights, Zander's Bible, etc.)
• Daily Bible content — one slide per day auto-picked from DAILY_CONTENT in showcase-carousel.js (verses, tips, facts, encouragement). The rotation cycles through categories day-of-year so each day feels different.
• Latest Instagram posts — top 3 by likes from the last 60 days, pulled live from assets/data/instagram.json.

Edit the showcase slides or daily content

Both lists live at the top of assets/js/showcase-carousel.js — FALLBACK_SLIDES and DAILY_CONTENT. This is a JS file, so follow JSON-ish syntax carefully: single quotes, commas after every item, no trailing comma on the last one. If in doubt, ping the dev on duty.

🌱 Walking the Path of Light (homepage ministry map)

The homepage's second section, anchored in Psalm 119:105 ("Thy word is a lamp unto my feet, and a light unto my path"), draws the ministry's journey as a glowing path of waypoints on a dark canvas. Each waypoint card has a short paragraph, a tag line, and a call-to-action link. Changes here require an HTML edit in index.html (search for the-path). Keep paragraphs short — the cards are meant to be scannable. If the team's lifecycle framing evolves, update all three phase cards together so the loop still makes sense.

🔧 How to do common tasks

Add a new event to the calendar

1. Sign in to calendar.google.com with seedthewordministry@gmail.com.
2. Click anywhere in the calendar on the target date.
3. Enter a title, pick a start/end time, add a description.
4. Save. The event shows on the website within 1 minute.

Publish a new podcast episode

1. Go to podcasters.spotify.com and sign in.
2. Click New Episode → upload the audio file (MP3 or WAV).
3. Add a short title and 1-2 sentence description.
4. Click Publish. The episode appears in the site's Spotify embed automatically (may take a minute).

Change the livestream schedule

The "LIVE NOW / OFFLINE" logic is hardcoded in assets/js/twitch-integration.js. If the schedule changes (e.g., moves from Saturday 7 PM), the site needs a code edit. Ping the dev on duty.

Trigger a fresh Instagram sync

1. Go to the repo's Actions tab.
2. Pick Scrape Instagram Feed from the left sidebar.
3. Click Run workflow → choose branch main → Run workflow.
4. Wait ~1 minute. The site updates within a minute of completion.

⚙️ Set up the order email handler (Apps Script Web App)

The bundle-builder review form on bundle-builder.html can either submit to a free Formspree inbox (default) or to a Google Apps Script Web App you own. The Apps Script path adds three things Formspree's free tier can't: an automatic gifter receipt, a permanent Google Sheet ledger of every order, and an optional heads-up email to the giftee. Setup takes about 10 minutes the first time, no installs, no payments.

Heads-up: MailApp.sendEmail sends as the script owner via Google's session — there is no SMTP, no Gmail App Password, no 2FA prerequisite for this script to function. (2FA on the account is generally a good idea, but unrelated.)

1. Sign in to script.google.com as seedthewordministry@gmail.com.
2. Click + New project. Rename it to STW Order Handler (top left, click the title).
3. In another tab, open sheets.new. Rename the spreadsheet to STW Order Ledger. Rename the first tab from Sheet1 to Orders (right-click the tab → Rename). (Already done — the existing Sheet ID is baked into order-handler.gs.)
4. (Skipped — Sheet ID is already in the source.)
5. Open the repo file docs/apps-script/order-handler.gs in another tab. Copy its full contents.
6. Back in the Apps Script editor's Code.gs, select all (Ctrl/Cmd+A) and paste over.
7. (Skipped — no placeholder to replace; LEDGER_SHEET_ID is already populated.)
8. Click Save (disk icon, top toolbar). Then click Deploy → New deployment. Set Type = Web app. Set Description = v1. Set Execute as = Me (seedthewordministry@gmail.com). Set Who has access = Anyone. Click Deploy.
9. Authorize when prompted — Google will ask for permission to access Sheets and send Gmail. Click Allow. (You may see an "unverified app" warning — click Advanced → Go to STW Order Handler (unsafe). This is expected for personal scripts.)
10. Copy the Web app URL at the end of the dialog (starts with https://script.google.com/macros/s/…/exec).
11. Open the admin editor → pick Site config (cross-cutting) → paste the URL into orderHandlerUrl → Save & commit.

Verify it works: hard-refresh bundle-builder.html in another tab. Place one test Essentials order to your own email, ticking the giftee opt-in box and entering a second email you can read. You should get three emails arrive (gifter receipt, team notification, giftee heads-up) and a new row in the Orders tab of the Sheet. For Ministry Calling you'll get two emails (the giftee path is intentionally never used for outreach orders).

If something looks off: open the Apps Script editor → Executions tab in the left sidebar — every doPost call logs there with full input/output. Most issues are a typo'd LEDGER_SHEET_ID or the deployment access set to Only myself instead of Anyone.

Updating the script later: when docs/apps-script/order-handler.gs changes in the repo, repeat steps 5–6 (paste new contents over Code.gs), then click Deploy → Manage deployments → ✏️ pencil → New version → Deploy. The Web app URL stays the same.

📖 Wire the Share-Your-Story Google Form to the team email

The "Share your story" modal on news.html iframes the same Google Form configured in assets/data/media-drop.json. To get the styled team-notification email and a row in the Stories tab of the STW Order Ledger every time someone submits, we install an On form submit trigger on onStoryFormSubmit. One-time setup, ~5 minutes.

Why a programmatic trigger install? The STW Order Handler is a standalone Apps Script project (created at script.google.com directly), not bound to a spreadsheet. The trigger UI's Event source dropdown only offers Time-driven and From calendar in standalone projects — From spreadsheet is hidden. We get around that by calling ScriptApp.newTrigger(...).forSpreadsheet(...).onFormSubmit().create() from inside the script itself, which Google honors regardless. The helper functions installStoryTrigger() and removeStoryTriggers() live at the bottom of order-handler.gs for exactly this purpose.

1. Open the Form (Share Photos & Videos — Seed the Word) in the editor (click the pencil icon if you only have the public link, or open it from forms.google.com while signed in as the ministry account).
2. Click the Responses tab → green Sheets icon → Select existing spreadsheet → pick STW Order Ledger (the same sheet your orders write to: 17j5TDDTZ-58MuZ7VO7c1ohPkyHw2LZ2GCWYMFb-CJ50). Click Select. Google will add a new tab to the spreadsheet automatically — leave it; our trigger writes to its own Stories tab and ignores Google's auto-tab.
3. Open the Apps Script editor (script.google.com → STW Order Handler). Make sure the latest order-handler.gs from the repo is pasted into Code.gs and saved (the trigger-install helpers were added in the same commit that fixed onStoryFormSubmit).
4. In the function dropdown at the top of the editor (just left of the ▶ Run button), pick installStoryTrigger.
5. Click ▶ Run. Authorize the new Forms scope when Google prompts (you'll see "STW Order Handler wants to access… Manage your forms in Google Drive" — click Allow).
6. Open the ⏰ Triggers tab (clock icon, left rail). Confirm there's now an entry for onStoryFormSubmit with event type On form submit. Done.

Verify it works: open the live news.html, click 📤 Share photos, video & testimony, fill in the form with your own name/email and any caption, and submit. Within ~30 seconds you should see a styled email at seedthewordministry@gmail.com with subject [STW Story] {your name}, and a new row in the Stories tab of the STW Order Ledger.

If no email arrives: open the Apps Script editor → Executions tab. Each form submission should log an onStoryFormSubmit entry with the trigger payload. Common failure modes:

• "Form trigger fired without namedValues" — the form's responses aren't linked to the spreadsheet that the trigger is bound to. Repeat step 2.
• "Form trigger missing name/email" — the form's question labels don't contain "name" or "email". Open the Form editor and confirm the questions are titled Your name and Your email.
• No execution logged at all — the trigger isn't installed. Repeat steps 4–5 (or run installStoryTrigger again — it's idempotent and removes any prior triggers before re-creating).

To remove the trigger (e.g. switching forms, debugging duplicate emails): pick removeStoryTriggers from the function dropdown and click ▶ Run. It deletes every existing onStoryFormSubmit trigger.

If you'd rather skip the form entirely and have the modal POST directly to the same Apps Script Web App (the same path the contact form uses): change the Share-Your-Story modal in news.html from an iframe to a native form, and have it POST { type: 'story', name, email, story, mediaUrl, consentToPublish } to the URL in orderHandlerUrl. The handler already has a handleStory branch wired up for that path; you just lose the file-upload affordance Google Forms gives you for free.

✅ Verify the bundle customization tiers

The store-page journey now organizes every customization into three tiers: ⭐ Recommended (gold-bordered pills with a star prefix), Standard (normal pills), and 🛎 Special-order (collapsed talk-to-team card). Picking any special-order item changes the order flow: the CTA reads "Continue to share your special-order request →", the team email subject becomes [STW Special Order], and the Sheet's column O is marked yes. After any catalog edit (assets/js/bundle-item-catalog.js) or Apps Script redeploy, walk this checklist to confirm everything still lines up:

1. P1 — tiers render correctly. Hard-refresh store.html, click Essentials → Start customizing → For myself. In step 2's "On the Bible" section, confirm Engraving, Custom painting, and Page-edge spray painting are gold-bordered ★ pills listed first. Confirm a 🛎 Special-order options card exists below — collapsed by default — containing items like Foil stamping and Edge gilding. Repeat for Life Group step 4 and Ministry step 3.
2. P2 — special-order propagation. On any bundle, expand the special-order card and tick one item (e.g. Edge gilding). Advance to review and confirm: (a) a gold informational banner above the form lists the flagged item, (b) the submit button reads "Continue to share your special-order request →", (c) the team email subject after submit reads [STW Special Order] and the body has a "🛎 Special-order items — confirm before fulfilling" section, (d) the Sheet's column O for that row is yes.
3. P3 — tooltip accessibility. Tab through any step. Each pill should be followed in tab order by a small (i) icon with a 3px gold focus outline. Press Enter or Space on the icon — a dark tooltip should appear with the item's plain-English description. On mobile (or DevTools 375px width), tap the (i) icon — the tooltip should appear inline below the pill row, not overlap the next pill.
4. Sign-opt-out. On Essentials step 2 or Life Group step 4, scroll to the bottom and tick Skip the back-cover ministry signing. The review summary on bundle-builder.html should read "Back-cover signing: SKIPPED (per gifter request)" and the team email after submit should include a "🖋 Back-cover signing: SKIPPED per gifter request — do not sign." line.
5. Backward-compat. Old ?c= URLs from before this change should still decode and render — the schema extensions are additive, with missing fields defaulting to [] or false.

If any of those don't behave as described, paste the screen state and we'll trace it from the live system. Most regressions show up in the Apps Script Executions tab — every doPost call logs the full payload + the script's reconciled isSpecialOrder decision.

🧯 Troubleshooting — if the site looks broken

Calendar is empty on news.html

• Check if Google Calendar has any upcoming events at all — maybe there just aren't any.
• Open the browser console (F12) on the news page and look for red errors mentioning "calendar" or "403/401."
• If the API quota is exceeded, calendar will silently fail. Wait an hour and retry, or check the Google Cloud Console for the API key.

Instagram images look broken

• Check the repo's Actions tab. Did the most recent "Scrape Instagram Feed" run succeed?
• If it's been failing for days, rss.app may have disconnected. Sign in to rss.app and re-authorize the Instagram source.
• Worst case: trigger a fresh run manually (see above).

Contact form isn't sending

• Sign in to formspree.io/forms and check the form's message log.
• Verify the form is still "Active" and the ministry email is confirmed.
• Free tier is 50 submissions/month — check the usage counter.

Podcast embed is blank or broken

• Visit the show page directly — if that loads, the embed will too.
• If the show is marked private, public embedding fails. Verify in the podcasters dashboard.

Livestream says "LIVE" when we're not, or vice versa

• The status is schedule-based, not from Twitch. It'll show LIVE Saturday 7–10 PM Pacific regardless.
• If the actual stream time moves, the code needs an update. Ping the dev on duty.

Something else looks wrong

• Hard-refresh the page first (Ctrl+Shift+R / Cmd+Shift+R). Most "broken" reports are stale browser cache.
• Check the repo's Actions tab for recent failed runs.
• Check the browser console (F12 → Console tab) for red errors. Screenshot them before pinging the dev.

📣 Announcing events to Telegram, Instagram & beyond

Every event on the News page has a single 📣 Share Event button in its modal. Tapping it opens a dropdown with multiple destinations — Telegram, WhatsApp, Instagram, the device share sheet, or plain clipboard — and pre-fills each one with an announcement following our ministry format. No retyping, no copy-paste dance.

The announcement format

The Share button uses our ministry template. Every event auto-generates something like this:

❕! MAY 25, 10AM ! ❕
🌱Seed The Word! 🌱
@ Lincoln Rock State Park!

Address:
📍Lincoln Rock State Park, 13253 US-2, East Wenatchee, WA 98802, USA

🙏🏻🤍Hello youth!! 🎉
Memorial Day is coming up soon!

Sign ups are open now!

Date & time 📆 : May 25th, 10am
Cost💲: 20$

Sign up with : @Alina Matyuk-Pavlun
(contact @seedtheword admins for details)

We can\u2019t wait to see you there! \u2728

More Details (https://seedtheword.github.io/seedtheword/news.html#event=abc123)

How each field is generated (so Calendar edits drive the post)

• Time header — format is ❕! DAY-OR-DATE, TIME ! ❕. Close events get the friendlier label (TONIGHT, 6PM, TOMORROW, 7PM, SATURDAY, 10AM); events further than a week out show the date (MAY 25, 10AM). On-the-hour times drop the minutes.
• Venue line "@ Lincoln Rock State Park!" — pulled from the event title if it ends with @ Something, or falls back to the first part of the address. Add @ Lincoln Rock State Park to the event's Google Calendar title to get that exact line.
• Address or coordinates — just the text, no embedded maps links (Telegram auto-linkifies a bare address). If the Calendar event has no address but has coordinates in its extended properties, those are shown instead with a Coordinates: label.
• 🙏🏻🤍 description — pulled verbatim from the event's Description field, prefixed with 🙏🏻🤍. The team's emojis, line breaks, and sign-up instructions come through as written. Keep descriptions under 600 characters — longer ones get trimmed.
• More Details link — a deep link to the event's modal on news.html. Clicking it opens the News page with the event expanded.

Share destinations in the dropdown

• 📱 Device share… — appears on phones (and some desktop browsers). Opens the native share sheet with every installed app. Fastest if you're on your phone.
• 📣 Telegram — opens Telegram's share sheet pre-filled with the announcement and link. Pick the Announcements chat, hit send. Telegram generates a rich preview card from the News page's Open Graph image.
• 💬 WhatsApp — opens WhatsApp with the announcement pre-filled.
• 📷 Instagram — IG has no public share API, so this copies the caption to the clipboard and opens @seedtheword. From there you paste it into a new post, story, or DM.
• 📋 Copy announcement — full text to clipboard. Paste anywhere.
• 🔗 Copy event link only — just the URL, no message. Useful for inline mentions ("see ya at the @seedtheword study ↓ url").

Shareable event links

Every event has a direct URL: news.html#event=<event-id>. Clicking it opens the News page with that event's modal already expanded. The URL in your address bar updates automatically when you open an event, so you can grab it from there if you prefer. Closing the modal cleans up the hash.

Pro tip: edit the event in Google Calendar to control the post

Since everything in the announcement comes from the Calendar event, you can tune the wording by editing the Calendar entry:

• Title ending in @ Place Name → venue line reads "@ Place Name!"
• Paste the full street address into Location → Apple Maps + Google Maps links are auto-generated
• Put the invite/description in the Description field → wraps with 🙏🏻🤍 automatically

Want fully-automated posting (no tap required)?

Done — see the next section for how the Telegram bot handles scheduled announcements automatically.

🤖 Telegram bots — announcements, Bible, prayer

We run three separate Telegram bots so members see clear senders in the chat and each bot can be paused independently. All three post to the @seedtheword supergroup, each into a different topic.

📸 How to attach a photo to a calendar event

Both the Telegram announcements bot and the News-page event cards pull photos from whatever image URLs appear in a calendar event's description. This is the one folder for everything pattern — set sharing once on a single Drive folder, and every file you drop in there inherits the correct sharing automatically.

Hey — for event photos, the easiest way is the 📎 paperclip icon in the calendar event itself. The mirror handles the rest within 5 minutes.

If that doesn't work for some reason, the manual fallback is to upload to our shared STW Calendar Photos folder first:

{{FOLDER_URL}}

Then paste the file's share link into the calendar event's description. Thanks! 🙏

Bot 1 — Announcement bot

• What it does: Posts today's calendar events from the ministry Google Calendar.
• Where: Announcements topic (thread 553).
• Schedule: runs every 15 minutes, Mon–Sat, during quiet-hours window (default 07:00–21:00 PT). LIVE events bypass quiet hours. No Sunday runs.
• Anti-spam: Each event fires at most three posts over its lifetime — once as upcoming, once as a reminder (default 3 hours before start), once as live. Dedup log at assets/data/telegram-announcement-log.json.
• Event photos: paste any image URL into the event description and the post becomes a Telegram photo / album (up to 10 photos). See the "Attach a photo to a calendar event" section above for the Drive folder walkthrough.
• Secret: TELEGRAM_BOT_TOKEN
• Workflow: .github/workflows/telegram-announcements.yml
• Test it: Actions → Telegram Announcements → Run workflow → dry_run = true.

Bot 2 — Daily Bible bot

• What it does: Mon–Fri posts the day's NT reading + optional Russian link + a Prayer & Thanksgiving block. Saturday posts a branded Study Saturday Live teaser with this week's review passages pulled from study-saturday.json.
• Where: General channel (messageThreadId: null). Update the thread ID under Editor → Telegram bot config → Daily Bible bot if the destination changes.
• Schedule: 08:00 Pacific, Monday–Saturday. No Sunday post.
• Reading plan (Mon–Fri): same one the homepage uses — anchored on Apr 30 2026 = Mark 11, advancing one chapter per weekday.
• Saturday template: dedicated Study Saturday Live teaser with TONIGHT banner, Twitch link, three body paragraphs, "This week's study focus / This week's reading" pulled from study-saturday.json. Fully configurable under Saturday: … fields in the editor.
• Saturday config knobs (in telegram-bot.json → bible.saturday, or Editor → Telegram bot config → Daily Bible bot): enabled, twitchUrl, streamStartTimePT, rulesUrl, and four body paragraphs (bodyIntro / bodyReview / bodyGoal / bodyRulesNote).
• Spotify links (Mon–Fri): per-chapter overrides in assets/data/bible-spotify-map.json — chapters for English, russianChapters for Russian. Fallbacks: fallbackShowUrl + russianFallbackShowUrl inside the bible section. Russian line is omitted entirely when no Russian URL is configured.
• Prayer block toggle: set "includePrayerBlock": false inside the bible section if you ever want posts without it.
• Secret: TELEGRAM_BIBLE_BOT_TOKEN
• Workflow: .github/workflows/daily-bible.yml
• Test it: Actions → Daily Bible Reading → Run workflow → dry_run = true.

Bot 4 — Weekly playlist digest

• What it does: Every Saturday at 8 AM Pacific, posts "What's new in the community playlist this week" into the Worship & Music topic, listing each track added in the past week with a one-tap Spotify link.
• Where: Worship & Music topic (thread 1064).
• Schedule: Saturday 08:00 PT. Lands alongside Saturday's Study Saturday Live teaser so members see both Saturday posts as a single weekly rhythm. If nothing was added that week, the post is skipped — we don't send empty digests.
• Reads from: the public Spotify playlist whose ID is set at bible.playlist.playlistId.
• Secret: posts via TELEGRAM_BIBLE_BOT_TOKEN (same bot as daily Bible posts).
• Workflow: .github/workflows/weekly-playlist-digest.yml
• Test it: Actions → Weekly Playlist Digest → Run workflow → dry_run = true.

🎵 STW Community Playlist

Drop in songs that worship God, minister to your soul, or remind you who He is. We all listen together.

▶️ Listen to the playlist
https://open.spotify.com/playlist/18QMpMTYrFt2KxW1Q9NsvX

➕ Join as a collaborator (one tap)
https://open.spotify.com/playlist/18QMpMTYrFt2KxW1Q9NsvX?si=69aaa882a74d40c8&pt=3cf27aeb2c1ffec6bf48b7345e141c26

How to add: tap the green link above once (Spotify opens, accept the invite). After that, any song you're playing in Spotify has Add to playlist → STW Community Playlist in the three-dot menu — on phone or desktop.

Every Saturday at 8 AM PT, a digest of the week's new additions lands in this topic automatically. 🎧

Bot 3 — Prayer & Thanksgiving nudge bot (disabled)

• Status: Disabled as of May 2026. The Bible bot now posts a full Prayer & Thanksgiving blockquote as part of its daily message (Mon–Sat, 8 AM PT), so this separate nudge would double up. Re-enable under Editor → Telegram bot config → Prayer nudge bot if the day ever comes that we want the second touch again.
• What it did: Posted the daily prayer-and-thanksgiving reminder into the main channel.
• Secret: TELEGRAM_PRAYER_BOT_TOKEN (still provisioned so flipping enabled: true brings it back without re-adding the bot to the group).
• Workflow: .github/workflows/daily-prayer-nudge.yml — still on the cron, but the script exits cleanly when enabled: false.

Bot 5 — Weekly prayer digest (disabled by default)

• What it does: Mon / Thu / Sat at 8 AM Pacific, posts a short summary of the prayer requests and thanksgivings shared in the Prayer & Thanksgiving topic since the last digest. Each entry is one bullet — attribution + a 1-2 sentence summary (~200 characters), never the full vulnerable text. Saturday's digest lands alongside the playlist digest so members see both as a single Saturday rhythm.
• Where: Prayer & Thanksgiving topic (thread 21).
• Schedule: 08:00 PT Monday, Thursday, Saturday. The first run after the system goes live (First_Run) does NOT post — it just marks the slot complete and starts the capture window from that moment, so going live doesn't dump a back-fill flood.
• Two-half pipeline: Telegram bots can't read history retroactively, so a continuous Poller runs every 15 minutes and writes captured prayers to assets/data/telegram-prayer-log.json. The triweekly Digest_Poster reads that log and posts on Mon / Thu / Sat. Both halves gate on the same prayer.digest.enabled flag.
• Summarizer modes: prayer.digest.summarizer in telegram-bot.json picks how each entry gets compressed. "rule-based" uses sentence-boundary truncation (no API needed, fully deterministic). "llm" calls Gemini 2.5 Flash via the GEMINI_API_KEY Secret for a 1-2 sentence summary in the human's voice — and gracefully falls back to rule-based on missing key, network failure, or content-filter trip. The digest always renders.
• Secrets: TELEGRAM_PRAYER_BOT_TOKEN (reused — same bot as the nudge above; no new bot needed). Plus GEMINI_API_KEY if running in "llm" summarizer mode.
• Workflows: .github/workflows/prayer-digest-poll.yml + .github/workflows/prayer-digest-post.yml
• Test it: Actions → Prayer Digest Poller → Run workflow → dry_run = true to verify auth without mutating the log.

{
  "schemaVersion": 1,
  "lastUpdateId": 84321,
  "lastModified": "2026-05-23T15:00:09Z",
  "optOut": [],
  "completedSlots": {
    "2026-W21-thu": { "since": "...", "messageId": 4731, "entryCount": 4, "postedAt": "..." }
  },
  "entries": [
    { "chatId": -1001234567890, "messageId": 4521, "userId": 987654321,
      "displayName": "Maria K", "kind": "telegram", "anonymous": false,
      "text": "stripped body for summarizer", "ts": "2026-05-21T18:42:00Z" }
  ]
}

Bot 7 — Saturday Discussion Icebreaker

• What it does: Every Saturday at ~9 AM Pacific, posts a single warm icebreaker question into the Discuss Scripture topic (thread 434), anchored in the week's three reading walks (NT, OT history, Poetry & Prophecy). The question is generated by Gemini from the 15 chapters Mon-Fri just covered; if Gemini is unreachable, falls back to a deterministic five-question rotation so the room always has a prompt.
• Where: Discuss Scripture topic (thread 434).
• Schedule: Saturday 09:00 PT, fired by the kickSaturdayIcebreaker Apps Script trigger. Lands ~1 hour after the daily Bible bot's morning post so the topic is the second thing members see, not competing for attention.
• Secrets: TELEGRAM_BIBLE_BOT_TOKEN (reused — same Bible bot as the daily reading post). GEMINI_API_KEY (optional; on missing key it gracefully degrades to the rule-based fallback rotation).
• Workflow: .github/workflows/saturday-icebreaker.yml
• Test it from Apps Script: open the Apps Script editor, function dropdown → run kickSaturdayIcebreakerTest. A clearly-labeled "(test)" preview lands in the Discuss Scripture topic within ~1 minute, using the most recent Saturday's readings if you're not running it on a Saturday. Bypasses the once-per-day dedup so you can hit the button as many times as you like while iterating on prompt or anchor.
• Test it from GitHub: Actions → Saturday Icebreaker → Run workflow → set test_run = true. Same outcome, available without opening Apps Script.
• Privacy: The LLM only sees chapter references (e.g. "Mark 12, 1 Samuel 24") — never user content. Same approval level as the prayer digest summarizer.
• Idempotency: The script writes a once-per-day entry into assets/data/telegram-bible-log.json after a successful real (non-test) post, so a duplicate kick on the same Saturday is a no-op. Test posts never write the dedup log.
• To turn it off: flip bible.saturdayIcebreaker.enabled to false in telegram-bot.json and commit. The next kick will exit cleanly without posting.

Bot 8 — Bible Donate / Receive (disabled by default)

• What it does: A public-facing intake at donate.html, reachable by a QR code printed on physical signs around Everett, Mukilteo, and Lynnwood. Two flows: Donate a Bible (coordination only — name, contact, count, drop-off vs pickup) and Receive a Bible (story-gated review — admin reads the story body, clicks Approve or Decline; decline is silent). Submissions land in a new Bibles Sheet tab; admin notifications go to seedthewordministry@gmail.com like every other email pipeline. Framed on store.html as the inbound paired path of the same distribution mission.
• Where: Form on donate.html. Audit trail in the Bibles Sheet tab. Admin notifications → seedthewordministry@gmail.com. Approve/Decline routes → web app doGet. Handoff form (post-approval) → web app doGet.
• Schedule: Form is event-driven (one POST per submission). A 30-minute cron (processBibleReviewReminders_) re-emails admins for any pending_review row that's been waiting more than 48 hours.
• Story gate: The receive flow's only required filter — beyond name + email + city — is the story field, bounded 80–1500 characters. Below 80 chars rejects (filters copy-paste spam visually). Above 1500 trims (bounds admin reading load). Anyone willing to write 80 honest characters about why they need a Bible passes.
• Decline behavior: Silent. The requester does not receive an email. The default-trust posture is "lean toward yes"; decline is reserved for clearly bad-faith submissions.
• Sign tracking: Each printed sign points at donate.html?sign=<id>. The Apps Script writes sign_id on every Bibles row so we can correlate which signs convert. Sign list lives at assets/data/sign-locations.json; QR SVGs at assets/images/sign-qr/<id>.svg. Re-run scripts/generate_sign_qr_codes.py after editing the JSON.
• Privacy: Mailing addresses are collected ONLY post-approval, on the handoff form, and ONLY when the requester picks "mail". Pending and declined rows never have an address on file.
• Secret: BIBLE_REQUEST_REVIEW_SECRET — new HMAC signing key for approve/decline/handoff tokens. Generate with openssl rand -base64 32.
• Lives in: docs/apps-script/order-handler.gs (extends the existing web app) + assets/js/donate.js + donate.html + assets/data/sign-locations.json.

Bot 6 — Prayer Request Intake (disabled by default)

• What it does: Two cards on community.html (under the live Telegram dashboard) open a quiet modal where members can submit a prayer request or a thanksgiving announcement. Each Submission is appended to a private Prayers Sheet tab (audit-only — admin eyes only), then relayed into the Prayer & Thanksgiving Telegram topic (thread 21) using the same (via the website) marker the Bot 5 digest already recognizes. Submitters who shared an email get a four-step encouragement drip (Day 0 confirmation, Days 3, 7, 14) with one-click unsubscribe baked into every message.
• Where: Form on community.html. Telegram relay → Prayer topic (thread 21). Drip → email via MailApp. Unsubscribe → web app GET handler.
• Schedule: Form is event-driven (POST per submission). Drip cron fires every 30 minutes via Apps Script time trigger.
• Producer ↔ consumer contract: This intake is the producer half whose consumer is Bot 5. The two are wired together by the literal (via the website) substring set at prayer.intake.marker here AND at prayer.digest.websiteSubmissionMarker in the digest spec. Editing one without editing the other to the identical value breaks recognition — the digest will silently skip every website submission. The _help note in telegram-bot.json repeats this warning at the top of the prayer.intake block.
• Audit-first ordering: The handler always appends the Prayers row BEFORE calling Telegram. If Telegram fails, the row stays with telegram_status='failed' and the form shows a soft "received but not yet visible" message. A Submission can never produce a Telegram message without a corresponding audit row.
• Secret: TELEGRAM_PRAYER_BOT_TOKEN (reused — same bot as Bot 5; no new bot needed). Plus a new HMAC signing key, PRAYER_INTAKE_UNSUBSCRIBE_SECRET, used to sign the per-Submission unsubscribe tokens.
• Lives in: docs/apps-script/order-handler.gs (extends the existing web app) + assets/js/prayer-intake.js + docs/apps-script/prayer-drip-templates.json.

Bot 7 — Layered Bible Reading Plan (ships enabled)

• What it does: Adds a quiet "🌿 Going deeper today" row on community.html directly below the existing weekly NT-strip card, and a matching short footer on the Bot 2 Bible post for Mon–Fri. Up to four pills per weekday: OT walk (Genesis–Esther, one chapter/day), Poetry & Prophecy (Job, Ecclesiastes, Song of Solomon, Isaiah–Malachi excluding Psalms and Proverbs, one chapter/day), Psalm of the day, Proverb of the day. Saturday and Sunday: the row does not render and the Telegram footer is omitted (Sat keeps its Study Saturday Live post unchanged; Sun the bot does not run).
• What stays untouched: the existing NT walk in assets/js/bible-plan.js is frozen — same anchor (Mark 11 on Thu Apr 30 2026), same sequence, same date math. The Saturday Review block in assets/js/study-saturday.js + assets/data/study-saturday.json is also frozen — same two pills, same JSON keys, same admin schema. No admin action against either of those is part of this feature.
• Where: Front-end: community.html + assets/js/layered-plan.js + CSS in assets/css/main.css. Telegram: extends .github/scripts/post_daily_bible_to_telegram.py (GitHub Actions Mon–Fri runner) AND the dailyBibleBot flow in docs/apps-script/order-handler.gs (Apps Script time-trigger backup). Both ports read the same config block and produce byte-equal chapter references.
• Schedule: Website renders on every page load of community.html. Telegram footer rides along on Bot 2's existing Mon–Fri 8 AM PT cron — no new schedule.
• Newcomer page: a separate canonical page at start-here.html renders the locked 30-entry plan from assets/data/newcomer-30day.json. Reader-relative — day 1 is whatever day the reader picks it up. The QR card on bundles (guide-newcomer-qr) points at this URL.
• Lives in: assets/js/layered-plan.js, assets/data/newcomer-30day.json, start-here.html, plus the bible.layeredPlan block in assets/data/telegram-bot.json.

Adding a Spotify episode for a specific chapter

1. Open assets/data/bible-spotify-map.json in the repo.
2. Inside "chapters", add an entry keyed by the exact reading label from bible-plan.js. Examples: "Mark 16", "1 Corinthians 13", "John 3".
3. Value is the full Spotify URL (episode preferred, show is fine too).
4. Remove the __example_Mark 16 key that's there as a placeholder.
5. Commit. The next Bible post that matches that chapter will use your link; chapters you haven't mapped still post with the default show URL.

Troubleshooting — the Telegram workflow failed, what now?

Turn a bot off, change its topic, or change a schedule

• Pause a single bot: set "enabled": false in its section of telegram-bot.json, commit. The scheduled workflow still runs but exits without posting.
• Change destination: update chatId or messageThreadId in the relevant section, commit.
• Change a schedule: edit the cron line in that bot's workflow YAML. Reminder: cron uses UTC, so PT hours need a +7 (PDT) or +8 (PST) offset.

Adding a new bot to the system

1. Create it with @BotFather → /newbot. Save the token.
2. Add the bot to @seedtheword and promote it to admin with "Post Messages" permission.
3. Add the token to repo Settings → Secrets and variables → Actions with a new name like TELEGRAM_XYZ_BOT_TOKEN.
4. Ping the dev on duty to add a new section to telegram-bot.json and a new workflow under .github/workflows/.

🔐 Where secrets live (NOT here)

We intentionally don't store API keys, passwords, or tokens on this page. Secrets live in:

• GitHub Secrets (repo → Settings → Secrets) — used by Actions
• Service dashboards (rss.app, Formspree, etc.) — each has its own login
• The ministry's shared password manager (Bitwarden, 1Password, or similar — set this up if you haven't)

📝 Recent changes

Big-picture history of what's on the site and when it was set up:

• May 2026 (current) — Site-wide reorganization. Homepage showcase renamed to "Featured Ministry Feed" with a 9-category rotation (announcements, outreach, highlights, store, ministry initiatives, Friends in Jesus, today's verse, How We S.E.E.D., tips/resources) pulling live data from each source. Path of Light waypoints renamed to Plant the Seed / Water to Grow / Gather the Harvest. About page restructured: "About S.E.E.D. Ministry" → "Our S.E.E.D Story"; the 9 stitch tiles' bottom row rewritten to the three phases; "How We S.E.E.D." cards rewritten (Bible reading, fellowship schedule, Study Saturdays, Prayer & Worship with Philippians 4:6-8 and John 4:23-24, Outreach); Contact heading renamed to "Contact us - @seedtheword". Community page got a 4-up platform CTA row (Telegram / Spotify / Twitch / Instagram) with equal billing, replacing the old Telegram-only big card; "Daily Touchpoints" renamed to "Learn more about us online". Study Saturday livestream card now merges the weekly review (Old/New Testament passages) into one card. Admin editor got a structured form for the Telegram bot config (all three bots + quiet hours + reminder minutes), the Recommendations legacy copy-paste flow was retired (legacyCopyPaste flipped to false), and cache busters bumped to v=12. Mobile: seed-story tiles now open on tap (or keyboard Enter/Space) — no longer hover-only.
• May 2026 — Homepage rebuilt as Hero → Featured From Our Ministry → Walking the Path of Light. Dropped the separate "Today at Seed the Word" dashboard section (Showcase Carousel already covers rotating content). News page gained "Ministry Outreach & Highlights" (3 carousel cards + existing 9-tile grid); removed "Ways to Help". Calendar events now have a 📣 Share Event dropdown (Telegram, WhatsApp, Instagram, Device share, Copy) that pre-fills the ministry's announcement template with Apple/Google maps links. News page has Open Graph tags for rich link previews on Telegram. Admin help got a searchable interface, Mermaid flowcharts, and an interactive Recommendations builder with live Spotify/YouTube previews.
• May 2026 — Store page rebuilt around three tone-differentiated bundles (Essentials, Life Group, Ministry calling). Each bundle card has a rotating slideshow powered by per-folder images.json manifests. Store header renamed to "Love. Gift. Repeat — that's Jesus." Added support-the-ministry PayPal quick-give panel. Bundle-builder page rebuilt to match aesthetic.
• May 2026 — "A message from our friend, Ruslan Y." permanent video card added to Community page. Partner Ministries + What We're Listening To migrated from JS arrays to assets/data/recommendations.json (admin-editable via the builder tool). Media drop folded into the News outreach callout with Google Forms integration.
• May 2026 — Added Spotify podcast embed, 4-icon header/footer socials, mobile nav fix, announcement timezone fix, 3-column contact section with Formspree. Fixed livestream "OFFLINE" showing on Saturdays before 7 PM PT.
• April 2026 — Community page redesign (Discussion, Stay Connected, Friends in Jesus), Instagram feed via rss.app, bible-reading plan, Showcase Carousel on homepage, calendar event modal with 5-tier color codes, month-themed calendar backdrops.
• Earlier — Initial site build, Netlify CMS setup then removed, Google Calendar integration, ministry highlights grid.

🆘 If everything is on fire

• The site deploys from main. To revert a bad change: repo → Commits → find the last good commit → "Revert."
• If you can't figure out what broke, email the dev on duty. Include a screenshot of the broken page and the browser console if possible.