Menu
▾
▴
firebird-website
|
From: Jiri C. <di...@ci...> - 2008-10-09 15:18:03
|
Hello *,
consider this as a 1st concept. Take it, "mashup" it, do it best. :)
I would like to have new structure absolutely clear in first and
second level. Then it can be bunch of pages. The first level will be
as a main guide-post. The second level for good orientation in section
(links, navigation bar, ...)
So my propose is:
/download
./firebird
./2.5
./2.1
...
./net-provider
./jaybird
...
/documentation
./firebird
./2.5
./release-notes
./lang-ref
...
./2.1
./net-provider
...
/development
/resources
./news
./mailing-lists
./tracker
./conferences
...
/foundation (maybe can be under other)
/other
./licensing, FB brand, logos, everything else
It's not much different from current state, just little tune up.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
|
|
From: Dmitry Y. <fir...@ya...> - 2008-10-09 15:48:12
|
Jiri Cincura wrote: > > consider this as a 1st concept. Take it, "mashup" it, do it best. :) Please don't consider my words a critique of your draft proposal, but I believe we should do some preliminary steps before: - set up a set of categories our pages could belong to - enumerate all the existing pages and assign them appropriate categories (multiple choices are allowed) - rank the categories by number of pages This would show us what menu items and sidebar sections would suit our contents better. I don't think that e.g. Download or Documentation sections require this approach, but some others IMHO do. Dmitry |
|
From: Jiri C. <di...@ci...> - 2008-10-09 16:03:16
|
On Thu, Oct 9, 2008 at 5:47 PM, Dmitry Yemanov <fir...@ya...> wrote:
> Please don't consider my words a critique of your draft proposal, but I
Absolutely not. Every good idea counts.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
|
|
From: Jorge A. B. <li...@da...> - 2008-10-09 18:19:14
|
I like the PostgreSQL website (http://www.postgresql.org/) organization. maybe some ideas can be taken from there (like "shorcuts"). Dmitry Yemanov escribió: > Jiri Cincura wrote: > >> consider this as a 1st concept. Take it, "mashup" it, do it best. :) >> > > Please don't consider my words a critique of your draft proposal, but I > believe we should do some preliminary steps before: > > - set up a set of categories our pages could belong to > - enumerate all the existing pages and assign them appropriate > categories (multiple choices are allowed) > - rank the categories by number of pages > > This would show us what menu items and sidebar sections would suit our > contents better. I don't think that e.g. Download or Documentation > sections require this approach, but some others IMHO do. > > > Dmitry > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Firebird-website mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-website > > > -- Jorge Andrés Brugger Informática DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia Comodoro Rivadavia, Chubut, Argentina Teléfono (0297) 446-4444 int. 103 Correo electrónico: jbr...@da... Website: www.dasu.com.ar |
|
From: Dmitry Y. <fir...@ya...> - 2008-10-09 18:44:32
|
Jorge Andrés Brugger wrote: > I like the PostgreSQL website (http://www.postgresql.org/) organization. > maybe some ideas can be taken from there (like "shorcuts"). Actually, their shortcuts are pretty much the same as our sidebar (which just requires simplification, IMHO). The core idea of the layout is also the same: logo, menu bar, hot news balloon, releases/shortcuts/support sidebar and the blog-style area. The only difference is that they have three categories there (news/events/planet) while we have only one. I believe a combination of smarter sidebar, minor reorganization of the main page and new professional style/graphics will bring us at least to the same level as pgsql :-) Dmitry |
|
From: marius p. <ma...@gm...> - 2008-10-09 18:51:00
|
On Thu, Oct 9, 2008 at 9:44 PM, Dmitry Yemanov <fir...@ya...> wrote: > Jorge Andrés Brugger wrote: > >> I like the PostgreSQL website (http://www.postgresql.org/) organization. >> maybe some ideas can be taken from there (like "shorcuts"). > > Actually, their shortcuts are pretty much the same as our sidebar (which > just requires simplification, IMHO). The core idea of the layout is also > the same: logo, menu bar, hot news balloon, releases/shortcuts/support > sidebar and the blog-style area. The only difference is that they have > three categories there (news/events/planet) while we have only one. > After we agree on the website structure we can do some html test pages that will be integrated later by the firebird webmasters :) > I believe a combination of smarter sidebar, minor reorganization of the > main page and new professional style/graphics will bring us at least to > the same level as pgsql :-) I agree we will work to do an better website than them And definitely we will not the mysql way :) > > > Dmitry > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Firebird-website mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-website > -- developer flamerobin.org |
|
From: Pavel C. <pc...@ib...> - 2008-10-10 10:27:10
|
Jiri Cincura napsal(a): > > consider this as a 1st concept. Take it, "mashup" it, do it best. :) > > I would like to have new structure absolutely clear in first and > second level. Then it can be bunch of pages. The first level will be > as a main guide-post. The second level for good orientation in section > (links, navigation bar, ...) The core problem with our website is that it is (or should be) a tool for several distinct (yet often overlapping) groups of users: - First time visitors: They're looking for download and basic introductory information - Casual visitors: They're looking for news and latest releases to update - Users looking for documentation - Users interested in details what's going on in each sub-project (dev. updates, road maps, source code, dev. documentation, tracker, lists etc.) - Projects developers: to work with information that is not suitable to get buried in mail archives, like RFC's, road maps etc. They need wiki or pages with comment threads. - People interested and/or involved in community: Events, job board, lists, attached projects (like FlameRobin) etc. - Foundation. The current mess we have to deal with is result of our attempt to hold all this in single big site where you can directly go from any area to another, that evolved from small site over many years of adding content and sub-areas. This simply doesn't work. To fix that, we have to split the site into several (cross-linked) purpose-oriented sub sites, where the main page is mere portal with most prominent headlines and links to each sub-site (mozilla.org main page is good example of this structure). To make navigation and management more easy, I would like split the site into several logical sites (preferably on the same host) with different sub-domains: www.firebirdsql.org Main page, downloads. news.firebridsql.org News-style pages for each sub-project or group, with aggregation on main page of this sub-site. Also produces RSS feeds and widgets for embedding into other site pages. Handles history for all these news. doc.firebirdsql.org Sub-site dedicated to documentation, holds documents, FAQ, wiki. developers.firebridsql.org Sub-site dedicated to developers. Each sub-project has it's own space here. community.firebirdsql.org Sub-site dedicated to community communication channels, events, job boards, etc. foundation.firebirdsql.org Firebird Foundation web space. The main page would serve as hub to direct first time or casual visitor around, i.e. big blurbs to get download and introductory information quickly, jump gate to each sub-site and some breaking news from around the project. The metaphor: Get IT (jump to download), Learn IT (jump to doc), Share experience (jump to community), Develop IT (jump to developers), Support IT (jump to foundation). Frequent users would typically go directly to the sub-site of their main or current interest: news, doc, developers, community, foundation. And because they have their own sub-domain, it's easy to bookmark them or use smart URL box that current browsers provide. All sub-sites should preferably use the same theme / skin and header with top menu going to other sub-sites. They should use combination of side bar with location bar (textual top menu bar below header in form <main> / <level 1> / <level 2> ...) for navigation within sub-site (developers.mozilla.org is good example of this structure). best regards Pavel Cisar IBPhoenix Firebird QA & web site |
|
From: Lester C. <le...@ls...> - 2008-10-10 10:53:38
|
Pavel Cisar wrote: > All sub-sites should preferably use the same theme / skin and header > with top menu going to other sub-sites. They should use combination of > side bar with location bar (textual top menu bar below header in form > <main> / <level 1> / <level 2> ...) for navigation within sub-site > (developers.mozilla.org is good example of this structure). Something bitweaver can handle quite happily ... You already have wiki.firebirdsql.org set up, just need to add the rest. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php |
|
From: Dmitry Y. <fir...@ya...> - 2008-10-23 04:44:20
|
Pavel Cisar wrote: > > The current mess we have to deal with is result of our attempt to hold > all this in single big site where you can directly go from any area to > another, that evolved from small site over many years of adding content > and sub-areas. This simply doesn't work. To fix that, we have to split > the site into several (cross-linked) purpose-oriented sub sites, where > the main page is mere portal with most prominent headlines and links to > each sub-site (mozilla.org main page is good example of this structure). While being basically agreed with this idea, I believe we should think more about the home page contents. There could be some other important things (aside from the sub-area links) to be placed there. For example, I have a strong feeling that some kind of news (basic or aggregated) should exist on the main page instead of being located in the dedicated news area only. As you could see, many similar projects (e.g. the ones posted by Roman) share this concept. Also, we could have a sponsored links area that would allow us to get money for placing commercial offers on the main page (it is unlikely to work well if placed elsewhere). > www.firebirdsql.org > Main page, downloads. + About us (intro, history, licenses, SQL compliance, success stories, etc) -- an absolute must have there, IMHO > news.firebirdsql.org > News-style pages for each sub-project or group, with aggregation on main > page of this sub-site. As mentioned above, I'd prefer to see the aggregation on the main page of the site. We don't seem to have so many news to split them between sub-projects, so I think a dedicated sub-site is an overkill for the time being... > 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. > The main page would serve as hub to direct first time or casual visitor > around, i.e. big blurbs to get download and introductory information > quickly, jump gate to each sub-site and some breaking news from around > the project. The metaphor: Get IT (jump to download), Learn IT (jump to > doc), Share experience (jump to community), Develop IT (jump to > developers), Support IT (jump to foundation). > > All sub-sites should preferably use the same theme / skin and header > with top menu going to other sub-sites. They should use combination of > side bar with location bar (textual top menu bar below header in form > <main> / <level 1> / <level 2> ...) for navigation within sub-site > (developers.mozilla.org is good example of this structure). Sounds okay to me. Dmitry |
|
From: Pavel C. <pc...@ib...> - 2008-10-23 08:28:37
|
Dmitry Yemanov napsal(a): > > While being basically agreed with this idea, I believe we should think > more about the home page contents. There could be some other important > things (aside from the sub-area links) to be placed there. For example, > I have a strong feeling that some kind of news (basic or aggregated) > should exist on the main page instead of being located in the dedicated > news area only. As you could see, many similar projects (e.g. the ones > posted by Roman) share this concept. I basically agree with you, but it's not high on my priority list for main page, where each inch of real estate is a valuable commodity. We can show up one, three or five top news subjects here with link to the rest, but you know, news items are strange beasts. It depends on how many we'll produce, not all are of the same importance (and the importance if often just in the eye of the submitter) etc. > Also, we could have a sponsored > links area that would allow us to get money for placing commercial > offers on the main page (it is unlikely to work well if placed elsewhere). That's very good idea. >> www.firebirdsql.org >> Main page, downloads. > > + About us (intro, history, licenses, SQL compliance, success stories, > etc) -- an absolute must have there, IMHO These things are certainly an option to consider for main page, as at least links to complete info, but I'd like keep main page simple (it's easier then to locate desired information). If we would manage to squeeze it all or some more on main page in reasonably readable way, so be it, but lucidity is the only measure for main page. >> news.firebirdsql.org >> News-style pages for each sub-project or group, with aggregation on main >> page of this sub-site. > > As mentioned above, I'd prefer to see the aggregation on the main page > of the site. We don't seem to have so many news to split them between > sub-projects, so I think a dedicated sub-site is an overkill for the > time being... Well, the idea is to have an aggregating news engine there, where we can easily add new news sources (local or remote via RSS feeds) with automatic history archive. You can browse aggregated main page or individual news sources. These sources could be news tracks from sub-projects, individuals (aka blogs), foundation, topic focused (like releases, outages) etc. With RSS feeds available for each. It would be possible to put any selection of news to nay page within the site if necessary. >> 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. Well, the sub-sites were meant to be just apache configuration thing that would make bookmarking and direct jumps using URL box of the browser more easy. There is nothing that would stop anybody to use different design, layouts etc. between dev. sub-sites accessible via url developer.firevirdsql.org/<subprojectname>. And as we have to be consistent and we have a lot of sub-projects (with potentially more in future), I guess we'll end with too much sub-domains which would beat their purpose. best regards Pavel Cisar IBPhoenix |
|
From: Martijn T. <m.t...@up...> - 2008-10-23 08:34:50
|
> >> 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 |
|
From: Jiri C. <di...@ci...> - 2008-10-23 07:27:03
|
>> 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. -- Jiri {x2} Cincura (CTO x2develop.com) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com |
|
From: Dmitry Y. <fir...@ya...> - 2008-10-23 08:39:20
|
Jiri Cincura wrote: > > Is History item really inportant? ... Being accessible directly from a home page? I don't think so. The point was that this information (the entire "about us" subsection) should be a part of the main sub-site contents (www.fbsql.org one), not on docs.fbsql.org or elsewhere. As for the home page, I'd be happy with just an "About Us" link that points to the sub-section with appropriate articles. And may be some quick link (intro? quick start guide?) on the sidebar (if we'll decide to have one). >> 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 ... We're here to share ideas :-) I'm not insisting on anything. Dmitry |
|
From: Jiri C. <di...@ci...> - 2008-10-23 08:54:38
|
On Thu, Oct 23, 2008 at 10:38 AM, Dmitry Yemanov <fir...@ya...> wrote:
> As for the home page, I'd be happy with just an "About Us" link that
> points to the sub-section with appropriate articles. And may be some
> quick link (intro? quick start guide?) on the sidebar (if we'll decide
> to have one).
I see the point and completely agree.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
|
|
From: Carlos H. C. <li...@wa...> - 2009-02-25 13:49:02
|
From: http://w-shadow.com/blog/2009/02/25/top-4-free-embedded-databases/ - A notably confusing and disjointed website. I had to dig around for a while to find out what I needed to know. Some sections also present outdated information. - If you casually browse around Friebird’s site you may get the impression that the embedded version only works with .NET (they even have an entire sub-website dedicated to the .NET version). However, you can actually use it with many other languages by downloading the embedded version and using the standard Firebird APIs. []s Carlos H. Cantu www.FireBase.com.br - www.firebirdnews.org www.warmboot.com.br - blog.firebase.com.br |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X