Add a Support Saba donations page (/donate)

[spizeck]

Goal

Add a public Support Saba page at /donate that helps Sea Saba visitors give back to the island while also giving Saba organizations, groups, and community projects a clear way to request support from Sea Saba.

This is a two-sided community-giving program:

1. Visitors can discover vetted Saba organizations and donate directly to those organizations.
2. Saba organizations, groups, and projects can request support from Sea Saba.

Sea Saba does not process visitor donations.

Visitor donations

Use a typed recipient registry and fail safely when no approved recipients are configured. Do not invent organizations, donation URLs, nonprofit/tax status, descriptions, amounts, or other claims. Partners already present elsewhere in the repository are not automatically approved donation recipients.

Each published recipient should have owner-approved:

• organization name
• short description
• category/focus
• official direct donation URL or payment method
• optional approved logo/image
• any required wording or restrictions

Candidate recipient outreach, September 27, 2026

Current candidates identified for a balanced first group:

• Sea & Learn Foundation: environmental/cultural education, science and community programming. Draft email prepared from chad@seasaba.com to info@seaandlearn.org asking them to confirm their official donation link, preferred description, imagery, and wording.
• Saba Reach Foundation: employment, education, youth/community programming. Draft email prepared to director@sabareach.org asking for the official donation/payment method, preferred description, imagery, and wording.
• Saba Conservation Foundation (SCF): marine and terrestrial conservation. Draft email prepared to info@sabapark.org asking them to confirm the official donation link, preferred description, imagery, and wording.
• Child Focus Foundation: children and after-school/community programming. Draft email prepared to childfocussaba@gmail.com asking for the official donation/payment method, preferred description, imagery, and wording.
• Body, Mind & Spirit (BMS): health, inclusion and community wellbeing. Chad contacted a BMS board member directly. She will get back to him. Do not add BMS to the live recipient registry until the organization supplies/approves the relevant donation details and wording.
• SFPCA: animal welfare. SFPCA is currently in a period of organizational upheaval. Do not pursue or publish them now. Keep them as a future candidate and revisit once the organization is settled and can provide an approved direct donation method and wording.

Potential future/secondary concept:

• Project Bureau Saba / Sea Fan Society Foundation may be useful as a route for grassroots/local projects that do not have a large organizational structure. This needs separate owner review before inclusion and should not automatically be treated as a standard donation recipient.

Do not scrape or infer bank details. Do not publish a recipient until Sea Saba has a direct, organization-approved destination for the visitor's donation.

Request support from Sea Saba

Allow local organizations, groups, and projects to request support such as:

• financial support or sponsorship
• goods or supplies
• raffle prizes
• Sea Saba services
• staff/community participation
• other appropriate in-kind help

Keep the process friendly and proportionate rather than bureaucratic.

Ground rules:

• clear benefit to Saba
• a clear project and someone responsible
• Sea Saba can understand where support goes
• projects/community benefit rather than unrestricted personal cash gifts
• prefer direct supplier payment, purchasing, or provision of services when cleaner
• reasonable follow-up afterward, such as a receipt, photo, or short update

Small requests, small follow-ups.

Do not promise funding or support, invent budgets/deadlines, or imply every request will be approved.

Submission architecture

For the initial implementation, use the same email/WhatsApp handoff approach as the existing contact experience rather than creating a new server-side email identity path. The user should be able to send the request from their own email client, including attachments if needed.

Issue #104 tracks the future Respond.io Custom Channel architecture and may later provide a better server-backed submission path without collapsing different visitors into a shared sender identity.

Privacy and analytics

Do not send applicant PII into GA4/GTM/Vercel Analytics. Generic events such as donation_request_started and donation_request_submitted are acceptable without personal fields.

Keep privacy documentation consistent with the actual submission mechanism.

Current implementation

PR #172 implements the page and remains under owner review. The page includes the two-sided program, typed/fail-safe recipient data, support-request workflow, privacy/analytics treatment, responsive polish, and footer entry point.

The footer should contain Support Saba once under Plan Your Trip, after Recommended Partners. Visiting Yachts remains under Explore.

Before publishing recipients

• Wait for replies/confirmation from the contacted organizations.
• Owner-review all organization descriptions and destination URLs.
• Add only recipients with verified direct giving details.
• Keep SFPCA deferred until its organizational situation stabilizes.
• Keep BMS pending the board member's response.