Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 1457940DB0E for ; Wed, 28 Mar 2012 16:45:11 -0300 (ADT) Received: from huggy.petdance.com ([72.14.176.61]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SCynr-0007FP-TP for pgsql-docs@postgresql.org; Wed, 28 Mar 2012 19:45:10 +0000 Received: from [172.28.1.125] (host3130.follett.com [12.47.12.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: andy) by huggy.petdance.com (Postfix) with ESMTP id 52D4D41C04C; Wed, 28 Mar 2012 15:44:53 -0400 (EDT) Subject: Re: Adding links to alternate versions of doc pages Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: multipart/alternative; boundary="Apple-Mail=_1549A4D3-4987-4509-A4BF-64A797DD1EC0" From: Andy Lester In-Reply-To: <4F734B96.9020102@enterprisedb.com> Date: Wed, 28 Mar 2012 14:45:13 -0500 Cc: Greg Sabino Mullane , pgsql-docs@postgresql.org Message-Id: <505D0FCA-DB66-416D-98D5-24176D8D2BDD@petdance.com> References: <4F734B96.9020102@enterprisedb.com> To: Heikki Linnakangas X-Mailer: Apple Mail (2.1257) X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/31 X-Sequence-Number: 7230 --Apple-Mail=_1549A4D3-4987-4509-A4BF-64A797DD1EC0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On Mar 28, 2012, at 12:34 PM, Heikki Linnakangas wrote: > I totally agree, I am often google annoyed by this, too. Patch, please = ;-) My vague plan is to take the source docs and the process for it, and = modify from there and create a sample website, say, = newdocs.petdance.com, that I could point y'all at and get feedback. = =46rom there, I can actually create a patch once we're happy with the = end results. I will be more than happy to work to make this happen. What I don't = know, however, is anything at all about how the docs in the tarballs get = put out into HTML pages on the website. As in, zero, nada, zip. Can = someone please point me at docs that describe this process? And/or help = me to understand the backend so that I can work to make a prototype? Thanks, Andy -- Andy Lester =3D> andy@petdance.com =3D> www.petdance.com =3D> = AIM:petdance --Apple-Mail=_1549A4D3-4987-4509-A4BF-64A797DD1EC0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1

I totally = agree, I am often google annoyed by this, too. Patch, please = ;-)

My vague = plan is to take the source docs and the process for it, and modify from = there and create a sample website, say, newdocs.petdance.com, that I = could point y'all at and get feedback. =46rom there, I can = actually create a patch once we're happy with the end = results.

I will be more than happy to work to = make this happen. What I don't know, however, is anything at all = about how the docs in the tarballs get put out into HTML pages on the = website. As in, zero, nada, zip. Can someone please point me = at docs that describe this process? And/or help me to understand the = backend so that I can work to make a = prototype?

Thanks,

Andy

<= /div>

--
Andy Lester = =3D> andy@petdance.com =3D> = www.petdance.com =3D> AIM:petdance

= --Apple-Mail=_1549A4D3-4987-4509-A4BF-64A797DD1EC0--