Export Meetup.com Events to a Github Pages Jekyll site

For a long time, our main Omaha Java Users Group communication has been
through meetup.com/omahajava/,
however we do still have an ojug.org website too.
At first, we would nicely copy the event to both Meetup and OJUG.org, however within a few
months you can see that we simply stopped duplicating effort and the events on ojug.org quickly got out of date. Not a big deal at the
time. But it would be nice to archive our past events to the ojug.org site (especially as we
explore Meetup.com alternatives in the near future [1]).

(if you want the TL&DR: see all the details at https://github.com/jeffsheets/ojug-meetup-export.)

Exporting Events from Meetup.com

The first step was to find a way to export our past events. I had hoped
for a CSV export through the admin UI, but didn’t see anything. I then thought it might take
some web scraping, or maybe some network dev tools api call watching. But noticed that there
was a grayed out setting in the admin UI for the Meetup API 🤔. A quick google found the Meetup GraphQL API
page. And to my surprise, sending a test query just worked! 🎉

After a little trial and error from their API docs, and increasing the result count to 100 to
get all of our events without paging, I was able to export all of the past events to JSON

 query($meetupId: String!) {
groupByUrlname(urlname: $meetupId) {
pastEvents(input: {first: 100}) {
edges {
node {

And some inputs of:

Which gave a
nice JSON result
, like this:
“data”: {
“groupByUrlname”: {
“description”: “Omaha’s Java User Group @omahajug. yadda
yadda yadda”,
“pastEvents”: {
“count”: 65,
“edges”: [
“node”: {
“title”: “Angular JS for Java Developers”,
“description”: “This month //etc etc etc”,
“dateTime”: “2014-05-20T17:30-05:00”,
“going”: 27

ojug.org Tech

Before showing you how the event blog post pages were generated, a quick note on the tech for
ojug.org (src at https://github.com/OJUG/ojug.github.io).
It is running on a standard Github
Pages Jekyll workflow
stack. While we have thoughts to move that over to 11ty, for now Jekyll is working fine. Create a new
markdown file in the _posts folder,
merge to the main branch, and the workflow auto-kicks off and redeploys our ojug.org site like

Generating Meetup event Jekyll posts

With this in mind, the blog needs .md files generated for each event in the events JSON. Using
a little Groovy, this was done pretty quickly with a GSP template, some functions to prettify
date formats, and a filename creation function. The groovy post.gsp
looks like:

layout: post
title: “<%= longDate %> <%= title %>”

<%= description %>

(This past event was exported from Meetup.com)
(<%= attended %> people had RSVP’d to this event in Meetup)

Then the code that generates the template for each JSON event is in PostGenerator.groovy:
 void generatePosts() {
def events = new
events.each {
def event = it.node
def filename = makeFilename(event.title, event.dateTime)
def outfile = new File(“$DEST_FOLDER/$filename”)
def filecontents = new SimpleTemplateEngine()
title : event.title.replaceAll(‘"’, ‘"’),
description: event.description,
longDate : convertToLongDate(event.dateTime),
attended : event.going
outfile.write filecontents

When executed, nice markdown files are generated in the output directory, similar to 2014-05-20-angular-js-for-java-developers.md:

layout: post
title: “May 20, 2014 Angular JS for Java Developers”

This month //etc etc etc

(This past event was exported from Meetup.com)
(27 people had RSVP’d to this event in Meetup)

The last step was to copy all of the new markdown files into the _posts directory, create a
PR, merge it, and see the final results up at ojug.org!

Wrap up

And that’s it! Writing this blogpost probably took longer than the process to export Meetup to
JSON, and generate new markdown files for the Jekyll blog! You can view all of the full source
on my github at https://github.com/jeffsheets/ojug-meetup-export

[1] - A quick footnote, about Meetup.com… Over the years Meetup has been great for
advertising our group, attracting new members, having a great user interface, and easily
collecting RSVP’s for events. We’ve always been lucky enough to have great sponsors to pay the
ever increasing fee, which is now up to $197.98/year. However Meetup’s decision to not allow
us (or any group) to “freeze” the account, means that our sponsor has been paying that fee for
2.5 years with little benefit. Talking to other local tech meetup organizers, it became
apparent that many of us are pondering ways to free ourselves from these fees. Our sponsors
could throw some pretty great user group parties with the savings! There’s a lot of
functionality we’d have to replicate though, so I’ll leave that full discussion for another