telstrapurple / devevents Goto Github PK

Now that we have a lot of events in the list, we should improve how we manage the list.

I'm proposing we psuedo-archive older events to stop the listing page from growing too long and having a large signal-to-noise ratio.
I'm also proposing a reordering of information to make it easier to find things people are interested in.

I suggest we do the following:

• Split out previous years (e.g. 2017) into their own year specific pages, with a link from the main listing page
• Re-organize the main page to show events in a year in reverse date order
• Have separate tables for each upcoming year (2018, 2019, etc.)
• Add a table of contents to jump to specific years as well as the list of recurring and completed events
• Split the table for the current year (currently 2018) into upcoming 2018 events and completed 2018 events. We can then remove the strikethrough formatting as it makes things harder to read.

contributing.md:

Ensure dates are in dd/mm/yyyy format (in case we want to parse this data later). Use TBC if the date is unconfirmed or unknown.

This seems to only be in-place for the pre-2018 data. Consensus in readme.md from 2018 onwards seems to have settled on dd-mmm-yyy (%d-%b-%Y) instead.

There is rather a lot of content in readme.md.

Suggest moving out the following to other pages:

• Honorable mentions (now closed as well)
• 2019 events
• CFP
• To be confirmed

Not sure about completed events that can probably stay

Might be a good one for the list? https://www.apidays.global/australia/

Just curious as why there's a US based conference included?