Dave,
I'm sure that postings will be required, because some questions may be
posed to the list for response to inclusion or exclusion of some parts
of the HTML. For example there appears to be a number of javascripts in
the pages.
Also I guess I can ask now, why is there pages for public & private
APIs?
I found on my project that through web analysis very few people
were actually accessing the API docs, so I removed them since they
were already available with the download. I'm not advocating this
in pgjdbc's case, by why two?
danap.
Dave Cramer wrote:
> Hi Dana,
>
> This is awesome! Keep us posted.
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Wed, Jul 24, 2013 at 2:24 PM, dmp <danap@ttc-cmc.net
> <mailto:danap@ttc-cmc.net>> wrote:
>
> In the last week I have evaluated the reduced list of tools for creating
> the new website by installing, using, and reviewing the documentation. A
> selection has been made to use Jekyll.
>
> The reason largely based on the two goals outlined in the initial thread
> and user responses.
>
> Goals:
>
>
> 1. Make the Site Easier To Maintain.
> 2. Allow Others to Contribute/Manage the Updates.
>
> Jekyll met those requirements better than the other options, Twitter
> Bootstrap was removed, because it is not a site generation tool as
> pointed out by feedback.
>
> The plan is to change the site to match the existing style of the
> postgresql.org <http://postgresql.org> site. As I begin this process
> of creating the scripted
> site I will post updates for review to:
>
> http://pgjdbc.ourbigsky.com/
>
> danap