Re: [Firebird-website] Structure of website proposal - 1st draft

[Martijn T. <m.t...@up...>]

> >> www.firebirdsql.org
> >> Main page, downloads.
> >
> > + About us (intro, history, licenses, SQL compliance, success stories,
> > etc) -- an absolute must have there, IMHO
>
> Is History item really inportant? ...
>
> >> developers.firebridsql.org
> >> Sub-site dedicated to developers. Each sub-project has it's own space
here.
> >
> > Maybe just define core.fbsql.org, jaybird.fbsql.org, etc? I'm expecting
> > every sub-site to have separate layouts (optimized for its purposes),
> > while still sharing the design concept with other sub-sites and the home
> > page. Right now we have quite a lot of differences between sub-project
> > pages, so they don't seem fitting each other well, this is why I think
> > that probably separate development sub-sites would suit us better.
>
> I think this will be overhead. Too much sub-sites ... I don't think,
> that Java, .NET, Python etc. drivers will have too much different
> sites. Maybe just core engine, but maybe not.

I'd suggest:

code.fb.org
drivers.fb.org
documentation.fb.org
foundation.fb.org


Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Sybase
SQL Anywhere, Oracle & MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com