• What would be the best strategy for an event that takes place each year and each year the website is “renewed”?

    The organizers of the event thought of having the regular domain of the website (eventsite.com) be the landing page of that year’s event and the previous years be eventsite.com/2018, eventsite.com/2017, eventsite.com/2016, etc. Then after this year, change this year’s site to eventsite.com/2019 and then eventsite.com become the landing page for 2020, and so on.

    I’m thinking changing the domain like that each year will be quite complicated and not the best idea, for many reasons. Or is there an easy way to do it and it can work without complications as I believe? I think better to have the year in the domain from the beginning and not changing it after each year, no?

    I also think it would be better to use sub domains 2019.eventsite.com instead of eventsite.com/2019. That’s how yearly events usually do it anyway. What are your thoughts?

    And is WP Multisite the way to go here? or is there a reason to not use Multisite in this case?

Viewing 2 replies - 1 through 2 (of 2 total)
  • You don’t say how much content is involved with each year, or whether the old ones are active or not, as in comments and additions. Do any of the years pull from past years, like photos or lists or anything? Do you want external links to the old ones to still go to the old ones, or to go to the current one?

    If it’s static for the past, I would consolidate each year to a Post (or if that’s too small, make it a category).
    If it’s still in use, you have the problem that external links would not have the year, so it is impossible to redirect correctly. So always have the year available and use redirects on the current one so it’s always accurate.

    Thread Starter slacle

    (@slacle)

    I don’t know all the details yet actually. Still trying to figure out how much work it will be to give them a quote and see if they will hire me for the job. Here’s what I know:

    There’s a good amount of content each year. Maybe around 10 pages of things like schedule, tickets, speakers, sponsors, gallery. So the content would change each year.

    So there would be for example eventsite.com/2019/speakers or 2019.eventsite.com/speakers

    The site is also multi language. Although I don’t know what plugin they’re using for it.

    I don’t think the previous years will be active. They just want an archive which people can look at for historical purposes.

    It can be assumed that new years won’t pull anything from past years.

    About the external links, I assume they would want the external links to go to their respective years. Which I see as a problem and which is why I mentioned that changing the domain each year to be a bad idea instead of having the year from the beginning. An external link like eventsite.com/speakers that originally referred to 2018 wouldn’t be able to be redirected to 2018.eventsite.com/speakers because then eventsite.com/speakers for the current year couldn’t be accessed.

    So I’m trying to figure out what is possible and what is not, and then depending on what I decide will work, then maybe I’ll have to try to convince them to things in a different way than they had envisioned.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Yearly event website’ is closed to new replies.