-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Describe your proposal
We should post our own events on our website. This gives more content to our website and provides us with a permanent archive of TorontoJS events. If the events are stored as e.g. JSON files, it also provides us with a dataset that we can load into the browser and do cool things with (that's probably a different proposal). We can also load in all of our historic events (also a different proposal). This could potentially be built on top of the tooling constructed in #1, or it could be something separate.
Why is this proposal important?
Having our own event listings makes it easier to show the archive of all the amazing things we've done over the years. Note that this proposal is not about managing events, it is just about showing the event listing -- we'll still point to external community/event management platforms like Guild for managing RSVPs etc.
Who will benefit from this proposal?
People running events will have a stable place to point to the historical archive; those seeking sponsors, new members, etc will be able to point to a stronger website with more information on it; and our community members (and the world) will be able to easily browse our past events and see all the neat things we've done!
When will this happen?
Ongoing -- maybe we'll eventually build some tooling for cross-posting events easily, or rely on a JSON export facility from an existing platform.
What platform/location will the proposal need?
I'm picturing these as JSON files in our github website repo, exposed through our website. We'll want a nice naming scheme for them that lets a client slurp them in by iterating through them.
How much will it cost?
Some amount of time from event organizers to add the JSON file -- hopefully a very small amount!
Describe the technical details of the proposal
We need a JSON schema for an event, ideally one that can start simple and expand over time. We need a naming schema, maybe just consecutive numbers (e.g. event-000001.json -- I'll be very happy for this to break when we pass our millionth event).
Anything else?
No response
Tag the organizers
@torontojs/organizers
Metadata
Metadata
Assignees
Labels
Type
Projects
Status