Locations and sources
Suggest a missing camp without changing the source catalog
Suggest missing camps from SummerCan setup without automatically publishing new sources or changing the global source catalog.
The problem
families need a safe way to send suggestions without giving every user source-admin control. For families and camp staff who notice a missing source, that means the hard part is not just finding camps; it is preserving the decisions that make the final family schedule trustworthy.
How SummerCan helps
SummerCan stores authenticated camp submissions for admin review instead of creating sources automatically. SummerCan is a planning tool: it helps organize discovery, comparison, review, and schedule output while leaving final provider confirmation with the family.
How it works
- Start with setup: children, date window, location/source choices, and unavailable blocks.
- Use discovery to open a chooser-ready set of camp groups and dated sessions.
- Choose and review camp interests before the schedule builder runs.
- Use the final schedule, share link, provider links, and calendar output as the handoff for real-world follow-through.
Feature-to-benefit table
| Feature | Why it matters here | Example |
|---|---|---|
| camp submission modal | Keeps the page focused on submit missing camp suggestion instead of generic camp browsing. | Open the setup plus card for a missing camp. |
| authenticated submission endpoint | Connects the family constraint to an observable planner surface. | Submit a camp name, URL, location, or note. |
| admin review queue | Turns reviewed decisions into a practical output families can inspect. | Let admins review suggestions before any source changes. |
Use-case examples
Initial setup
Open the setup plus card for a missing camp.
Decision review
Submit a camp name, URL, location, or note.
Schedule handoff
Let admins review suggestions before any source changes.
Objections and limitations
Is this a replacement for provider registration?
No. SummerCan helps with planning and schedule organization. The actual provider remains the source for enrollment, availability, pricing, and policy confirmation.
What about stale demo data?
The public app displays a frozen Summer 2026 catalog notice. Treat demo data as planning context and verify details before relying on them.
How private is a shared schedule?
Shared schedule links are bearer links. Send them only to people who should see the read-only schedule.
FAQ
How does SummerCan help with submit missing camp suggestion?
SummerCan stores authenticated camp submissions for admin review instead of creating sources automatically. The relevant product fit is camp submission modal, authenticated submission endpoint, admin review queue.
Does SummerCan book camps or guarantee availability?
No. SummerCan helps families organize discovery, comparison, preferences, and schedule output. Families should verify availability, pricing, policies, and enrollment directly with each provider.
What should a family prepare before using this workflow?
Have the children, ages, date window, unavailable blocks, and the locations and sources decision context ready before moving into camp choice and review.
Can the finished plan be shared?
Yes, finished schedules can be shared through a read-only schedule link, and calendar output is available from the result page when the plan is ready.
What makes this locations and sources page specific?
It focuses on families need a safe way to send suggestions without giving every user source-admin control, using camp submission modal and authenticated submission endpoint rather than repeating a generic camp-planning checklist.
Plan with the family constraints in view
Suggest missing camps from SummerCan setup without automatically publishing new sources or changing the global source catalog.
Open SummerCan