Skip to content
View packages

GoSeedly Dance Studio 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 family creation, edits, the season class store and resource setup. They preserve native account permissions, unrelated custom fields and row history, enforce the season rules and the children’s data guard on the server, 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 Season enrolment, Trials and enquiries, Recital preparation, Studio accounts. 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 24 fictional families holding 38 dancers across 14 weekly classes: 4 classes full with waitlists totalling 9, 6 trials inside the week, 10 classes with a costume of which 2 are past their order-by date, and 5 families past due beyond their grace days. 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.

  • Trial class request
  • Season enrolment request
  • Recital volunteer sign-up

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

02 / WORKING DOCUMENTS

Three reusable templates.

  • Class roster sheet
  • Costume order summary by class
  • Recital day call sheet

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-dance-studio/config.ts to set studio name, descriptor and default pipeline name, 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 opportunity is one family. It holds the household label, guardians with a relationship label and a preferred-contact flag, dancers as a first name and an age band label, class places with a status, a costume step, a size label and recorded absences, the tuition plan with its recorded state and grace days, ticket reservations, a volunteer role, the enquiry and trial steps with their dates, and an editable checklist.

A dancer is a first name and an age band label. The kit stores no date of birth, no age in years, no medical, allergy or injury note, no photograph, no school name and no custody detail, and every free-text field refuses the obvious accidental entries in the browser and again on the server. That is a guard against accidental entry, not a guarantee. A costume is flagged the day after its recorded order-by date while a dancer is still short of ordered, and tuition is flagged only beyond the grace days the office recorded. There is no online registration or booking engine, no tuition billing, autopay or payments, no ticketing or seat maps, no costume vendor ordering integration, no attendance check-in kiosk, no parent portal, no automated messaging and no scheduling engine.

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 Dance Studio Kit