Community MeetupsIndia tech calendar
Custom-domain calendar

Put a community calendar on its own branded domain.

Give each community one public calendar home with DNS records, feed URLs, subscription links, and a handoff packet that organizers can pass to their domain or Cloudflare owner.

Domain status
Keep the owner focused on the next DNS step instead of showing the whole integration surface first.
Not started
Generate records

Create the branded calendar configuration and DNS values for the community.

current
Add DNS

Add the CNAME and TXT records in the domain provider or Cloudflare zone.

pending
Verify domain

Confirm the TXT token and route the custom host to the calendar surface.

pending
Share subscription

Publish Apple, Google, Outlook, and raw ICS links on the community profile.

pending
Calendar configuration
Pick the community, branded host, filters, and visual preference for the public calendar page.

Use a subdomain that the community can verify with DNS.

Useful when the branded page should work as both calendar and archive.

DNS and URLs
The public page, raw ICS feed, preview feed, and subscription targets generated for Kubernetes BLR.
Custom-domain calendar workspace ready
Why this matters
A branded calendar turns a scattered promotion problem into one stable destination for every city chapter.
One public feed

Attendees subscribe once and keep seeing the latest meetup updates.

Organizer-owned domain

Community identity stays visible even when registrations happen elsewhere.

DNS handoff

The technical owner gets exact records, URLs, and verification status.

Archive option

The same destination can preserve past events, talks, and materials.

Community MeetupsIndia tech calendar