web site construction notes

[rppt]

Open issues

• What will be the website name in lpc.events domain (www.lpc.events, web.lpc.events)
• Will we host 2021 and older and 2022 and newer on the same host?
• Do we still want to have wordpress in parallel with indico?
• Do we want to keep additions as customization directory or we'll just drop them into the indico source?
• What caused site slowness? Do we need a stronger linode? Do we want to split front end and DB to different nodes?

Prerequisites

• Set up an email that indico can use
• Deploy up a "backup site" in our Linode account with archive of everything up to 2021
• Switch over linuxplumbersconf.org to the "backup site"

[aliceinwire]

What will be the website name in lpc.events domain (www.lpc.events, web.lpc.events)

www.lpc.events I think is ok

Will we host 2021 and older and 2022 and newer on the same host?

Maybe we can add a subdomain (something like 2021.lpc.events ?) and lpc.events will only show the new one ?
Depend on how many resources are using during heavy load, probably.
If we have the resources to divide, perhaps could be better.

Do we still want to have wordpress in parallel with indico?

I have no idea how much well WordPress is integrated with indico

Do we want to keep additions as customization directory or we'll just drop them into the indico source?

better keep as customization directory where possible IMHO

What caused site slowness? Do we need a stronger linode? Do we want to split front end and DB to different nodes?

I have no information regarding this issue

Set up an email that indico can use

Do we have a mail server ?

Deploy up a "backup site" in out Linode account with archive of everything up to 2021

lgtm

Switch over linuxplumbersconf.org to the "backup site"

like doing redirect ?

[rppt]

Do we want to keep additions as customization directory or we'll just drop them into the indico source?

better keep as customization directory where possible IMHO

We anyway have modifications to Indico code, so we anyway need to rebase out changes for any new Indico release. Adding the template modifications inline won't change much the maintenance cost. OTOH, it's easier to track template changes this way than with a customization directory.
I've added v3.0.3-inline-changes branch that has everything we need inside Indico repository.