stdcxx TLP site is live

[Martin Sebor <se...@roguewave.com>]

FYI: now that http://issues.apache.org/jira/browse/INFRA-1425
has been resolved I've copied the stdcxx incubator pages to
the TLP site for the time being: http://stdcxx.apache.org/

I'll continue working on removing incubation artifacts and, in
parallel, on prototyping a new site using Forrest. I'm hoping
to have something to show sometime next week. If anyone has
ideas/suggestions or would like to help with the prototype let
me know!

Martin

Re: stdcxx TLP site is live

[Martin Sebor <se...@roguewave.com>]

Gav.... wrote:
> Hi Martin,
> 
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com]
>> Sent: Saturday, 19 January 2008 4:15 AM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: stdcxx TLP site is live
>>
>> FYI: now that http://issues.apache.org/jira/browse/INFRA-1425
>> has been resolved I've copied the stdcxx incubator pages to
>> the TLP site for the time being: http://stdcxx.apache.org/
>>
>> I'll continue working on removing incubation artifacts and, in
>> parallel, on prototyping a new site using Forrest. I'm hoping
>> to have something to show sometime next week. If anyone has
>> ideas/suggestions or would like to help with the prototype let
>> me know!
> 
> Hopefully I can help.
> 
> A couple of questions.
> 
> I see you have some html site files in /site/ of svn. 
> Is this content synched with the main site?

Yes. A cron job updates it once an hour.

> If so, where in SVN are you planning on putting the forrest source
> files so that others can work on it?

I haven't given it much thought yet but if there is an established
convention for how to layout the site sources we'll want to follow
it, at least initially. IIRC, the incubator approach was to have
the sources in site-author/ and the generated site in site-publish/.

> 
> One way would be to have /site/forrest/src/*
> and have forrest svn publish site files to /site/html/*
> then a manual or cron sync of /site/html/* from /www/stdcxx.apache.org/

Makes sense. Is the reason for having the HTML under site/html rather
than directly under site/ where it is today to make it easy to sync
down just the generated site and not the sources in src/?)

> 
> So folks could checkout the source tree and those with svn ci access can use
> forrests svn deploy facility. Each committer would need to create an
> svn.deploy.settings file one level above the svn source so it does not get
> committed to svn.
> 
> You can look at http://svn.apache.org/repos/asf/xml/site/ and specifically
> http://svn.apache.org/repos/asf/xml/site/publish.xml as an example.

So the process for updating the site would go something like this:

   $ svn co https://svn.apache.org/repos/asf/stdcxx/site/ stdcxx-site/
   # ...edit pages in stdcxx-site/forrest/src/
   $ forrest -f stdcxx-site/forrest/publish.xml

where the forrest command would generate the site and commit it under
https://svn.apache.org/repos/asf/stdcxx/site/html?

If so, it sounds pretty straightforward (and very close to what I
expected).

> 
> How to proceed, I don't know how far you have got. Do you want me to convert
> the existing html files in /site/ to xdoc and send in a patch for the whole
> source tree (and create a better navigation structure), or something else ?

Wow, that would be a huge help!

Just as an FYI (as you might have already gathered), our site was
created by modifying another project's pages. It was quick and dirty
job as none of us had any understanding of Forrest (which was then
the norm in the Incubator) or the time to learn it and do it right.
I don't think anyone is attached to the current look and feel or has
a strong preference for any particular theme. To be honest, I don't
even know what themes are available. I'm mainly looking for something
simple to maintain where adding a new page doesn't involve changing
a whole bunch of cruft on all the other pages (menus, etc.)

> Within these files , I would use settings
> to enable dispatcher to make use of themes, although only the forrest
> standard pelt theme is really usable currently, you can base it to create
> your own site theme for a custom look and feel.
> 
> I think we should work on getting the configuration and publishing working
> first, then a theme can be worked on later.

Sounds good.

Martin

> 
> Gav...
> 
> 
> 
>> Martin
>>
>>
>> --
>> Internal Virus Database is out-of-date.
>> Checked by AVG Free Edition.
>> Version: 7.5.516 / Virus Database: 269.19.2 - Release Date: 1/12/2008
>> 12:00 AM
> 

RE: stdcxx TLP site is live

["Gav...." <br...@brightontown.com.au>]

Hi Martin,

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Saturday, 19 January 2008 4:15 AM
> To: stdcxx-dev@incubator.apache.org
> Subject: stdcxx TLP site is live
> 
> FYI: now that http://issues.apache.org/jira/browse/INFRA-1425
> has been resolved I've copied the stdcxx incubator pages to
> the TLP site for the time being: http://stdcxx.apache.org/
> 
> I'll continue working on removing incubation artifacts and, in
> parallel, on prototyping a new site using Forrest. I'm hoping
> to have something to show sometime next week. If anyone has
> ideas/suggestions or would like to help with the prototype let
> me know!

Hopefully I can help.

A couple of questions.

I see you have some html site files in /site/ of svn. 
Is this content synched with the main site?
If so, where in SVN are you planning on putting the forrest source
files so that others can work on it?

One way would be to have /site/forrest/src/*
and have forrest svn publish site files to /site/html/*
then a manual or cron sync of /site/html/* from /www/stdcxx.apache.org/

So folks could checkout the source tree and those with svn ci access can use
forrests svn deploy facility. Each committer would need to create an
svn.deploy.settings file one level above the svn source so it does not get
committed to svn.

You can look at http://svn.apache.org/repos/asf/xml/site/ and specifically
http://svn.apache.org/repos/asf/xml/site/publish.xml as an example.

How to proceed, I don't know how far you have got. Do you want me to convert
the existing html files in /site/ to xdoc and send in a patch for the whole
source tree (and create a better navigation structure), or something else ?
Within these files , I would use settings
to enable dispatcher to make use of themes, although only the forrest
standard pelt theme is really usable currently, you can base it to create
your own site theme for a custom look and feel.

I think we should work on getting the configuration and publishing working
first, then a theme can be worked on later.

Gav...



> 
> Martin
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.19.2 - Release Date: 1/12/2008
> 12:00 AM