Eta Eta Lambda · Website review

Two options for annapolisalphas.com

Both options are complete working websites built from the chapter’s real content and hosted free on Cloudflare. Please explore each one, then share which direction you prefer.

Preview prepared November 17, 2026. The live Wix site has not been changed.

Classic option home page on a desktop screen
Classic option on a phone

Option A · Familiar

Classic

A faithful recreation of today’s Wix site, rebuilt for speed, accessibility, and mobile. Members will recognize it immediately.

Open the Classic site

https://annapolisalphas-classic.pages.dev

Modern option home page on a desktop screen
Modern option on a phone

Option B · Redesign

Modern

A new, premium design: historic legacy meets modern presentation, with an events calendar, interactive history timeline, and photo gallery.

Open the Modern site

https://annapolisalphas-modern.pages.dev

What’s different

AreaClassicModern
Look & feelSame layout, colors, gold section bands, and menus members already knowNew premium design: black and old gold, serif headlines, generous spacing
Home pageHero photo, history card, event flyers, recent activities, national programsInteractive 3D chapter seal, stats, announcement bar, events, programs, news, ways to get involved
Events"Upcoming Activities" flyer wall; past flyers drop off automaticallyFilterable calendar, event detail pop-ups, add-to-calendar (Google / .ics), shareable event pages
HistoryCharter video, officers, lineage and past presidents in expandable panelsInteractive decade-by-decade timeline built from the lineage and presidents records
NewsMedia Center with categories, tags, and photo galleries (all 184 posts)Newsroom with category filters, related stories, and a dedicated Gallery of 136 albums
ProgramsOriginal program pages (Alpha Academy, Brothers Keeper, VPHP, GTHS)Program hub plus detail pages for all five programs, with related stories
MobileFaithful but fixed: no overlapping footer or empty gaps from the Wix mobile viewDesigned mobile-first with a slide-out menu
URLsKeeps the existing Wix addresses (/about, /post/…, /media-center…)New, cleaner addresses; every old Wix address redirects automatically

A closer look

Current Wix home page
Today (Wix) for reference
Modern events calendar
Modern: events calendar with filters
Modern history page with interactive timeline
Modern: history and timeline

Included in both

  • Both sites read the same content files: posts, events, announcements, officers, committees, lineage, and programs.
  • Chapter members update content once (through Pages CMS or GitHub) and both sites rebuild automatically.
  • Contact form with spam protection stores messages in a free Cloudflare D1 database.
  • Hosted on Cloudflare Pages free tier: $0/month. No Wix plan is required for the public site.
  • Accessibility: keyboard navigation, screen-reader labels, reduced-motion support, and AA color contrast.

Known limitations

  • Member-only area (directory, profiles, officer dashboards) is not migrated. It still runs on Wix and needs a separate plan before the domain moves.
  • Post photo galleries (about 6,200 photos) still load from Wix’s image servers. They must be copied before Wix is cancelled (step in the migration plan).
  • Wix-only features are not reproduced: post likes, view counts, comments, and the Instagram feed widget (it showed no posts on the live site).
  • The chapter’s social media accounts are not linked anywhere on the current site, so the new sites leave them blank until leadership provides them.
  • Wix Contacts sync: the current contact form feeds Wix Contacts, which the chapter’s contact list app pulls weekly. The new form stores messages separately.
  • These are preview sites on temporary addresses. annapolisalphas.com is unchanged and still served by Wix.

Questions for leadership

  1. Which option should become annapolisalphas.com: Classic or Modern?
  2. Which social media accounts should the site link to?
  3. Where should the members-only area live going forward (keep on Wix at a members subdomain, or rebuild later)?
  4. Who should receive contact-form messages, and should they also flow into the chapter’s contact list?