You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now 2023 and 2024 are not static sites and rely on the BE API and everything. 2022 is a static site served from S3 but is far from perfect (http://2022.pycon.it/ gives a 403 while http://2022.pycon.it/en works)
The ideal solution would be the 2022 approach of generating a static "snapshot" of our site that doesn't rely on the BE anymore to make it more future-proof.
As 2023 and 2024 (and future websites) will look very similar, we should consider adding a banner or something in the old pages clearly saying "This website is the archived website of PyCon Italia XXXX. Click here to go to the latest edition".
It might be as be worth adding a line saying that the content is correct at the time the snapshot was taken.
Right now 2023 and 2024 are not static sites and rely on the BE API and everything. 2022 is a static site served from S3 but is far from perfect (http://2022.pycon.it/ gives a 403 while http://2022.pycon.it/en works)
The ideal solution would be the 2022 approach of generating a static "snapshot" of our site that doesn't rely on the BE anymore to make it more future-proof.
As 2023 and 2024 (and future websites) will look very similar, we should consider adding a banner or something in the old pages clearly saying "This website is the archived website of PyCon Italia XXXX. Click here to go to the latest edition".
It might be as be worth adding a line saying that the content is correct at the time the snapshot was taken.
The text was updated successfully, but these errors were encountered: