What's Carrying Over
The integrations and behind-the-scenes functionality moving from the legacy site to the new one
The systems the legacy site relies on, and what happens to each. Some are visible — the donation form, the dining center finder — and most run quietly in the background.
For who owns each account, see Third-Party Services.
This page describes what each integration does, not how to access it. Account IDs, API keys, and other credentials live in a secure store, not in documentation or the codebase.
Donation & giving
Giving runs on Blackbaud, with Double the Donation for employer matching and hosted tools from FreeWill, GiveSmart and PayPal alongside it. All of it carries over, along with the pages it sits on: gifts of stock, planned giving, donor-advised funds, corporate partnership, tribute and memorial gifts, and employer matching.
Giving online covers how the donation form works and how much of that experience can be ours. Giving tools covers matching gifts, planned giving and tribute tags.
One piece doesn't make the trip. The legacy site still loads a script for Fundraise Up, a second donation platform, but the account behind it no longer exists and nothing renders. It's dropped rather than moved.
Email & marketing
| System | What it does |
|---|---|
| Constant Contact | Newsletter signups and email marketing lists. The legacy site's WordPress plugin doesn't carry over, so the signup form is rebuilt to feed the same list. See Newsletter signup. |
| Resend | Transactional email: form notifications, confirmations, and receipts the site sends on its own. A delivery service, not a mailing list. |
Locations & maps
| System | What it does |
|---|---|
| Dining center locator | The legacy site has a proximity search (enter a location, set a radius). The location data — every center's address, hours, and contact details — carries over; the locator itself is rebuilt. See the Community Dining outline, where the map now lives. |
| Maps | The locator's map is built on Mapbox rather than an embedded Google Map: it can be styled to match the brand, it doesn't load Google's cookies and trackers, and it's cheaper at this site's traffic levels. "Get directions" links still open the visitor's default maps app. |
Analytics & marketing tags
The legacy site's measurement and advertising tags all carry over, managed through a tag manager. Here they load behind the consent banner rather than on every visit. See Privacy & Consent for how that gate works.
- Google Tag Manager: the container that loads everything below Carrying over
- Google Analytics: site traffic and behavior Carrying over
- Meta (Facebook) Pixel: ad measurement and audiences Carrying over
- The Trade Desk: advertising measurement Carrying over Still firing on every legacy page, so the campaign that placed it hasn't been turned off
Gifts are the blind spot in all of this: the donation form is an iframe, so analytics sees the path into a gift but not the gift itself. Giving online covers what that means for reporting, and Recommended Tools covers how to read the analytics once they're set up.
Accessibility & language
| Tool | What it does | Carries over |
|---|---|---|
| Recite Me | The accessibility toolbar (read-aloud, text resizing, color adjustments, translation). See Accessibility for where toolbars fit. | Yes, as a layer on top of the site's own accessibility work. |
| Google Translate (GTranslate) | The legacy site's translation approach. | Yes, translation carries over alongside the toolbar. |
Forms
The legacy site collects submissions through several forms: Contact, Request Meals, Volunteer Sign Up, and Contact for Help. Today these are emailed to staff. The site stores each submission in the CMS as well as sending the notification, so nothing depends on someone holding onto an email.
Volunteer sign-up is the exception. It runs on VolunteerHub, so those submissions live there rather than in the CMS. Volunteering covers why, and what the site can show without it.
Content systems
Structured content types that carry over rather than being rebuilt from scratch:
- News & Events: news posts and event listings (see Navigation)
- Dining centers: the full set of location records
- Programs: the program pages (Medically Tailored Meals, Diners Club, Meals 4 Kids, Friendly Chats, and the rest)
- Diners Club partner restaurants: the participating restaurants with address, hours, and menu highlights. Location records like the dining centers, not hand-edited page copy
- Press coverage: outside coverage of MOWP. These are link records (outlet, date, headline, URL) rather than posts, since they point at the outlet that published them
- Newsletter issues: the Motion back catalog as PDFs, with cover images. How far back the archive runs is a decision for MOWP; the files themselves carry over either way
- Seasonal logo variants: the legacy site swaps in special logo art for moments like Pride month. The site keeps that practice, with the variants managed in the CMS and scheduled to switch on and off automatically.
Infrastructure
Already in place and carrying over (covered in more detail under Resources):
- Cloudflare: CDN, DDoS protection, SSL
- Redis: caching for performance
- Media/asset storage: images served from cloud storage rather than the web server
- Automated backups: regular, restorable backups
- Monitoring & error tracking: uptime checks and error reporting. The uptime check polls a
/healthzendpoint rather than the homepage, so a slow page render doesn't register as an outage. That endpoint has to carry over with everything else, or the monitor goes dark at launch