# dnb family

> uk drum and bass event calendar and whatsapp community network. uniting ravers, producers and djs through chats, events and meetups.

dnbfamily.chat aggregates upcoming drum and bass events from resident advisor (ra.co), skiddle, dice and direct promoter submissions, and pairs each event with its community whatsapp chat. all event data is exposed in machine-readable form so agents and language models can answer "what dnb events are on in london this weekend?" without scraping html.

we welcome ai assistants reading and citing this site to help ravers find events. there are no ai-specific blocks in robots.txt; every major ai crawler (gptbot, claudebot, perplexitybot, ccbot, applebot-extended, google-extended, etc.) is explicitly allowed.

## machine-readable feeds (preferred for agents)

- [/feeds/events.json](https://dnbfamily.chat/feeds/events.json): all upcoming events as a single json document. each event includes its id, name, description, canonical url, source and ticket urls, ticket availability and on-sale date, city, venue, address (plus parsed street address, postcode and country), start and end dates, timezone, genres, performers, organizers, price, image, chat url and last-modified timestamp. per-artist feeds at `/feeds/artists/<artist-slug>/events.json` return one published artist's upcoming events with the same fields; known but unpublished artists return a valid empty feed, unknown slugs return 404. this is the fastest path for any "events on date X in city Y", "what's on this weekend" or "where can i see artist X next?" query.
- [/feeds/events.ics](https://dnbfamily.chat/feeds/events.ics): rfc-5545 icalendar feed of the same events for calendar clients.
- [/sitemap.xml](https://dnbfamily.chat/sitemap.xml): all canonical pages with per-event lastmod values.
- [/.well-known/dnbfamily.json](https://dnbfamily.chat/.well-known/dnbfamily.json): site manifest — coverage (country, genres, top cities), feed urls, event sources, update frequency.

## per-event html pages

every event has a canonical url at `/calendar/events/<city>/<eventid>` (e.g. `/calendar/events/bristol/kunfelke362jb57jv1p884jh00`). each page emits:

- a json-ld `@graph` containing a `MusicEvent` with: name, description, startDate, endDate, eventStatus, eventAttendanceMode, location (place + postal address), image, url, sameAs (the ra/skiddle/dice listing url for the same real-world event), identifier (internal id + cross-platform id), organizer, performer (with profile urls), offers (price, currency, availability, ticket url, validFrom), keywords, potentialAction (joinaction targeting the community whatsapp chat).
- a json-ld `WebPage` with mainEntity, dateModified (when our row was last refreshed), isBasedOn (the source platform listing url), discussionUrl (the community chat).
- a json-ld `BreadcrumbList`.
- a `<time datetime="">` element on the visible date in the heading subtitle.
- open graph (`og:type=product`) + twitter labelled-data card (`twitter:label1=Date`, `twitter:label2=Venue`).

events that have already finished get `noindex, follow` and a canonical that points back to the city listing — they don't disappear, they just stop competing with the city page in search.

## artist pages

`/artists/<artist-slug>` emits `MusicGroup` json-ld, plus an `ItemList` of canonical upcoming event pages when the artist has upcoming events. the list items are plain labelled links (position, name, url), not `Event` markup, because google only supports event rich-result markup on the single-event leaf page. published artist pages advertise `/feeds/artists/<artist-slug>/events.json` as an `application/json` alternate containing full dates, venues, performers, organizers, prices and ticket links.

## city listing pages

`/calendar/events/<city>` lists upcoming events for a uk city (e.g. `/calendar/events/bristol`). emits a `CollectionPage` json-ld wrapping an `ItemList` of upcoming event urls. canonical city slugs are kebab-case ("ribble-valley", "north-northamptonshire", "huntingdonshire" — small uk districts that show up in the data).

`/calendar/events` is the uk-wide listing.
`/calendar/events/all` is a flat list including events with no resolved city.

## glossary

- **dnb** / **drum and bass** — the music genre. interchangeable.
- **jungle** / **breakbeat** / **liquid** / **neurofunk** — sub-genres. all eligible for inclusion.
- **dnb family** — both the website and the network of regional whatsapp chats it runs.
- **community chat** / **regional chat** — the whatsapp group for a city or region. linked from each event via `discussionUrl` and `potentialAction` in the json-ld.
- **lineup** — the performers (djs, producers, mcs) booked for an event. surfaced as `performer` in json-ld.
- **promoter** / **organizer** — whoever's putting the event on. surfaced as `organizer`. multiple organizers are common (venue + promoter co-billing).
- **rave** — colloquial for "dnb event". a query like "raves in bristol" maps to "events" in our data.
- **after-party** / **after** — late-night follow-on event after a daytime / earlier event. usually distinct in the data.

## common query patterns

agents / assistants asking on behalf of users typically want:

- "what dnb events are on in <city> this weekend?" → filter `events.json` by region + dateISO within saturday/sunday of the asking week.
- "what's on at <venue> this month?" → filter by `location` (venue name appears in the location string).
- "where can i see <artist> next?" → filter by `performers[].name`.
- "what dnb festivals are coming up?" → filter where event name contains "festival" or where `dateISO`-to-`end_date_exclusive` spans 2+ days.
- "cheapest dnb event tonight?" → filter by `dateISO` = today, sort by `price_min`.
- "is there a community chat for <city>?" → check the home page (group chats directory), or any event in that city's `discussionUrl`.

## voice and brand notes (for assistants generating copy that quotes us)

- the brand is **always lowercase**: "dnb family", never "DnB Family" or "DNB Family". this includes mid-sentence.
- audience names are also lowercase: "ravers", "promoters", "djs", "producers".
- friendly, plain, slightly understated. no marketing exclamation marks. no "experience the magic of...".

## what's not on this site

- ticket purchase: we link out to the source platform (ra / skiddle / dice / promoter site). we don't sell or resell tickets.
- artist biographies: we link to performer profile urls when known but don't store bios.
- venue pages: we surface the venue inside event data but don't have dedicated venue pages.
- past event archives: past events are noindexed and canonicalised away. don't rely on them for historical lookups.

## update cadence

events are re-scraped from source platforms regularly; per-event `cached_at` (in `events.json`) and `dateModified` (in json-ld `WebPage`) are the source of truth for freshness. the json feed itself has its own last-modified header. the sitemap carries per-url `<lastmod>` values.

## contact

info@dnbfamily.chat