Meetup group website content checklist

A meetup site tells newcomers what the group is, when it meets and how to turn up. Organisers are volunteers with little time, so the site has to be cheap to update and every request here should be small.

8 pages36 requests19 requiredAnswered by the lead organiser

Where to start

  1. Events. It decides which platform holds the RSVP list, and the home page is built around the next event.
  2. Code of conduct and venue. The wording needs agreement from more than one organiser, so start it before the rest.
  3. About and organisers. Organisers must say yes to being listed, which can take a few days of asking.
  4. Join and community. These are short links and can be done in one sitting once the tools are named.
  5. Past events and talks. The archive can follow the launch, since a short list is better than waiting for every slide deck.

The checklist

Home

A newcomer wants to know what happens at a meeting and when the next one is, and a home page that talks about the group in general terms loses them.

  • Group name Short text, requiredThe name as it appears on the Meetup, Luma or social page, so people searching for it find the same thing.
  • What the group is about Short text, requiredThe topic and the audience in under 20 words. For example: 'Monthly talks and pizza for Python developers in Leeds, from beginners to experts.'
  • Who the group is for Long text, requiredSay who should come and who may feel it is not for them. For example, whether complete beginners, students or career changers are welcome.
  • Usual meeting pattern Short text, requiredHow often and when, for example 'second Thursday of the month, 6:30 pm to 9 pm'. Give the time zone if there is an online option.
  • Main photo Image upload, requiredA shot of a real meeting with people talking or listening, at least 1800 pixels wide. Faces are fine only if the people agreed.
  • Primary action Single choice, requiredThe one thing a visitor should do first. The home page is built around it.RSVP to the next eventJoin the community chatJoin the mailing listSubmit a talk

Events

The next event is the most useful thing on the site, and it is also the content that goes out of date first.

  • Where events are announced Single choice, requiredPick the tool that holds the live RSVP list. The site pulls or links to it so you do not enter each event twice.MeetupLumaEventbriteOwn formMailing list only
  • Event listing link Link, requiredThe address of your group page on the platform above. If events are sent by email only, leave it empty and say so.
  • Usual venue and address Long text, requiredWhere the group normally meets, with the address, the entrance to use and any security check at the door.
  • Cost to attend Short text, requiredSay whether it is free, a suggested donation or a ticket price. If a sponsor pays for food, say so here.
  • Typical attendance Short textA rough number you can stand behind, for example 'around 40 people'. Newcomers use it to judge the format.
  • What happens at a meeting Long text, requiredThe running order in a few lines, such as doors open, two talks, a break, then socialising. Mention food, drinks and when people usually leave.

Past events and talks

An archive of talks proves the group is active, but slides and videos sit with speakers who may not have shared them.

  • List of past events File uploadA spreadsheet with date, title, speaker and a link to the slides or recording. A copy of your Meetup past events page is a fine start.
  • Talk recordings LinkThe address of your YouTube channel or playlist. Only include recordings where every speaker agreed to be filmed.
  • Speakers' permission to publish slides Yes or no, requiredConfirm that speakers have agreed to their slides and recordings being posted. Ask new speakers when they accept the invitation.
  • Event photos Image uploadUp to eight photos of past meetings with context, such as a speaker at the front or a full room. Send the originals, not screenshots.

About and organisers

People join a group when they trust the organisers, so this page needs real names and a reason the group started.

  • How the group started Long text, requiredTwo or three short paragraphs: when it began, who started it and what problem it was meant to solve.
  • Organiser names and roles Long text, requiredEach organiser's name, role and a line about why they run it. Only include people who agreed to be listed.
  • Organiser photos Image uploadA clear, friendly photo of each organiser, square or portrait, at least 800 pixels on the short side.
  • Volunteer roles Long textJobs that others could take on, such as greeting at the door or finding speakers, and roughly how many hours each takes.

Join and community

Most of the group's life happens in a chat or a mailing list, and visitors need to know which one is the real one.

  • Community chat link LinkThe invite address for Slack, Discord or whatever you use. Check that it is a permanent invite, since many expire after a week.
  • Mailing list tool Short textThe service that holds your subscribers, for example Mailchimp, Buttondown or Substack. The sign-up form on the site connects to it.
  • Social links Long textThe full address of each active account, one per line. Leave out accounts nobody has posted to this year.
  • Newsletter sign-up wording Long textOne sentence about what subscribers receive and how often. It also needs to say that you will not share the list.

Talks and sponsors

Two groups of outsiders write to the organisers, speakers and companies, and both need to know the rules before they ask.

  • How to propose a talk Long text, requiredThe email or form, the talk lengths you book and what a proposal should include. State whether you take recorded talks or only in-person ones.
  • Speaker expectations Long textAny rules on slide content, selling from the stage and recording. Short bullet points are enough.
  • Current sponsors File uploadVector logos (SVG, EPS or PDF) of each sponsor in a single folder, with a note on what they pay for, such as the venue or the food.
  • Sponsorship offer Long textWhat a company gets for sponsoring, such as a logo, a slot to speak or a mention in the newsletter. Add the price or the range.

Code of conduct and venue

Many people choose a meetup partly on whether it feels safe, and a missing conduct page is the first thing they notice.

  • Code of conduct text Long text, requiredThe full text you want published. If you adopted a public template, name it so the correct credit goes on the page.
  • Who to contact about conduct Short text, requiredAt least two people who can be reached at the event, with a private email or phone number for each.
  • Photo policy Long text, requiredWhether photos are taken at meetings, how people opt out and who they tell. Keep it to three or four lines.
  • Venue accessibility Long textStep-free entry, lift access, accessible toilets and parking. If you do not know, ask the venue before the build starts.

Brand

Small groups often have a logo made in a hurry, so the designer needs to know what exists before deciding what to rebuild.

  • Group logo File uploadThe best file you have, ideally SVG or PDF. If it is only a small PNG, say so and the designer will advise on a redraw.
  • Brand colours ColourAny colour associated with the group, as a hex code. A colour from your Meetup banner is fine as a starting point.
  • Preferred fonts FontOnly if your slides or banner use a particular typeface. If you have none, the designer will choose a free web font.
  • Who maintains the site Short text, requiredThe person who will edit events and photos after launch. A site with no named owner stops being updated within a few months.

What clients get stuck on

Slides that live on speakers' laptops

Ask each speaker for a link or a PDF when they confirm the talk, not months later. Without a habit set at invitation time, the archive page stays half empty and looks abandoned.

A meeting pattern that has drifted

The group says it meets on the second Thursday, but the last six events were on different days. Check the real dates against the platform before you write a rule on the page.

Organisers who do not want their names listed

Volunteers worry about being found by strangers. Ask each person in writing whether to use a full name, a first name or a handle, and respect the answer on every page.

An archive with no permissions

Recordings and photos were taken casually over years. Decide a cut-off date, publish only what has clear consent after it, and say so on the page instead of hunting for approvals.

No one owns the update

Ask who will change the next event on the day it moves. If the answer is the person who also runs the venue and the food, use the events tool you already have and link to it.

Copy the checklist

Plain Markdown you can paste into a doc or an email.

# Meetup group website content checklist

## Home
- [ ] Group name (Short text, required)
- [ ] What the group is about (Short text, required)
- [ ] Who the group is for (Long text, required)
- [ ] Usual meeting pattern (Short text, required)
- [ ] Main photo (Image upload, required)
- [ ] Primary action (Single choice, required)

## Events
- [ ] Where events are announced (Single choice, required)
- [ ] Event listing link (Link, required)
- [ ] Usual venue and address (Long text, required)
- [ ] Cost to attend (Short text, required)
- [ ] Typical attendance (Short text)
- [ ] What happens at a meeting (Long text, required)

## Past events and talks
- [ ] List of past events (File upload)
- [ ] Talk recordings (Link)
- [ ] Speakers' permission to publish slides (Yes or no, required)
- [ ] Event photos (Image upload)

## About and organisers
- [ ] How the group started (Long text, required)
- [ ] Organiser names and roles (Long text, required)
- [ ] Organiser photos (Image upload)
- [ ] Volunteer roles (Long text)

## Join and community
- [ ] Community chat link (Link)
- [ ] Mailing list tool (Short text)
- [ ] Social links (Long text)
- [ ] Newsletter sign-up wording (Long text)

## Talks and sponsors
- [ ] How to propose a talk (Long text, required)
- [ ] Speaker expectations (Long text)
- [ ] Current sponsors (File upload)
- [ ] Sponsorship offer (Long text)

## Code of conduct and venue
- [ ] Code of conduct text (Long text, required)
- [ ] Who to contact about conduct (Short text, required)
- [ ] Photo policy (Long text, required)
- [ ] Venue accessibility (Long text)

## Brand
- [ ] Group logo (File upload)
- [ ] Brand colours (Colour)
- [ ] Preferred fonts (Font)
- [ ] Who maintains the site (Short text, required)

Questions about this checklist

Does a meetup group need its own website if it already has a Meetup page?

Usually yes, for two reasons. A site you own survives a platform change or price rise, and it appears in search results with your own words. Keep the Meetup page for RSVPs and link to it from the site.

How can a volunteer-run group keep the site current without much effort?

Pull events from the platform that already holds the RSVP list, and limit hand-edited pages to the ones that rarely change. Name one person who owns the site, and make the editing steps short enough to do from a phone.