Re: proposal to simplify the website

John,

The machines that host the sites are not setup with CMS. There isn't that
much content and every CMS I've ever seen has a learning curve. This is
simple, store the html in git, pull it to the machine

The biggest part of the site is the API docs, which is generated with
javadoc.

My goal is to make it simple, currently it took me a few days to figure out
forrest, and since it's auto generated I have no idea if it's correct,
except to read everything. This proposal allows simple changes

Thanks,

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Thu, Apr 25, 2013 at 12:59 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:

> On 4/24/2013 1:39 PM, Dave Cramer wrote:
>
>> Currently the jdbc website requires working knowledge of forrest and
>> seems to be a considerable barrier to entry to making changes.
>>
>> Just this week the ODBC guys changed their site to be a static site based
>> on the main site's template http://psqlodbc.projects.**pgfoundry.org<http://psqlodbc.projects.pgfoundry.org>I am proposing a similar solution. Dana has offered to take on the task of
>> changing it over but understandably doesn't want to waste his time if it
>> won't be used.
>>
>> thoughts ? constructive criticism ?
>>
>
> wouldn't a site based on a CMS that could be managed by multiple people
> without direct file access make more sense? something blog or wiki
> based, perhaps? sure, more effort up front to develop...
>
> or is the community of "jdbc website contributors" so small that giving
> them each ssh access to the entire site is acceptable ?
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-jdbc<http://www.postgresql.org/mailpref/pgsql-jdbc>
>