Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Rich Bowen <rbowen@rcbowen.com>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_C685E979-066B-4362-84D5-BC29457A9FEC"
Subject: Re: Proposal to move docs to Apache CMS
Date: Mon, 30 Apr 2012 12:21:45 -0400
In-Reply-To: <A132A198-5E1F-40DC-B540-0828AA4B9285@rcbowen.com>
To: docs@httpd.apache.org
References: <201204242006.24835@news.perlig.de>
 <5a358e5c-97c8-435c-ba4e-6f92410b8432@iris> <20120425125052.GN7563@toftum.dk>
 <C1D24009-7F83-46C1-8755-49287EFC7360@rcbowen.com> <4F9ABB13.7080707@cord.dk>
 <4F9B4F54.2080000@primary.net> <4F9EB17D.30909@cord.dk>
 <A132A198-5E1F-40DC-B540-0828AA4B9285@rcbowen.com>
Message-Id: <42794ED9-C23D-421C-899F-4D14BC78DE8C@rcbowen.com>

--Apple-Mail=_C685E979-066B-4362-84D5-BC29457A9FEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 30, 2012, at 11:46 AM, Rich Bowen wrote:

>=20
> Thanks for heading this up. I talked with Joe about this years ago, =
but then never followed up on it.
>=20
> My biggest question is whether it would require that we rewrite our =
XML, or if the existing XML is already in the right DTD?
>=20


Hmm. I think I misread. are we talking about the website, or the product =
documentation?

The former, I can see an advantage to, but the latter I might take some =
convincing. We ship those docs with the product, so maintaining them in =
the CMS might not be the best service to our users.
--
Rich Bowen
rbowen@rcbowen.com :: @rbowen
rbowen@apache.org


--Apple-Mail=_C685E979-066B-4362-84D5-BC29457A9FEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Apr 30, 2012, at 11:46 AM, Rich Bowen wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><br =
class=3D"Apple-interchange-newline">Thanks for heading this up. I talked =
with Joe about this years ago, but then never followed up on =
it.</div><div><br></div><div>My biggest question is whether it would =
require that we rewrite our XML, or if the existing XML is already in =
the right DTD?</div></span><br =
class=3D"Apple-interchange-newline"></blockquote></div><div><br></div><div=
><br></div>Hmm. I think I misread. are we talking about the website, or =
the product documentation?<div><br></div><div>The former, I can see an =
advantage to, but the latter I might take some convincing. We ship those =
docs with the product, so maintaining them in the CMS might not be the =
best service to our users.</div><div><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Inconsolata; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Inconsolata; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">--<br>Rich Bowen<br><a =
href=3D"mailto:rbowen@rcbowen.com">rbowen@rcbowen.com</a> :: =
@rbowen<br><a =
href=3D"mailto:rbowen@apache.org">rbowen@apache.org</a><br><br><br><br><br=
><br></div></span></span>
</div>
<br></div></body></html>=

--Apple-Mail=_C685E979-066B-4362-84D5-BC29457A9FEC--