Two gardeners talking beside wooden raised beds in a walled community garden

// Nonprofit

Boca Raton Urban Gardens

Nonprofit Website, Online Giving & Back Office on 27ERP

Built bocagardens.org for a 501(c)(3) community-garden nonprofit in Boca Raton, FL, and set the organization up on 27ERP: one-time and monthly gifts through Stripe Checkout on the nonprofit's own account, a season of 65 garden beds sold from an interactive plot map, workdays and events with tickets, and seven website forms that arrive as prospects in a back office that speaks nonprofit — supporters, proposals, funds received.

Garden Beds on the Plot Map

One-time + Monthly

Gifts on the Nonprofit's Own Stripe Account

Payment Keys on the Website

Website Forms That Become CRM Records

// Product tour

Inside the Build

Marketing site

bocagardens.org: the home page, the Give hub and donate page, events, the interactive plot map and the planting calendar.

Next.js 16Tailwind CSS v4MotionVercelwww.bocagardens.org

Boca Raton Urban Gardens home page with the garden hero and calls to rent a bed, volunteer and give — Home page: rent a bed, join a workday, give something that grows

The Give hub listing donations, engraved bricks, memorial trees and sponsorship tiers — The Give hub: donations, bricks, trees and sponsorships

The donate page with preset amounts, one-time or monthly, designation and tribute options — Donate: one-time or monthly, designation, tribute, cover the fee

The events page listing upcoming workdays and garden events with tickets — Events and workdays, read from 27ERP

The interactive plot map of the Susan Whelchel Community Garden showing available and taken beds — The plot map: 65 beds, availability from ticket stock

The South Florida planting calendar page — A South Florida planting calendar

Boca Raton Urban Gardens home page on a phone — The home page on a phone

Back office

27ERP set up as a nonprofit. These screens are from a fictional demo workspace with nonprofit wording — Supporters, Prospects, Funds received — not the client's data.

27ERPPostgreSQLGoogle Cloud Run

The 27ERP dashboard on a nonprofit workspace reading Funds received and Supporters — Dashboard: funds received, supporters, what needs attention (demo data)

The Donations list with totals raised, gifts and donors — Donations: every gift with totals and filters (demo data)

The customers list titled Supporters on a nonprofit workspace — Supporters: the customer list in the nonprofit's own words (demo data)

The events list showing a workday and a bed-season event — Events: a workday and a season of beds (demo data)

The articles list that publishes stories and news to the site — Stories and news, published from the back office (demo data)

// The problem · 4 pain points

The Challenge

A community-garden nonprofit in its second season needed its website to do real work: take gifts without a person in the loop, show which of its 65 beds were open and keep that in step with who had paid, sell seats to workdays and classes, and turn every volunteer, newsletter and sponsorship form into a record someone could follow up. Before giving moved onto 27ERP, a donation on the site was a pledge form, and staff emailed a payment link by hand.

Gifts needed a checkout

A donation was a pledge form followed by a payment link sent by hand, so monthly giving, tributes and designations all meant manual follow-up

65 beds, one season, a waitlist

Every bed's availability had to be visible on the site and stay in step with who had actually paid for the season

Workdays and classes with seats

Free and paid events needed sign-ups, tickets and a count of who was coming, without a second tool

One record per neighbor

A neighbor who gives, volunteers and rents a bed should be one supporter record, not three unrelated entries

// How it works

How It Works

The website holds no payment keys and no database of its own: every gift, bed, ticket and form goes through 27ERP's public API and lands as a record staff can work from.

Give

One-time or monthly, on the nonprofit's own Stripe account

Donate page

Amount, frequency, designation, tribute, cover the fee

27ERP checkout

The site posts the gift to the public donations API

Stripe Checkout

On the nonprofit's own connected account

Gift recorded

When Stripe confirms, once per monthly charge

Supporter

Matched by email, or created

01
Donate page
Amount, frequency, designation, tribute, cover the fee
02
27ERP checkout
The site posts the gift to the public donations API
03
Stripe Checkout
On the nonprofit's own connected account
04
Gift recorded
When Stripe confirms, once per monthly charge
05
Supporter
Matched by email, or created

Beds & events

A season of beds is one event with a ticket per bed

Season event

One event per garden season, a ticket type per bed

Plot map

Available, taken or not open, read from ticket stock

Reserve a bed

A one-seat order with a 30-minute hold

Stripe Checkout

Paid on the same connected account

Bed marked taken

Ticket stock updates the map on the next read

01
Season event
One event per garden season, a ticket type per bed
02
Plot map
Available, taken or not open, read from ticket stock
03
Reserve a bed
A one-seat order with a 30-minute hold
04
Stripe Checkout
Paid on the same connected account
05
Bed marked taken
Ticket stock updates the map on the next read

Forms & stories

Every form is a prospect; every story is an article

Website form

Contact, volunteer, newsletter, sponsor, brick, tree, waitlist

Turnstile

A bot check before anything is sent

Prospect in 27ERP

Tagged with the form it came from

Reply from the record

Two-way email on the prospect

Article in 27ERP

Stories and news drafted with a preview link

Published to the site

No redeploy; the site re-reads on a timer

01
Website form
Contact, volunteer, newsletter, sponsor, brick, tree, waitlist
02
Turnstile
A bot check before anything is sent
03
Prospect in 27ERP
Tagged with the form it came from
04
Reply from the record
Two-way email on the prospect
05
Article in 27ERP
Stories and news drafted with a preview link
06
Published to the site
No redeploy; the site re-reads on a timer

// What we built

Our Solution

Marketing Site

Next.js 16 site with Tailwind CSS v4 and Motion: gardens with an interactive plot map, events, stories and news, a South Florida planting calendar, and a Give hub for donations, engraved bricks and memorial trees. Deployed on Vercel, every form guarded by Cloudflare Turnstile. The site reads 27ERP server-side through its public tenant API and holds no payment keys of its own.

Giving Through 27ERP

The donate page posts to 27ERP's donations checkout, which opens Stripe Checkout on the nonprofit's own connected account: preset or custom amounts, one-time or monthly, a designation, an in-honor or in-memory tribute with a notification email, anonymous giving and an option to cover the fee. The gift is recorded when Stripe confirms the money, and the donor is matched to a Supporter or becomes one.

Beds as a Season Event

Each garden season is one event in 27ERP with a ticket type per bed. The site maps ticket types to beds on the plot map — available, taken or not open — and reserving a bed creates a one-seat order with a 30-minute hold and Stripe Checkout. A full season shows a waitlist form instead, which files a prospect.

Events & Workdays

Workdays, family days and classes are 27ERP events with free or paid tickets. The site lists them from the same records, takes the order, and 27ERP holds the seats and emails a QR ticket per seat.

Forms That Become Prospects

Contact, volunteer, newsletter, sponsorship, brick, memorial-tree and bed-waitlist forms post to 27ERP as prospects tagged with the form they came from, so a Volunteer sign-up never looks like a quote request. Staff reply from the record with two-way email.

Stories From the Back Office

Stories and news are 27ERP articles with drafts and preview links, published to the site without a redeploy. The workspace is set up as a nonprofit, so staff see Supporters, Prospects, Proposals and Funds received on the main screens instead of customers, leads, estimates and revenue.

// Technologies used