AsyncAPI Hack & Conf 2021 - Website

[derberg]

We need a place where we can share conference details, invites, registration for those that want to get email reminders, schedule, dates. Basically everything related to the events.

There are many options we have here but most obvious are 3:

1. we reuse https://www.asyncapiconf.com/, not just the domain but the feel and look of the website too
2. we use https://www.asyncapiconf.com/ domain but create completely new website (most time consuming)
3. we just add a new view to AsyncAPI website under https://www.asyncapi.com/events/21/conference and https://www.asyncapi.com/events/21/hackathon

My preference is 3 as I honestly do not remember why last year we hosted the event under separate domain really. Website was hugo, not nextjs tech as it is now, but still was flexible to do it there.

[magicmatatjahu]

I also opt for 3 option 💪🏼 Create one time the pages for event and conference and reuse them. We can also add possibility that people submit their presentations as PRs with content as for a blog post, i.e. as MDs with metadata.

I don't know if it was discussed but we can also extend the events page with possibility to adds the local events - if people will organise some local meetup related to the Event-Drive topics, then they can also add info about in in out site. What do you think?

[derberg]

I don't know if it was discussed but we can also extend the events page with possibility to adds the local events - if people will organise some local meetup related to the Event-Drive topics, then they can also add info about in in out site. What do you think?

this is definitely something we should consider long term, I think it deserves a separate issue in website repo

[smoya]

I would opt for a combination of 1, 2, and 3. Let me add some details:

• 1. Because I consider having a separated domain gives the importance it deserves as an event. It emphasizes it is a big event, something temporary. I also thing it's easier to share as individual URL, short to remember and fast to find through search engines.
• 2. I would advocate for keeping a similar design, which feels like a fresh and cool one. Perhaps I will modify it a bit just to differentiate with last event.
• 3. We can always add a link to the event page that redirects to asyncapiconf.com. We can also create a subdomain like conf.asyncapi.com or similar.

I also suggest to keep the last event page per historical reasons. People might want to check last year edition details. An example is how Jamstack conf does: https://jamstackconf.com/2020/october/

[derberg]

for now the best option was with just reusing what we had:

• so we have website here https://conference.asyncapi.com/ under dedicated domain
• we did not continue with https://www.asyncapiconf.com/ as main one as it was not part of the deal with LF and yeah, solving this would take to much time, and anyway subdomain seems better for the future.
• https://www.asyncapiconf.com/ should, and will redirect to https://conference.asyncapi.com/
• https://conference.2020.asyncapi.com/ is where we keep old website. Soon after this PR is merged it will reflect old conference and info about new
• regarding https://www.asyncapi.com/events. I eventually did not go this path as I liked what Maciej wrote about I don't know if it was discussed but we can also extend the events page with possibility to adds the local events. I think this is the future direction really. We should have events view where all asyncapi-related and eda-related events are listed. The ones with date that is close to the event are featured. Not only local events but also conferences as there are many. @magicmatatjahu as you are behind the initial idea, you mind dropping your brain into an issue in website repo 🙏🏼 doesn't have to be super sophisticated issue, just a brain dump as anyway we won't be able to start it before we have some dedicated designer that can ease implementation, and there are other super important things to do in the website

[derberg]

I think the topic is closed and will lock conversation, lemme know if I'm wrong