WEBSITE PROPOSALPrepared by Unstuck · Lodge approval pending
Mount Shasta ElksLodge No. 2333 · California
A PROPOSAL FROM UNSTUCK

Less busywork.
More time for the lodge.

Start with a helpful website. Add practical automations around the way your officers and volunteers already work.

Today: a simple place to start.

This demo includes lodge information, directions, official Elks links, and a sample calendar. It is a proposal, not an official replacement website. No member records are collected and no automated messages are sent.

PHASE 1 · ONE RELIABLE CALENDAR

Enter an event once.

Give a designated officer a simple editor for dates, menus, reservations, and cancellations. Separate public listings from member-only information. Let members subscribe to the approved calendar.

Needed: a calendar owner, current event source, and agreement on what can be public.

PHASE 2 · HELPFUL REMINDERS

Prepare. Review. Send.

Turn approved events into draft email reminders and Facebook announcements. An officer reviews each message before it goes out. Track delivery and prevent duplicate sends.

Needed: authorized account access, an approved mailing list, communication preferences, and a reviewer.

PHASE 3 · VOLUNTEERS & RESERVATIONS

Make the handoff easier.

Collect event RSVPs and volunteer availability, maintain a waitlist when needed, and provide a kitchen or attendance count. Add online payments only if the lodge chooses them.

Needed: capacity rules, an organizer, and reservation and cancellation policies.

PHASE 4 · A MONTHLY RHYTHM

Draft the newsletter.

Assemble upcoming events and approved updates into a newsletter draft. Remind officers about agreed deadlines and provide a handover guide for the next volunteer team.

Needed: newsletter format, deadlines, approved photos, and publishing ownership.

Five things to discuss tonight

  1. What repeated task takes the most time each month?
  2. Who owns the calendar, newsletter, and Facebook page today?
  3. Which events and details belong on a public website?
  4. Can the secretary share the current bylaws, house rules, and communications policies?
  5. Who should approve updates, and who is the backup?

A foundation that can grow.

This demo uses Next.js on Cloudflare Pages. A later backend can use Cloudflare Workers for workflows, D1 for event and delivery records, Queues for jobs, and scheduled triggers for reminders. Staff access and an audit trail come before connecting member information or outbound messages.

Choose the first automation after the lodge identifies its biggest source of busywork. This proposal does not commit the lodge to service fees, a delivery timeline, or third-party services.

What we found online

Facebook: bpoe2333 is linked by the lodge’s official Elks page. Other local social accounts have not been verified. The existing resources page has a malformed Facebook URL; this demo uses the address shown on the lodge’s dedicated Facebook page.

Official lodge website · Official calendar · Elks marketing resources