Community Garden Plot Booking Web App with Watering Rota and Harvest Log

PlotShare, the Community Garden Plot Booking Web App with Watering Rota and Harvest Log, is a web application that lets a community garden publish a map of its plots, take bookings for a season, run a shared watering rota, and record every harvest pick with its quantity. A gardener opens the plot grid, sees at a glance which plots are available, booked, waitlisted, or under maintenance, and books a free plot or joins the waitlist for a taken one. Once booked, the gardener joins a rota group that waters on fixed days, swaps slots when away, and logs each harvest with crop, quantity, and date, so the garden always knows who holds which plot, whose turn it is to water, and what each plot produced. A delivered garden starts empty, while the demo preview shows a labelled seed garden so every screen can be checked at a glance.

Community gardens usually run on a noticeboard, a group chat, and a spreadsheet that only one person understands. Plots sit empty while a waiting list lives in someone's messages, watering depends on whoever remembers, and nobody can say at season's end what any plot actually grew. The failure is not effort — volunteers work hard — it is shared memory: bookings, watering turns, and harvests are recorded in three different places, or nowhere at all. PlotShare replaces that scattered record with one visible system: the plot grid is the booking record, the rota is the watering record, and the harvest log is the production record, all readable by every gardener in the group.

This is a built-to-order software project: the web app source, the working single-file demo preview, and the complete documentation kit are prepared fresh for you. To order, request a WhatsApp quotation stating your scope (the base app, plus any optional features you want), and you will receive a price and a delivery timeline before any build starts.

From a newcomer arriving at the garden to the season's last harvest, the flow has six stages and no stage depends on memory. The organiser sets up the garden's plots on the grid with sizes and states, and a gardener browses the map to find a free plot or a waitlist worth joining. Booking fixes the gardener to a plot for the season and places them in that plot's rota group, which waters on fixed days and swaps slots when someone is away. While the season runs, the rota page shows whose turn is due, missed waterings surface as alerts, and every pick is logged with its quantity. At season's end, the harvest log totals what each plot produced, the organiser closes the season, and plots return to available or maintenance for the next round.

1. The organiser sets up the garden's plots on the grid, each with a size and a state: available, booked, waitlisted, or under maintenance.
2. A gardener opens the plot grid, clicks a plot to see its holder and booking state, and books a free plot or joins the ordered waitlist for a taken one.
3. Booking places the gardener in that plot's rota group, which waters the group's plots twice a week on fixed days.
4. When a gardener cannot make a slot, they offer it to the group as a swap before the day arrives; the group sees the open slot and covers it.
5. If a plot goes unwatered past its crop's interval, it appears on the missed-watering alerts list with the days since its last watering.
6. Each harvest is logged with date, plot, crop, and quantity in kilograms, and the log totals every plot's production for the season.

Tech stack:

• HTML · CSS · JavaScript
• Node.js · Express
• SQLite database
• REST API endpoints
• Responsive CSS grid layout
• Git · VS Code editor
• Single-file HTML demo preview

Four capabilities carry this app. First, the plot-grid map: the garden's plots appear as a colour-coded grid showing available, booked, waitlisted, and maintenance states, so a newcomer can see in seconds where space exists without asking the organiser. Second, season booking with a waitlist: a gardener books a free plot or joins an ordered queue for a taken one, and the queue advances automatically when a plot frees up. Third, the shared watering rota: booked plots are watered on fixed group days, slots can be swapped before the day arrives, and missed waterings surface as alerts. Fourth, the harvest log and seasonal calendar: every pick is recorded with plot, crop, quantity, and date, and a crop calendar shows what to sow and harvest in each season. Together they replace the noticeboard, the group chat, and the single-person spreadsheet with one record every gardener can read.

• [Plot-grid map with availability] The garden's plots appear as a colour-coded grid — available, booked, waitlisted, or under maintenance — and clicking a plot shows its holder and booking state. The demo seed shows 24 plots, with 12 booked, 6 available, 4 waitlisted, and 2 under maintenance.
• [Season booking with waitlist] A gardener books a free plot for the season or joins an ordered waitlist for a taken plot, and the queue advances when a plot frees up. In the demo, Plot A3 carries 2 people waiting, and Plot D3 carries 3.
• [Shared watering rota with swaps] Booked plots are watered twice a week by rota groups on fixed days, and a gardener who cannot make a slot offers it to the group as a swap before the day arrives. The demo rota week runs from 2 Nov 2026 with 5 watering days.
• [Missed-watering alerts] A plot whose last watering is older than its crop's interval appears on an alerts list with the days since watering, so a dry plot is visible to the whole group. The demo seed shows 3 alerts, including Plot B3 tomatoes unwatered for 4 days.
• [Harvest log with quantities] Every pick is logged with date, plot, crop, and quantity in kilograms, and the log totals each plot's season production. The demo seed logs 6 picks totalling 15.1 kg in October 2026, led by 4.2 kg of tomatoes from Plot A3.
• [Seasonal crop calendar] A season guide shows what to sow and harvest in winter, summer, and monsoon months, helping gardeners plan the next planting. The calendar is a planning guide, not a yield promise, and the garden organiser can edit its entries.
• [Builder note — why the rota is shared, not private] A watering slot is a shared duty, not a private reminder: the rota only works because a missed slot is visible to the whole group, so swaps are offered to the group before the day arrives rather than discovered afterwards. That visibility is the project's key mechanism line, and it is why missed-watering alerts go to the group, not to one phone.
• [Admin controls — optional, not in the base build] Garden-admin controls such as plot creation, season dates, and member approval are an optional add-on, clearly separated from the base build. The base build ships with one organiser account and a fixed demo garden layout.

• Complete web app source code (plot grid, booking and waitlist logic, rota with swaps, harvest log, crop calendar)
• Working single-file demo preview of the app's flows, with the frozen seed garden of 24 plots
• Setup guide for running the app locally and hosting it online
• Project report PDF (background, problem, methodology, architecture, results, limitations)
• PPT presentation for final review
• Viva Q&A preparation document (booking state machine, rota swap design, harvest aggregation, SQLite schema)