Skip to content
View packages

GoSeedly Campground & RV Park Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original backend helpers are required for connected booking creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep every figure in its own unit, refuse access codes, passes, Wi-Fi passwords, logins, card numbers, Social Security numbers and other ID numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Reservations, Seasonal and monthly guests, Groups and rallies, Site upkeep. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore one fictional season, mid-April to mid-October, on 22 sites: 32 bookings in all, with 4 seasonal guests, 2 monthly guests, 3 groups and rallies, 5 upkeep jobs and 18 nightly bookings. Each booking shows from the date it was booked, so a summer date fills the grid and an off-season date shows next season's renewals and early reservations. Sample edits stay in memory and reset on navigation or reload. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

MORE OF THE WORKING DAY

From the first inquiry
to the final handoff.

Editable native forms and document templates give your team a practical starting point.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • Reservation request
  • Seasonal and monthly site inquiry
  • Group or rally request

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Arrival sheet
  • Seasonal site agreement outline
  • Group block summary

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

Checklists alongside the work.

Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.

Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-campground-rv-park/config.ts to set company name, descriptor, default pipeline name, the park's season and its own site list, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

One contact-linked booking holds the kind (nightly, monthly, seasonal, group or rally, site upkeep), the guest or group, how they found the park, party counts and labels for pets and vehicles, the rig with its length, slide-outs and the power it needs, the recorded rate and its period, for seasonal and monthly guests the agreement dates and the renewal answer with its date, every stay with its site, arrival, departure, expected arrival time and status, every out-of-service window for upkeep, every payment line with its due and paid dates as recorded, and an editable checklist.

Sitepost records sites, stays, agreements, group blocks and upkeep as your office typed them. It takes no payment or deposit, runs no online booking, holds no site by itself, sends no confirmations or reminders, opens no gate and issues no codes or passes. It never says a site, hookup, road, rig or stay is safe, permitted, inspected or compliant with any health, fire, electrical or park rule, and an agreement here is your office's record, not a lease. The season follows the open and close dates your park records, with an honest off-season board. Gate, bathhouse, laundry and cabin codes, passes, Wi-Fi passwords, logins, card numbers and Social Security numbers are refused in recorded text and in the native form drafts, while site numbers, amps, rig lengths, plates, counts and prices are accepted.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.

See the interface and everything included.

Back to GoSeedly Campground & RV Park Kit