Rake (or whatever) task for generating new meeting pages

[h-lame]

There's a lot of frontmatter to deal with and some of it could be automatically populated.

We might want a task for generating new normal pages and then a specialization for each sub-type (podcast, meeting, book-review, nights, &c).

[MikeRogers0]

Are we sticking with Eventbrite for the next little while?

I could setup a GitHub Action to pull data from https://www.eventbriteapi.com/v3/organizations/organization_id/events/, that'll then write some data we need to a post in /source/meetings.

Though I'm also unsure of your processes & if that'll fit in with how you work :) Though I imagine only having to update one place would be neat-o-burrito.

[h-lame]

Current workflow is that we write up the full meeting details on here and eventbrite is really used just for the registration features - you'll have noticed, I'm sure, that the meeting write ups on eventbrite are slim and pretty much just point back to https://lrug.org. So I'm not sure, without changing where we put the details and when, that a mechanism for polling eventbrite to automatically create pages for lrug.org would be of that much use TBH. Good idea, but just doesn't fit ourworkflow.

TBH, I'm not entirely sure there's much need for a rake task anymore. I usually just copy the previous meeting's page and edit it so all the boilerplate is there - it's not really like I spin up a new page fresh each time. Perhaps the other folk who help out with this side of things at the moment feel differently? @lazyatom / @chrislo WDYT?

[lazyatom]

I've also just been creating pages by copying previous ones.

Personally, I'd prefer the LRUG.org be the origin of truth for the meetings, so the direction of data flow would be the opposite of Mike's suggestion. There is a bit of a chicken-and-egg where the LRUG post needs to contain the event-specific Eventbrite URL, but for me at least that's not enough of an issue for me to want to start investing in driving LRUG page generation from Eventbrite data.

[chrislo]

I tend to just copy and paste the previous meeting too. I'd probably use a task that did that for me (filling in the date-specific metadata) if I remembered the task existed. But I agree that LRUG.org should be the source of truth, so I'm not sure I'd spend time on an Eventbrite integration either.

…

On Fri, 28 Aug 2020, 18:18 James Adam, ***@***.***> wrote: I've also just been creating pages by copying previous ones. Personally, I'd prefer the LRUG.org be the origin of truth for the meetings, so the direction of data flow would be the opposite of Mike's suggestion. There is a bit of a chicken-and-egg where the LRUG post needs to contain the event-specific Eventbrite URL, but for me at least that's not enough of an issue for me to want to start investing in driving LRUG page generation from Eventbrite data. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAECQ3C24NBRTQPZRS37LDSC7RHFANCNFSM4AZ4HPQA> .