Hi Richard, I might be in a minority on this list for suggesting that the SQLite website could indeed become more helpful and informative through a redesign.
I am not suggesting that the redesign necessarily be focused on attractiveness, although, there can be some correlation in ease of use and general attractiveness. I do think that it needs to be embellished with more information, and with more ease to find that information. Here are some concrete examples -- 1. Perhaps the greatest improvement would occur if we enhance the syntax section with more examples, particularly in the EXPRESSION sub-section. Some functions are just not clear (for example, what does glob(X,Y) do... granted, I can probably search for it and find examples, but examples right there would be very helpful). Bringing the date and time functions from the wiki to the syntax page would be more direct and helpful. Having examples for each and every command would be very useful and also educational. On this email list what I learn about SQL is waaaaay more than what I learn about SQLite, and expanding the syntax section would go a long way toward achieving both these aims. 2. An extension web project for SQLite and its various language wrappers would be very useful. Perhaps that could be accomplished by sub-wikis. Some might contend that language-specific documentation belongs with that language website, and that would be not an invalid argument, but if the focus of the SQLite website is to promote the use of SQLite no matter what language is being used, then the SQLite website should try to accomplish, or enable accomplishing of, this goal even if it means possibly creating redundant websites. 3. A user-editable list of frequently used tasks -- - how to rename a table - how to import export data - how to deal with blobs - creating use-defined functions - implementing full-text search In all of the above cases, a wiki style that allows users to add comments right on the documentation pages would be great. Once set up, it will be up to the users to populate it with useful content. This has worked well in other projects and would work well here. Of course, a version *without* user-generated content would still be included in the source code so users can build one themselves for their local, offline use. On 11/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > We are looking at renovating the design of the SQLite > website and would love to have suggestions from the > community. If you have any ideas on how to improve > the SQLite website, please constribute either to the > mailing list or directly to me. > > Here are some links to competing database products > that might inspire comments: > > http://www.postgresql.org/ > http://www.firebirdsql.org/ > http://www.hsqldb.org/ > http://opensource.ingres.com/ > http://db.apache.org/derby/ > http://exist.sourceforge.net/ > > Among the comments received already are these: > > (1) It is not clear from the homepage that the software > is free. > (2) Half the page is devoted to talking about bugs in > the software. This suggests low quality. > (3) The "News" contains scary words: "radical changes". > (4) Three releases in as many months suggests the > code is not stable. > (5) Move the BigNameUsers to the front page > (see http://www.sqlite.org/wiki?p=BigNameUsers) > (6) Need more eye-candy. > > I do not necessary agree with the above comments, but I > am open to any and all ideas. You will not hurt my feels, > so speak freely. > > Thanks in advance for your input. > > -- Puneet Kishor ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
