alexwlchan
commented
5 years ago Maybe split the call to action and the rationale? So somebody can just read it and see “ah, I need to do X” and not read all the detail of why X is a good thing or which conference got X right or wrong.
e.g. the food and drink section could be simplified to
A prospective attendee wants to know: * What sort of food and drink are you providing? * Will I be able to eat it? * When will it be available? The default food/drink option at a lot of tech events is pizza and beer, but a lot of people can't have one or both of those. Depending on how much flexibility you have, you may be able to include more people. You should: * Offer food which satisfies as many dietary requirements as possible. Vegetarian at a bare minimum, more if you manage it * Tell people what sort of food you're providing, and what dietary requirements it satisfies * Clearly label the food, both by category and ingredients * Tell people when mealtimes are * Offer non-alcoholic, low-caffeine and low-sugar drinks
Right now the site reads like a barely organised braindump of ideas (because that's what it is!).
If you're organising an event, do you really want to read 8500 words of text (the long version) to get the advice? I think it could be much more digestible.
In particular, I'd like to provide a really short checklist of "things you can do", possibly broken down by timeframe? And generally make it easier to navigate.