[Inpycon] PyCon India Website for 2014
gora at mimirtech.com
Sat Oct 19 08:26:30 CEST 2013
On 18 October 2013 10:00, Anand Chitipothu <anandology at gmail.com> wrote:
> On Thu, Oct 17, 2013 at 8:11 PM, Gora Mohanty <gora at mimirtech.com> wrote:
> For PyCon India 2013 website, the designer spent about 2 weeks time
> designing the website and I spent almost equal amount of time implementing
> the details. I think what I did could've been split and done by multiple
> people, but couldn't do it because of last minute. If we plan well, we'll be
> able to manage that this year. But I still think the designing has to be
> done by a one person who understands the design.
Agreed: Design should be done by one person, though the
implementation work can be shared by many people.
>> Anand, while I think that you should be the one taking
>> major decisions for the site, I would advocate moving
>> to a CMS-based site, with HasGeek's funnel. My choice
>> would be django and feincms, but that is open to debate.
>> For future years, I strongly feel that all the work that
>> should be needed should be content population, and
> We already have a CMS. EventFrame is the opensource software that we used,
> which is again written in Python. It can have multiple pages and those pages
> can be edited by admins. I think what we lack is good editors. People who
> can think about how to organize content and write well.
Yes, I am aware that eventframe functions like a rudimentary CMS
(a) There is just too much work involved in cloning the repo, configuring
and setting things up. Once a CMS is set up, all work can be done
through the admin back-end.
(b) The CMS is far from where it can be comfortably used by non-technical
people. Agreed with you that we need good editors. Technical people
are typically bad at writing content, and we should get to a level where
someone can contribute content with as little difficulty as possible.
> I'm fine with trying out new CMS, if it is considerably better. If not we
> can stick to what we have now.
Good point: Let's think about what we want, and I can set up a
demo. Will get back to you on this.
More information about the Inpycon