Make the workspace
feel like your team.
Edit apps/web/components/devlaunch-dog-breeder/config.ts to set business 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 record is a litter, a family or a breeding dog. A litter holds the litter letter, breed, dam and sire call names, an outside stud's owner, the bred date, the due date as you recorded it, the whelp date, the first go-home day, the price as recorded and its puppies, each with collar color, sex, coat color, birth weight in ounces, status, the family it names, go-home and gone-home dates and a vet visit recorded date. A family holds the inquiry, application and decision dates, the litter it waits for, the pick number and deposit as recorded and its preferences. A breeding dog holds its call name, sex, registration label as recorded, health testing as typed and heats. Every record has an editable checklist.
Whelpline records what your program wrote down. It is not a health record, a registry, a contract or a payment tool: it calculates no due date, reads or verifies no health test, registration or pedigree, makes no health guarantee and no veterinary claim, takes no deposits or payments and sends no calls, texts or emails. Medications, doses and vaccine entries are refused in notes; card numbers, bank and routing numbers, Social Security numbers, kennel and gate codes and registry or payment app logins are refused in recorded text, names included, and in the native form drafts, in any casing, while microchip numbers, registration labels, weights, prices and deposits are kept. It is a guard against accidental entry, not a guarantee.
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.