[Inpycon] PyCon India Website for 2014

Anand Chitipothu anandology at gmail.com
Fri Oct 18 06:30:40 CEST 2013

On Thu, Oct 17, 2013 at 8:11 PM, Gora Mohanty <gora at mimirtech.com> wrote:

> On 17 October 2013 22:30, Anand Chitipothu <anandology at gmail.com> wrote:
> [...]
> > -1
> >
> > There are four things involved in making the website.
> >
> > 1. Artwork for the website (logo, footer images, other icons etc.)
> > 2. The visual design of the website (layout, colors etc.)
> > 3. Implementation (software for rendering pages, browser testing,
> support for mobile devices)
> > 4. Content
> >
> > I think 1 and 2 are very close and can't be separated. I don't think it
> makes sense to design a logo without knowing the color scheme that we are
> going to use for the website.
> >
> > From my experience of building PyCon India websites from last 4 years,
> our community is not good at doing visual design. I suggest to take help of
> a professional designer.
> >
> > We can take care of doing 3 and 4.
> We would like to be involved, though I know that I had
> volunteered this year, and not managed to finish much.
> If we can start planning now for next year, we would be
> able to commit to finishing things.
> I agree that 1 and 2 should be done by someone with
> proven design skills. If we cannot find such a volunteer,
> and the resources are available, it makes sense to hire
> a professional designer.

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.

> 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
> restyling.

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.

I'm fine with trying out new CMS, if it is considerably better. If not we
can stick to what we have now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20131017/edb3bc8b/attachment.html>

More information about the Inpycon mailing list