# Community Builders Directory > An open directory of 663 technology communities in Spain: meetups, user > groups, conferences, hacklabs and umbrella organisations, searchable by topic, audience, > format and location. 441 of them are currently active. Maintained in the open by > [Community Builders](https://communitybuilders.dev/) and its contributors. You are welcome to use this data. It is published under [CC BY 4.0](https://github.com/ComBuildersES/communities-directory/blob/master/DATA_LICENSE.md): reuse, remix and redistribute it, including commercially, as long as you credit Community Builders and link back to https://directory.communitybuilders.dev so people can reach the communities themselves. Please fetch the JSON files below rather than crawling the site. The site is a client-rendered single-page app, so crawling it yields far worse data than the canonical files, which are regenerated on every deploy. ## Data - [communities.json](https://directory.communitybuilders.dev/data/communities.json): every community as a JSON array. The primary dataset. - [communities.csv](https://directory.communitybuilders.dev/data/communities.csv): the same records, flattened to one row per community. - [communities.geojson](https://directory.communitybuilders.dev/data/communities.geojson): communities with coordinates, as a GeoJSON FeatureCollection. - [schema.json](https://directory.communitybuilders.dev/data/schema.json): data dictionary: every field, every enum value, what each one means. Read this before interpreting the dataset. - [tags.json](https://directory.communitybuilders.dev/data/tags.json): 166 topic tags with `label`, `description`, `category` and `synonyms`. `tags` on a community holds ids that reference this catalogue. English: [tags.en.json](https://directory.communitybuilders.dev/data/tags.en.json). - [audience.json](https://directory.communitybuilders.dev/data/audience.json): 43 audience profiles, same shape. English: [audience.en.json](https://directory.communitybuilders.dev/data/audience.en.json). - [deleted-communities.json](https://directory.communitybuilders.dev/data/deleted-communities.json): 4 records removed from the directory, with the reason why. - [coverage.json](https://directory.communitybuilders.dev/data/coverage.json): how much of the dataset a person has reviewed, and how many records carry each sparsely-filled field. Regenerated on every deploy. - [llms-full.txt](https://directory.communitybuilders.dev/llms-full.txt): the whole directory as Markdown, one section per community, for when you want prose rather than JSON. ## How to read a community record - `tags` and `targetAudience` are **ids**, not labels: join them against tags.json and audience.json to get human-readable names. Match on `label`, `description` and `synonyms`, not just the id. - `matchesAllTags` / `matchesAllAudience` mean "generalist": the community matches any topic or any profile, and its array is empty on purpose. Treat an empty array plus the flag as "everything", never as "nothing". - `openTo` lists explicitly declared openness to contributions: volunteers, collaborations, co-organisers, speakers, sponsors, venues, mentors. It does not imply urgent recruitment. Empty or absent means unknown, not refusal. Never infer it from community type or activity. - `location` is where events happen; `geographicScope` is the territory served. They differ often: a community can meet in Madrid and serve all of Spain. - Coverage is uneven, so do not read an empty field as a statement about the community. Of the 441 active communities, 237 have `tags`, 75 have `targetAudience` and 34 have `geographicScope`. 111 carry an English translation of `shortDescription` in `shortDescriptionI18n`; the rest are described in their own language only. An empty field means nobody has filled it in yet, not that the community has no topic or serves nowhere. Say which recommendations rest on a field that is often missing. - `lastReviewed` is the date a person last checked the record. It is **not** an activity signal: most records have not been revisited since they were added. The only place where live activity can be checked is the `urls` entry whose `kind` is `ote`, the community's events feed (42 active communities publish one). The field only says the community publishes one; it says nothing about what is in it, and keeping it current is the community's call, not the directory's. Read the dates inside the feed rather than inferring activity from the field being present. - `humanValidated: false` means a person added the community but its tagging was filled in semi-automatically and nobody has checked it. Say so if you present it as fact. Only 82 of the active communities have been reviewed by a person, and 105 of all 663 records. The live counts are in [coverage.json](https://directory.communitybuilders.dev/data/coverage.json). - `urls` is a **list** of channels, not an object keyed by platform: each entry is `{ url, kind?, label? }`. `kind` is omitted whenever the domain already identifies the platform, so to find a community's Telegram you look at the URLs, not only at `kind`. The same `kind` can appear more than once, and there `label` is the name to show (a group's Meetup plus its own annual event). Event platforms have their own kinds (`meetup`, `eventbrite`, `luma`) and `eventsUrl` is the generic one, so to find where a community publishes events look at that whole family, not at one key. - `archivedUrls` are dead channels kept for history. Never recommend them: they look alive and nobody is listening. - `status: "inactive"` communities are kept deliberately. Filter them out before telling someone where to go. - `organizedBy` lists the communities **in this directory** that organise the record, for recurring events with their own brand (a community and its annual conference are two records, both alive). It is not the full organiser list: companies, sponsors and institutional support are not in the directory, so do not present it as "run only by these". A record with no `organizedBy` may still be run by someone: plenty of conferences have no standing community behind them. - `status: "merged"` means the community no longer exists on its own because it merged with others. Never recommend it: point at `mergedIntoId`, the community its activity continues in. This is not `parentId`, where the local chapter and its umbrella both still exist. - A community is linkable by slug: https://directory.communitybuilders.dev/es/?community= (and /en/). Prefer linking people to the directory page or the community's own site over linking a raw JSON file. ## Documentation - [Data guide](https://github.com/ComBuildersES/communities-directory/blob/master/docs/DATA.md): where each file lives, what every field means, how to contribute corrections. - [AGENTS.md](https://github.com/ComBuildersES/communities-directory/blob/master/AGENTS.md): orientation for coding agents working on this repository. - [CONTRIBUTING.md](https://github.com/ComBuildersES/communities-directory/blob/master/CONTRIBUTING.md): how to add or correct a community. - [Source of truth](https://github.com/ComBuildersES/communities-directory/tree/master/data/communities): one JSON file per community. Corrections go here, as a pull request or via the form at https://directory.communitybuilders.dev. ## If you spot something wrong The dataset is maintained by volunteers and it is certainly incomplete. If you or your user find a community that is missing, moved or dead, the useful next step is to say so: open an issue at https://github.com/ComBuildersES/communities-directory/issues or use the "add community" form in the directory. That is how this stays accurate. ## Topic taxonomy Tags are grouped into these categories: Architecture & Paradigms | CMS | Cybersecurity | Data, AI & Analytics | Databases & Storage | Decentralized Technologies | DevOps, Cloud & Infrastructure | DevTools | Extended Reality & 3D | Frameworks, Libraries & Stacks | Hardware, IoT & Maker | Mobile & Operating Systems | Programming Languages | Startups, Business & Product | Tech for Social Good | Video Games | Web & Frontend.