What's Carrying Over
The integrations and behind-the-scenes functionality moving from the current site to the new one
These are the systems the current site relies on. Each one needs to make the trip to the new site. Some are visible (the donation form, the dining center finder); most run quietly in the background. The goal of this page is to make sure every one of them is accounted for.
No credentials here
This page describes what each integration does, not how to access it. Account IDs, API keys, and other credentials are managed separately and securely. They don't live in documentation or the codebase. When it's time to connect each service on the new site, we pull those from a secure store.
Donation & giving
The current site runs more than one giving platform, which is worth untangling before the rebuild.
| Platform | What it does | Status |
|---|---|---|
| Blackbaud | Powers donation forms and the Sustainers Circle donor portal (recurring giving, payment management, giving history) | Carrying over |
| FundraiseUp | A second donation platform loaded across the current site | To confirm Present in the current code; verify whether it's actively powering donations or is leftover from a past setup |
| Double the Donation | Employer matching-gift lookup (the "does my employer match?" tool) | Carrying over |
Open questionfor MOWP
Which donation platform is the active one? Blackbaud and FundraiseUp are both present on the current site. We need to confirm which is the primary, active system before wiring up the new site. We don't want to drop a working giving path, or carry over one that's no longer used.
Email & marketing
| System | What it does |
|---|---|
| Constant Contact | Newsletter signups and email marketing lists. The newsletter signup form on the new site needs to feed the same list. |
| Postmark | Transactional email: form notifications, confirmations, and receipts the site sends on its own. |
Locations & maps
| System | What it does |
|---|---|
| Dining center locator | The current 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 on the new site. See the Find a Dining Center outline for the proximity-vs-grid discussion. |
| Maps | The new locator's map is built on Mapbox rather than an embedded Google Map, for three reasons: the map can be styled to match the site's brand instead of looking like a pasted-in Google widget, it doesn't load Google's cookies and trackers (which keeps the consent banner footprint smaller), and it's cheaper at this site's traffic levels. "Get directions" links still open the visitor's default maps app (Google or Apple Maps) on their device. |
Analytics & marketing tags
The current site has several measurement and advertising tags in place, managed through a tag manager so they're easy to maintain. On the new site they load behind the consent banner — see Privacy & Consent for how that works.
- Google Analytics / Google Tag Manager: site traffic and behavior Carrying over
- Meta (Facebook) Pixel: ad measurement and audiences Carrying over
- The Trade Desk: advertising measurement To confirm If the campaign that placed it has ended, the cleanest move is to not carry it over at all
See Recommended Tools for 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 the full context on where toolbars fit. | Yes. The new site is built to strong accessibility standards on its own, and Recite Me carries over on top of that as an extra layer for visitors who rely on it. |
| Google Translate (GTranslate) | The current site's translation approach. | Yes, translation carries over alongside the toolbar. |
Forms
The current site collects submissions through several forms: Contact, Request Meals, Volunteer Sign Up, and Contact for Help. On the current site these are captured and emailed to staff. The new site captures submissions natively (stored in the CMS and sent as notifications), so submissions are stored, not just emailed.
Content systems
These aren't third-party tools, but they're structured content types that must be carried over rather than rebuilt from scratch:
- News & Events: news posts and event listings (see Navigation)
- Dining centers: the full set of location records
- Programs: the additional programs (Medically Tailored Meals, Diners Club, Friendly Chats, and the rest)
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 that alert us the moment something misbehaves