> -----Original Message-----
> From: Gevik Babakhani [mailto:gevik@xs4all.nl]
> Sent: 10 June 2005 08:23
> To: 'Marc G. Fournier'; 'Josh Berkus'
> Cc: Dave Page; pgsql-www@postgresql.org
> Subject: RE: [pgsql-www] Proposal for building knowledgebase website.
>
>
> Wow! Did I create a monster or just awaken it? All I wanted
> to do was to
> build a kb to help us expand. :)
>
> Anyway, I missed yesterday's discussion (unfortunately). Now
> I read that the
> direction we agreed on yesterday is changed. (bye bye vision).
> We now want to use Bricolage. If you think this is what we
> need and it will
> help us achieve things we have been missing, then you have my
> full support,
> Let's see where THIS wind shall take us.
No, not entirely bye--bye vision :-). The idea is to use Bricolage to
generate the template* content that will be automatically integrated
with the main website (because the main site is built entirely from CVS,
I invisage the output from Bricolage being automatically checked into
the pgweb CVS - probably by a cron job). This will still need
integration with the main site, work in Bricolage to setup templates
etc, configuration of the auto-checkin of templates to the pgweb CVS,
and some way to navigate all the content. I'm not entirely sure that the
treeview idea will work - that will need investigation.
* Note there is conflicting use of the word template here. Bricolage (as
I understand it) inserts content into templates to produce the output.
In our framework it's the other way round - the template contains the
content, and the framework applys the formatting to it to produce the
output. So, content + a Bricolage template should be able to produce a
pgweb template!
Regards, Dave.