Обсуждение: proposal to simplify the website
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 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 ?
Dave Cramer
On 04/24/2013 03: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 > 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. Sounds like a good idea to me. -- Glenn Holmer Weyco Group, Inc. phone: 414-908-1809 fax: 414-908-1601
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 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
John,
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,
On Thu, Apr 25, 2013 at 12:59 PM, John R Pierce <pierce@hogranch.com> wrote:
On 4/24/2013 1:39 PM, Dave Cramer wrote: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...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 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 ?
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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
On Thu, 25 Apr 2013, Dave Cramer wrote: > 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 concern is that without any templating system at all, some simple changes are going to require a copy and paste into every single page. Don't we need something beyond plain static pages that are directly edited? Forrest is kind of a dead project at this point, but there are a ton of other templating systems that generate static pages that are much more lightweight than Forrest. Shouldn't we consider one of them? Kris Jurka
Kris,
How many changes go everywhere ?
Any suggestions on a simple templating system ?
On Thu, Apr 25, 2013 at 1:48 PM, Kris Jurka <books@ejurka.com> wrote:
My concern is that without any templating system at all, some simple
On Thu, 25 Apr 2013, Dave Cramer wrote:
> 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.
>
changes are going to require a copy and paste into every single page.
Don't we need something beyond plain static pages that are directly
edited?
Forrest is kind of a dead project at this point, but there are a ton of
other templating systems that generate static pages that are much more
lightweight than Forrest. Shouldn't we consider one of them?
Kris Jurka
Simplify website? Maven site + github pages?
Javadoc is generated by maven: http://searls.github.io/jasmine-maven-plugin/apidocs/index.html
__________________________
Shijun Kong
From: Dave Cramer <pg@fastcrypt.com>
Date: Thursday, April 25, 2013 3:36 PM
To: Kris Jurka <books@ejurka.com>
Cc: John R Pierce <pierce@hogranch.com>, "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Subject: Re: [JDBC] proposal to simplify the website
Date: Thursday, April 25, 2013 3:36 PM
To: Kris Jurka <books@ejurka.com>
Cc: John R Pierce <pierce@hogranch.com>, "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Subject: Re: [JDBC] proposal to simplify the website
Kris,
How many changes go everywhere ?
Any suggestions on a simple templating system ?
On Thu, Apr 25, 2013 at 1:48 PM, Kris Jurka <books@ejurka.com> wrote:
My concern is that without any templating system at all, some simple
On Thu, 25 Apr 2013, Dave Cramer wrote:
> 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.
>
changes are going to require a copy and paste into every single page.
Don't we need something beyond plain static pages that are directly
edited?
Forrest is kind of a dead project at this point, but there are a ton of
other templating systems that generate static pages that are much more
lightweight than Forrest. Shouldn't we consider one of them?
Kris Jurka
This email message and any attachments may contain legally privileged or confidential information intended solely for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution or copying of this message or its attachments is strictly prohibited. If you have received this message in error, please notify us immediately by telephone, fax or email and delete the message and all attachments to the message. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Investor Analytics LLC.
Shijun Kong wrote: > Simplify website? Maven site + github pages? > > http://pages.github.com/ > > _sample: _http://searls.github.io/jasmine-maven-plugin/ > _Javadoc is generated by maven: > _http://searls.github.io/jasmine-maven-plugin/apidocs/index.html > > * > __________________________ > * > Shijun Kong I'm really not a fan of github. Yes I use it to host a project, but it is slow and I would not put a web site on it. If that is what is desired then someone else can do it. > > From: Dave Cramer <pg@fastcrypt.com <mailto:pg@fastcrypt.com>> > Date: Thursday, April 25, 2013 3:36 PM > To: Kris Jurka <books@ejurka.com <mailto:books@ejurka.com>> > Cc: John R Pierce <pierce@hogranch.com <mailto:pierce@hogranch.com>>, > "pgsql-jdbc@postgresql.org <mailto:pgsql-jdbc@postgresql.org>" > <pgsql-jdbc@postgresql.org <mailto:pgsql-jdbc@postgresql.org>> > Subject: Re: [JDBC] proposal to simplify the website > > Kris, > > How many changes go everywhere ? > > Any suggestions on a simple templating system ? > > > > Dave Cramer > > dave.cramer(at)credativ(dot)ca > http://www.credativ.ca > > > On Thu, Apr 25, 2013 at 1:48 PM, Kris Jurka <books@ejurka.com > <mailto:books@ejurka.com>> wrote: > > > > On Thu, 25 Apr 2013, Dave Cramer wrote: > > > 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 concern is that without any templating system at all, some simple > changes are going to require a copy and paste into every single page. > Don't we need something beyond plain static pages that are directly > edited? > > Forrest is kind of a dead project at this point, but there are a ton of > other templating systems that generate static pages that are much more > lightweight than Forrest. Shouldn't we consider one of them? > > Kris Jurka When Dave first brought this up to me I was against a CMS site. Yes there maybe some simple ones out there, but: 1. They do required a learning curve, 2. It has to stay well maintained from the development side otherwise it is going to get hacked. 3. If your content is not changing much it is not really worth it. A mainly static site should be fine with CSS template and some scripting to handle the areas that change, todo list and downloads that I know of provided the host server allows a perl/python and a database. If a simple CMS site software or other templating system is desired I can do the research, but will not guarantee that I will sign on to implement. danap.
Jekyll [1] (as made famous by github pages [2]) has to be one of the more widely used at this point. Content in html or e.g. markdown, with page templating etc. Not very hard to set up, plus a bunch of people know it now due to github pages integration.
We could easily set up a post-commit hook or cron job to pull the site down and run jekyll.
Cheers
Tom
On 26 April 2013 05:06, Dave Cramer <pg@fastcrypt.com> wrote:
Kris,How many changes go everywhere ?Any suggestions on a simple templating system ?On Thu, Apr 25, 2013 at 1:48 PM, Kris Jurka <books@ejurka.com> wrote:My concern is that without any templating system at all, some simple
On Thu, 25 Apr 2013, Dave Cramer wrote:
> 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.
>
changes are going to require a copy and paste into every single page.
Don't we need something beyond plain static pages that are directly
edited?
Forrest is kind of a dead project at this point, but there are a ton of
other templating systems that generate static pages that are much more
lightweight than Forrest. Shouldn't we consider one of them?
Kris Jurka