[Swift-devel] A suggested web content strategy for Swift

[Mihael Hategan]

For what it's worth, I think that if folks don't want docbook (which I'd
more inclined to drop if there was any other reasonable equivalent
system that produces good html output), then html in SVN still mostly
meets our needs. The only problem I see down the road is that there will
be as many ways to write a table as there are editiing sessions. So we
would be shifting complexity from learning docbook to managing large
html. But that's not necessarily true.

Mihael

On Tue, 2011-03-01 at 10:38 -0600, Justin M Wozniak wrote:
> On Mon, 28 Feb 2011, Michael Wilde wrote:
> 
> > David wrote:
> >
> >>
> >> $ google docs get --title "Userguide 0.92"
> >>
> >>
> >> http://code.google.com/p/googlecl
> >
> > This would be a big plus for making Google sites/docs usable as our 
> > document editor, without loosing the ability to do proper svn 
> > management.
> 
> If this works, great, but I'm currently thinking that svn versioning for 
> old manuals is not as important as having a good up-to-date manual.  My 
> train of thought is that if we are going to edit XML actually should edit 
> HTML+CSS.  Content management is the next logical step from there.
> 
> I've taken a look at the ExM Google site and done some editing for the 
> JETS manual.  Pasting formatted content into the site does not work 
> cleanly (on Firefox/Windows), and the controls report the wrong formatting 
> (font sizes, etc.).  Versioning seems limited to going back in time for 
> the given document.  Even so, I think we could get the current manual in 
> there and looking decent in two or three days' work.  I'm curious what a 
> completed high-quality publically available site might look like, does 
> anyone know of one?  And if Google Docs is any indication, the service 
> will probably improve over time.
> 
> I strongly feel we should make a firm decision at the concall this week 
> and go from there.
> 
>  	Justin
>