Set up a "Kids’ Activities" calendar your whole family can follow

The idea

You'll make a single view called "Kids’ Activities". A view is a saved calendar that pulls from the feeds you already have and gets its own unique subscribe-able link. Then you'll curate that view to meet your needs. In this example, we’ll customize it two ways, because sometimes different feeds need different treatment:

• Sports feeds are mostly shareable. You want to share every game, meet, and tournament, but not the practices. One keyword rule handles that.
• School feeds are mostly not. Half-days, club sign-ups, and class parties aren't worth a special trip, but the School Play and the Band Concert are. For those, you'll tag the few keepers and hide the rest.

The important part: all of this lives on the shared view. Your own calendar still shows every practice and half-day — only the feed that the fan club subscribes to is trimmed down.

What you'll need

• Your Tapestry workspace with your kids' feeds already added as Sources (sports app, school, etc.). New to adding external calendar feeds? The add-a-team-schedule guide covers it.
• About ten minutes.

Step-by-step

1. Create the "Kids’ Activities" view

   Go to Views → New calendar and name it whatever makes sense to you. We’re calling ours Kids’ Activities. A view is just a saved combination of sources, rules, and filters. Every view gets its own private subscription URL, which is what your kids’ fan club will follow.

2. Add the sources family cares about

   In the view's Sources list, check the feeds that belong on this calendar: the kids' sports and activity feeds, the school feed, and your own added events (the "Manual events" source). Leave out work, household chores, and anything personal, but do include any feeds that contain relevant events for multiple children — we can filter and organize them further in the next few steps.

   Sources are the usual starting point, but they're not the only way to pull events onto a view. Under "Also include (optional)" you can add a whole category, person, or tag, and any event carrying it joins the view no matter which feed it came from. That's additive — it's an or, not an and — so a single recital you assigned to Lily, or anything you tagged Fan Club, shows up even if its source feed isn't checked. Handy when the keepers are scattered across feeds you otherwise want to leave off.

   (Prefer separate feeds per child? See "Variations" at the end.)

3. Sports: show the games, hide the practices

   Open Workspace → Rules and add a new rule. Set it to apply to just the Kids’ Activities view (the "applies to" picker → Specific calendars → Kids’ Activities), so it never touches your own calendar.

   Then:

   • Condition: Title contains Practice
   • Action: Exclude from this calendar

   That's it! Games, meets, and tournaments stay; practices vanish from the shared feed. If "practice" might show up in a feed where you don't want this (say, a music-lesson calendar), add a second condition for the source so the rule only hits the sports feed.

   Your calendar is untouched

   Because the rule is scoped to the Kids’ Activities view, you still see every practice in your own "All events" calendar.

4. School: flip it — hide everything except what you tag

   The school feed is the opposite problem: you want almost none of it, plus the occasional gem. So instead of excluding the noise, you'll keep only what you mark.

   a. Make a tag. Go to Workspace → Tags and create one for this calendar. We’re calling ours Fan Club.

   b. Tag the keepers. When the School Play or Band Concert lands on your calendar, open the event and add the Fan Club tag. (Are the event titles unique and predictable? You can also auto-apply a tag with a rule — Title contains "Concert" → Add tag Fan Club.)

   c. Hide the rest. Back in Workspace → Rules, add another rule applied to the Kids’ Activities view:

   • Conditions (match all): Source is School · and · Tag Fan Club is not present
   • Action: Exclude from this calendar

   Now the school feed contributes only your handful of tagged events. Tag a new one next semester and it appears automatically; everything else stays hidden.

5. Color-code by kid (and label them for family)

   Add each child under Workspace → People and give them a color. People are a workspace-wide list of who your events involve, so once a kid has a color you can set it as the default on their sources, assign it per event, or apply it with a rule — and every one of their events picks it up.

   Inside Tapestry that's the good stuff: Lily's events show in teal, Sam's in orange, and you can filter the whole calendar by "who" in a click. Those per-event colors carry into the shared feed too, so a relative on Apple Calendar (or another app that supports per-event colors) really does see Lily in teal and Sam in orange. The one exception is Google Calendar, which paints a whole subscribed feed in a single color — so Google subscribers won't get the per-kid colors.

   For those Google folks, put the label in the title instead — one more quick rule on the view:

   • Condition: Source is Lily's soccer (so it only touches her events)
   • Action: Prepend Lily:

   Now "Soccer Game" reads as "Lily: Soccer Game" on Grandma's calendar even when it's all one color — an emoji prefix (Prepend "⚽ ") works the same way. (More on exactly what does and doesn't carry over in syncing a view to Google Calendar.)

6. Publish it and send the link

   Open the Kids’ Activities view and copy its calendar subscription (ICS) link. Send it to the grandparents. They just need to add it once — in Apple Calendar (File → New Calendar Subscription), in Google Calendar (Other calendars → From URL), or in Outlook (Add calendar → Subscribe from web). From then on it stays in sync on its own. The next time you tag a school play or a new tournament gets posted, it simply shows up on their calendar — no re-sending, no re-exporting.

Why this beats "just share my calendar"

• Your calendar stays whole. You still see every practice and half-day; family sees the curated version.
• It's a feed, not a snapshot. No re-exporting — changes propagate to everyone who subscribed.
• One link, every kid. Grandma and Uncle Brian can subscribe once and get all the kids' attend-worthy events at once.
• You can take it back. Rotate the view's link any time to revoke access without affecting anything else.

Variations

• One feed per child. If relatives only follow one kid, make a "Lily's Activities" view and a "Sam's Recitals" view the same way, and share each separately.
• A "local family" cut. Make a second view that also keeps practices for the grandparent or babysitter who helps with carpools — same sources, minus the exclude-practices rule.
• Any noisy feed. The "exclude "Practice"" trick works for any feed that's mostly-keep; the "tag the keepers" trick works for any feed that's mostly-skip. Mix and match per source.
• Follow a person, not a feed. Instead of picking feeds at all, build the view around a kid: leave Sources empty (or minimal) and under "Also include" add the person Lily. Every event assigned to Lily — across sports, school, music, and your own added events — lands on the view automatically, so there's nothing to re-check when a new feed shows up.

Ready to build it? Open Tapestry, head to Views, and you'll have a family-ready calendar in about ten minutes.