Skip site navigation (1) Skip section navigation (2)

Re: Bricolage: Impressive

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Steve Simms <steve(at)deefs(dot)net>
Cc: PostgreSQL Web Development Mailing List <pgsql-www(at)postgresql(dot)org>
Subject: Re: Bricolage: Impressive
Date: 2004-01-17 19:12:30
Message-ID: Pine.GSO.4.58.0401172206480.3310@ra.sai.msu.su (view raw or flat)
Thread:
Lists: pgsql-www
I'm also voted for Bricolade, because it's based on Mason, which I
personally have use a lot on many projects.
Multilingual support could be implemented on top of Mason, see
for example www.pgsql.ru

We use custom tag
<* ru=>'something in russian', en=>'the same in english' *>

If you need function call we have i18n(ru=>'...', en=>'....');

Of course, our approach doesn't limited by 2 languages.
We found it's much easier and maitainable for small evolving projects to
use that approach (inline), than gettext, because it's easy just edit
component. But, for stable project, gettext would be better.


	Oleg
On Sat, 17 Jan 2004, Steve Simms wrote:

> First, a brief introduction, since I started working off-list: I expressed
> some interest in helping work with the web site some months ago to Josh
> Berkus, and was directed to Dave, and possibly Robert.  I think an E-Mail got
> lost somewhere, however, so I didn't get further involved at that point.
>
> Last week, roughly around the same time as all the other new folks signed on
> to this list, I sent a message to Robert, Dave, and Marc asking if I could
> help, and was directed to try out Bricolage as a possible way of powering the
> Techdocs site.
>
> My background is in Linguistics, with a fair bit of work and credit in
> evaluating web sites for usability.  I'm employed with the job title of
> "Database Developer & Administrator", which involves maintaining our
> PostgreSQL installation and writing most of the interface programs that are
> used by the company's employees.  This is done using Apache + Perl + Mason,
> and I'm very familiar with the last two in particular.
>
> </end introduction>
>
> I now have a working installation of Bricolage installed, and have a better
> understanding of how it works.  In a word, it's impressive.  Unless our
> requirements for multilingualism (see previous message) prevent us from using
> it, I think it's a very good candidate for generating/unifying all of the
> PostgreSQL sites.
>
> It was designed for daily use by journalists, who are not interested in
> learning any form of markup, and who in most cases are not *allowed* to do any
> form of markup, since this is handled by the site.  They write their articles
> using plain text, generally as a sequence of paragraphs, though it's possible
> to intersperse other user-definable "elements" such as headings, quotes, etc.
> For instance, we could have an element called "SQL Code" that would be used
> for examples.  Josh Berkus' "Adventures in SQL" would then be a series of
> "Paragraph" blocks interspersed with "SQL Code" blocks.
>
> [This is not a complicated process, either.  By the look of it, I could easily
> move one of Josh's articles into Bricolage in under five minutes, just using
> copy and paste from my browser.]
>
> Each type of contribution has a workflow associated with it.  By default, an
> article would go through the Edit Desk, Review Desk, Legal Desk, and Publish
> Desk.  The workflow is completely customizable, so we could remove the Legal
> Desk, add a Translator's Desk, for example.  It contains a complete audit
> trail, and you can easily revert to an older version, if necessary.
>
> Once an article gets to the Publish Desk, it gets "burned" into HTML by going
> through a Mason template (default) or an HTML::Template template (alternate).
> This template provides all of the markup and site layout functions, and
> results in a plain HTML file, which can be automatically sent to any number of
> locations by a variety of means (FTP and File System are available by default;
> there may be others, and a simple cron job could fill in the gaps).
>
> The Bricolage server can be run from anywhere -- it need not (and arguably
> should not) be at www.postgresql.org:80.  The result is that a web server need
> only serve plain HTML files, for maximum efficiency and ease of installation
> and maintenance.
>
>
> Based on what I understand of Plone and Bricolage, and of what we want, it
> looks like Bricolage is the far better candidate, at least once you get around
> the barrier of getting it set up.  This is purely my opinion, however.
>
> I'll keep working on it, and see if I can get a simulation of the current
> TechDocs site going.
>
> Steve Simms
> Database Developer & Administrator
> Medical Media Systems, Inc.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Responses

pgsql-www by date

Next:From: Marc G. FournierDate: 2004-01-17 22:04:45
Subject: Re: Bricolage: Impressive
Previous:From: Steve SimmsDate: 2004-01-17 18:29:27
Subject: Bricolage: Impressive

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group