Re: [Firebird-website] Redesign of our website - feature requests in tracker

[Jiri C. <di...@ci...>]

On Wed, Oct 1, 2008 at 9:40 AM, Roman Rokytskyy <rro...@ac...> wrote:
> I see two aspects of the redesign. One is the visual representation,
> which can be done by the designer without any problem. But another side
> is the content itself, which, I suspect, cannot be task for the
> designer. And I am pretty sure that we should discuss the issues with
> the content before the we start the visual part.

I think, we should do this in simple and clear steps. IMO the new
website should be, in first, focused on "providing information". What
you need as a visitor? Get the Firebird, get some documentation, see
news and maybe where to ask. Are you interested in who is in core
engine team? No. And so on. If you work with Firebird, you will know
the site a little bit, so you will be able to find i.e. who's who in
core team ...

I propose to do it like:
1. Get some concensus on *structure* of web (this is IMO critical part
of success for this project).
2. Choice some design from preview or get some thoughts about it to designer.
3. Get some PHP (or something like that) code to make it working. It's
mainly static content (except documentation, download and news part),
so it's not so hard to do it. Three exceptions above can be done
easily too.

I also think, that using some CMS or blog-like SW isn't necessary
because only few people are changing site. Our web isn't huge or
difficult, the PHP background can be done in a few days (and I can do
it, if this project is interested).

-- 
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com