[Inpycon] Site problem

[Anand Chitipothu]

On Tue, 21 Jun 2016 at 02:02 Kracekumar Ramaraj <me at kracekumar.com> wrote:

> On Mon, Jun 20, 2016 at 10:39 PM, Noufal Ibrahim KV <
> noufal at nibrahim.net.in> wrote:
>
>> On Mon, Jun 20 2016, Saurabh Kumar wrote:
>>
>>
>> [...]
>>
>> > That's a valid concern, especially w.r.t to using same theme for each
>> > year post. Once of quick solution I can think of is having a generic
>> > theme so 2015's articles, doesn't look like 2016's articles.
>>
>> That'll just make it more confusing. It's good to have two separate
>> themes/branding otherwise this would never have been caught.
>>
>> > Creating blog per year, creates a bit of management/devops overhead.
>> > Although I don't the capabilities of volunteers to make it happen.
>>
>> Okay. I'm not sure how it's run now but earlier, an app would run at
>>
>>       in.pycon.org/<current year>
>>
>> and once the conference was over, we'd wget the site recursively and
>> just replace the live app with the static files. That way, the URLs
>> won't break and the site would be maintained but there's no overhead of
>> maintaining an app.
>>
>>       This was the what we did for 2009, 2010 and I think for 2011.
>>
>
> For past 3 years, blog engines were different, Jekyll and Pelican. Blogs
> are content heavy.
> Design team provides static site and volunteers convert the layout to blog
> engine theme.
> This grunt work is required for every year.
>
> This is matter of taste and don't see a real value. Though the url
> redirect/rewrite can be done at top level.
>
> http://in.pycon.org/2016/blog/ -> http://in.pycon.org/blog/2016/
>

It is not only a matter of taste but also a lot convenient when you want to
archive the website of a past conference. Everything in 2015, including
blog can be served statically.

Anand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20160620/9755649d/attachment-0001.html>