So today we discussed where we should publish an event and what events should be published on the website and what event should be published on the app. We decided that this topic needs more discussion, and some of the points that we already discussed and were already thinking about are:
- Maybe adding an iframe of the app into the website. This will solve the problem of people thinking that it's a new app and they have to download it and clicking on another button, and it will already be shown there. It will solve the problem of having to re-implement everything on the website, but it will probably be ugly. We would have to adapt the code of the website to look more like the design of the app, or more the code of the app to look more like the design of the website. This ties into a new design that we were going to think about anyway, which is related to what Anastasia wanted to suggest.
- We could use the same backend, and in this backend we could describe the app and the event and just have different sections for each part, like the title, maybe a link to a group, stuff that is more generic, and then put that information also on the website. The issue with that is that we want to actually keep the website for reoccurring events or at least not special events, or just the capability to sometimes design the event in a different way or add more information in the form of different buttons to different websites, or just have more flexibility. Samir brought up also an interesting point of having these pages indexed properly.
We also want to avoid some events that might be very weird at first glance to be on the website, because this is kind of like our face for the public, so we want to avoid that for now. We discussed the option of April suggesting having some kind of differentiation or way to say this event already exists on the website, so there's no need to duplicate it. Have some kind of section which is separated, and there we have the events from the reoccurring events and the special events and the other events through the app will be shown in a different section. That way, in order to not duplicate it, we add some kind of button somewhere to say, in the admin panel, that this event is already happening and described on the other part of the website.
Also, we were thinking about adding a link to every event in the app from the event on the website, so that there's more visibility for the app. When you're looking for something on the website and you see the event, you can also go to the app. We want to keep it so that people don't have to download and use the app, so we can write something like it really helps us to keep everything organized if you register through the app, but you can also just come specific events, obviously, for some, and otherwise, another option is to just directly link. Option three is to directly link to the app from the events button on the website. Just link to the app, not show any events at all on the website. That's also an option that I didn't mention.
If anybody needs to use the backend, then they would have to talk directly to Samir to get permission and try to hook that in somehow. If I forgot anything, then I'll just add it later, and if any of you see anything that we spoke about today, then please do just add it and let's discuss it soon.
So today we discussed where we should publish an event and what events should be published on the website and what event should be published on the app. We decided that this topic needs more discussion, and some of the points that we already discussed and were already thinking about are:
We also want to avoid some events that might be very weird at first glance to be on the website, because this is kind of like our face for the public, so we want to avoid that for now. We discussed the option of April suggesting having some kind of differentiation or way to say this event already exists on the website, so there's no need to duplicate it. Have some kind of section which is separated, and there we have the events from the reoccurring events and the special events and the other events through the app will be shown in a different section. That way, in order to not duplicate it, we add some kind of button somewhere to say, in the admin panel, that this event is already happening and described on the other part of the website.
Also, we were thinking about adding a link to every event in the app from the event on the website, so that there's more visibility for the app. When you're looking for something on the website and you see the event, you can also go to the app. We want to keep it so that people don't have to download and use the app, so we can write something like it really helps us to keep everything organized if you register through the app, but you can also just come specific events, obviously, for some, and otherwise, another option is to just directly link. Option three is to directly link to the app from the events button on the website. Just link to the app, not show any events at all on the website. That's also an option that I didn't mention.
If anybody needs to use the backend, then they would have to talk directly to Samir to get permission and try to hook that in somehow. If I forgot anything, then I'll just add it later, and if any of you see anything that we spoke about today, then please do just add it and let's discuss it soon.