Okay, cool! We are a go on this, at least for an October trial run.
@mkamin and @sspradling I will do my best to be at the next Program meeting, if you want to put it on your agenda.
As far as I’m concerned, I am just tech support on this. The Program Committee will have the say over adjustments to the content, branding, etc, and I can adjust the script accordingly.
October can be our trial run with this, and post-conference we can have an additional action item to make this permanent and devote ongoing funding to it.
Next Steps
Subdomain
We’ll need to decide what we want to call this. State of the Map US just puts the year as the subdomain, like 2026.ilgisa.org. Nice and short, follows an obvious naming convention.
If, long-term, we wanted to use this to keep an archive of past agendas and programs, we might want to include some signifier or what event, like 2026-annual.ilgisa.org, to leave room for things like 2026-chicago-regional.ilgisa.org.
a brief aside
I would suggest not putting past things into the same site, as it would clutter the search results. A single catch-all “archive” site could be created separately, or we just keep each meeting agenda as its own subdomain.
I’m leaning towards 2026-annual as the subdomain, but this can be discussed at the committee meeting.
Once we settle on a name, we’ll ask CM Services to get it officially created and pointed at the published site, which will be updated and made public in October. Easy enough.
Content Adjustments
To be discussed at next Program meeting.
Documentation
The instructions, such as they are at the moment, are written up in the repository README file, so they will appear on the main page of the repo itself.
It’s really just:
- adjust some text
- run a script
- upload a ZIP and click a button
These docs can be updated as the need arises.