Il giorno 17/feb/2012, alle ore 01:02, Paul Boddie ha scritto:

> Hello,
> 
> I just noticed that if I go to https://ep2011.europython.eu/, I get a 
> straight 
> redirect to https://ep2012.europython.eu/ (the front page) and not the 
> archived material at https://ep2012.europython.eu/ep2011/ (its specific 
> location). Would a more precise redirect not be nicer? I believe this was the 
> intention when we introduced year-specific sites.

Yes we can fix that.

We do have a problem with URLs though. The fact is that our web application is 
actually a multi-year application, that is meant to host contents for several 
years. Specifically, all paths under /conference are meant to be either 
referring to the current year or to the previous years, within the same 
website. For instance:

https://ep2012.europython.eu/conference/speakers/paolo-sammicheli

This is Paolo's profile page, and it makes sense "forever" the way it is now. 
It will link to his talks in the different conferences, and that's it. This 
fact (that the speaker page surives the multi-year versioning scheme) allows 
you to do a multi-year navigation of EuroPython contents, like seeing what the 
same speakers have talked in different years, search all talks by tag across 
different years, etc.

This page's URL used to be:
http://ep2011.europython.eu/conference/speakers/paolo-sammicheli

and if you go there, you get redirected to ep2012's URL, even if Paolo has not 
submitted a talk to ep2012 yet; it's just because the website application is 
now under ep2012.europython.eu; thus, to preserve all existing URLs, we had to 
do a redirection that preserves the path. This is also why the root path goes 
to this year's root path, even though we can special case that of course. 

There's also a few other things that you want to keep outside of the 
year-versioning scheme: eg: blog / RSS feed (unless you want to lose followers 
year after year).

So in a way the current URL scheme is not serving us well; it's a good way to 
have totally different websites each year, but it's a poor fit with our model 
of keeping multiple years within the same logical website to facilitate 
navigating and browsing the archives. With PyCon Italy, it used to be:

www.pycon.it/blog/*   - multi-year blog 
www.pycon.it/conference/*   - archived multi-year talk content
www.pycon.it/p3/*  - archived PyCon Tre (2009) website
www.pycon.it/p4/*  - archived PyCon Quattro (2010) website

but I can see that EuroPython needs to adapt to different groups managing the 
website, and thus having different websites.

So, what we can probably do is to evolve the current ep2011 archive into its 
own website (something like archive.europython.eu), that could use the current 
webapp "forever". We might even decide to import previous year's archives into 
it, so have a central point where all EuroPython talks are archived (btw, were 
talks videorecorded during UK EPs?), and this might make sense even if whoever 
succeeds us prefer a radically new website / webapp. Also, after we import 
everything, we could expose the content through a data API, so that it's easier 
to manage/migrate it in the future, should we change idea again.

> P.S. Nice to see https everywhere, by the way. :-)


Yup, I think it was due. We even got an explicit complaint about this, last 
year.
-- 
Giovanni Bajo   ::  ra...@develer.com
Develer S.r.l.  ::  http://www.develer.com

My Blog: http://giovanni.bajo.it





_______________________________________________
Europython-improve mailing list
Europython-improve@python.org
http://mail.python.org/mailman/listinfo/europython-improve

Reply via email to