You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Gav..." <br...@brightontown.com.au> on 2008/02/01 05:31:14 UTC
Re: [jira] Assigned: (STDCXX-686) redesign web site
Hi Martin,
Let me know what info you need from me next.
Once the source files I sent are in svn, then I'll be able to patch
properly against that.
I notice Jira replies are set to issues@, is there a Jira ticket filed to
change this to dev@.
Gav...
<quote who="Martin Sebor (JIRA)">
>
> [
> https://issues.apache.org/jira/browse/STDCXX-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Martin Sebor reassigned STDCXX-686:
> -----------------------------------
>
> Assignee: Martin Sebor
>
>> redesign web site
>> -----------------
>>
>> Key: STDCXX-686
>> URL: https://issues.apache.org/jira/browse/STDCXX-686
>> Project: C++ Standard Library
>> Issue Type: Improvement
>> Components: Web
>> Reporter: Martin Sebor
>> Assignee: Martin Sebor
>> Attachments: Copy of stdcxx.zip
>>
>> Original Estimate: 16h
>> Remaining Estimate: 16h
>>
>> The current web site is a bunch of static HTML pages with a lot of
>> difficult-to-maintain formatting cruft copied from pages of another
>> incubator project. We should look into generating the site from
>> easier-to-maintain "sources" using a tool like Apache Forrest or some
>> such.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Gav...
Re: [jira] Assigned: (STDCXX-686) redesign web site
Posted by Martin Sebor <se...@roguewave.com>.
Gav.... wrote:
>
> I notice Jira replies are set to issues@, is there a Jira ticket filed to
> change this to dev@.
>
FYI: As noted in http://issues.apache.org/jira/browse/INFRA-1512
this has been done.
Martin
--
View this message in context: http://www.nabble.com/Re%3A--jira--Assigned%3A-%28STDCXX-686%29-redesign-web-site-tp15220576p15316016.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
Ok, I think I'm finished now.
All pages converted to xdoc, all pages now reflect the current site
information including tables and links etc. I moved the mailing lists
section off the index page onto a page of its own.
Completed site currently published to
http://people.apache.org/~gmcdonald/stdcxx/index.html
for review.
So let me know what you think, any changes required or are you happy it can
now replace your existing site?
Once done, it should be easier for others to contribute to the documentation
of the site; we should probably add a section somewhere of instructions on
how people can do that, and what the steps are from editing the xdocs
through to getting it into svn through to the final stages of it being
published.
Gav...
> -----Original Message-----
> From: Gavin [mailto:gavin@16degrees.com.au]
> Sent: Sunday, 10 August 2008 11:45 PM
> To: dev@stdcxx.apache.org
> Subject: RE: Website Layout
>
> To add,
>
> I just done another round of updating, and I reckon all but the
> main index page and the new page is still to do which I should
> finish tomorrow.
>
> The Documentation Section, the Downloads Section, the Developers Section
> mission statement page, bugs page should all be upto date and links
> etc all enabled so are complete. Someone might want to check in case I
> made
> mistakes.
>
> Once the other two pages are done it should be good to go live, so please
> let me know if I missed anything.
>
> (the external docs of Class Reference and User Guide we can look to
> convert
> and amalgamate into the site afterwards imho and think this is what
> conclusion we came to earlier)
>
> Gav...
>
> > -----Original Message-----
> > From: Gavin [mailto:gavin@16degrees.com.au]
> > Sent: Sunday, 10 August 2008 8:20 PM
> > To: dev@stdcxx.apache.org
> > Subject: RE: Website Layout
> >
> >
> > It's been a while since March, moving to the other side of the continent
> > and
> > other stuff etc..
> >
> > Anyway, I did some more to the Forrest site, for me to work a bit more
> > freely I have put up a version at :-
> >
> > http://people.apache.org/~gmcdonald/stdcxx/index.html
> >
> > I realise I may be a bit behind as some content will have changed, but
> if
> > your happy with the layout etc, we can move on - that is of course you
> > haven't decided on another route yet.
> >
> > I'll continue on and get caught up on doc site content changes, then
> start
> > activating links etc. (bugs page more or less done)
> >
> > Gav...
> >
> > > -----Original Message-----
> > > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > > Sent: Tuesday, 11 March 2008 11:25 PM
> > > To: dev@stdcxx.apache.org
> > > Subject: RE: Website Layout
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Martin Sebor [mailto:sebor@roguewave.com]
> > > > Sent: Wednesday, 6 February 2008 7:04 AM
> > > > To: dev@stdcxx.apache.org
> > > > Subject: Re: Website Layout
> > > >
> > > > Gav.... wrote:
> > > > > Hi Eric/All,
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> > > > >> Sent: Saturday, 2 February 2008 2:17 AM
> > > > >> To: dev@stdcxx.apache.org
> > > > >> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > > > >>
> > > > >>
> > > > >> I like it. It follows the style of the current site so it's not
> > > > >> too disruptive.
> > > > >>
> > > > >> Couple minor suggestions:
> > > > >>
> > > > >> 1. Move the Documentation nav up to a tab next to the Download
> tab.
> > > > >
> > > > > Yes, that can be done, no problem, I'll do that in my next patch
> if
> > > > > no objections.
> > > >
> > > > Personally, I would probably try to tackle the migration of the
> > > > site as it is to Forrest first so we can publish it as our default,
> > > > and then work on improving the layout next. I don't know if this
> > > > approach makes sense or it's less effort to restructure it at the
> > > > same time.
> > > >
> > > > >
> > > > >> 2. Move all links at the top of the home page to the nav bar,
> > > > >> and subdivide them into groups (e.g. General [Objectives, About],
> > > > >> Project [Lists, Wiki, Status, News, Team], Technical (Bugs,
> Readme,
> > > > >> License, Platforms, References]
> > > > >
> > > > > Those links are auto generated from <sections> in the source and
> are
> > > > > internal links to the relative section on that page. Dividing them
> > > > > would mean creating new pages and moving content out of the home
> > page
> > > > > onto the new ones. This is no problem either, but its not my site,
> > so
> > > > > do you guys want to discuss the layout how you want it and I'll
> make
> > > > > the changes ?
> > > >
> > > > Sure. We don't have any design document or a rationale for the
> > > > current site but it makes sense to discuss it before Gav puts
> > > > in a whole lot of time into it. Btw., how difficult is it to
> > > > restructure the site in Forrest if we change our mind? :)
> > >
> > > It's fairly easy, so no problem.
> > >
> > > >
> > > > Here are some of my random thoughts on the subject...
> > > >
> > > > As far as tabs and menus go, I'd be inclined to follow the layout
> > > > used by other projects. From what I see on the Forrest site, for
> > > > instance, every tab is a menu with each menu item pointing to
> > > > a separate page (although the Versioned Docs and Plugins tabs
> > > > look like they're messed up). So if we expect each of Downloads
> > > > and Documentation to break down into a number of menu items with
> > > > a page for each, making them tabs sounds dandy.
> > > >
> > > > The one page I think is already way too long and that we should
> > > > probably break up into a number of smaller ones is index.html
> > > > (is there any kind of rule of thumb on how long the ideal page
> > > > should be?) We should probably split it up into an About page
> > > > (what is stdcxx), another one just for News, an another for
> > > > our "mission statement" (current Objectives). I can see us also
> > > > wanting to have a separate page or even a tab for Developers (as
> > > > on the Forrest page), and split that one into a page (or more)
> > > > for each of Committers, Contributors, and Users. And maybe also
> > > > PMC. Then there is Communication and Mailing Lists which could
> > > > be on the same page. I don't know how useful the References
> > > > section is. Seems like keeping this on the Wiki might work
> > > > better.
> > >
> > > I attached a diff to the issue making a start along the lines above.
> > > Once that's committed, I'll carry on and do some more.
> > >
> > > >
> > > > Btw., I should mention that during the restructuring of the site
> > > > I think it's important to preserve all existing links and ideally
> > > > also major anchors so we don't break links pointing to our site.
> > >
> > > If I do break any, I'll be sure to recheck and change them back where
> > > possible.
> > >
> > > Incidently, I'll try and tackle the converting of the Class Reference
> > > and User Guides last - there is a technique described at [1] , but
> lets
> > > get everything else sorted first and happy, then I'll look at them.
> > >
> > > [1] -
> > > http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
> > > source.html#cust
> > > om
> > >
> > >
> > >
> > > >
> > > > Martin
> > > >
> > > > >
> > > > >> 3. Where's the logo? :)
> > > > >
> > > > > I'll fix that.
> > >
> > > fixed.
> > >
> > > Gav...
> > >
> > >
> > > > >
> > > > > Gav...
> > > > >
> > > > >> Brad.
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > > > >>> Sent: Friday, February 01, 2008 1:25 AM
> > > > >>> To: dev@stdcxx.apache.org
> > > > >>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > > > >>>
> > > > >>> G'Day,
> > > > >>>
> > > > >>>> -----Original Message-----
> > > > >>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> > > > >>> Martin Sebor
> > > > >>>> Sent: Friday, 1 February 2008 3:00 PM
> > > > >>>> To: dev@stdcxx.apache.org
> > > > >>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> > > > >>>>
> > > > >>>> Gav... wrote:
> > > > >>>>> Hi Martin,
> > > > >>>>>
> > > > >>>>> Let me know what info you need from me next.
> > > > >>>>> Once the source files I sent are in svn, then I'll be
> > > > >>> able to patch
> > > > >>>>> properly against that.
> > > > >>>> It looks quite good, thanks! I published it in my home
> directory
> > > > >>>> to get some feedback from others:
> > > > >>>>
> > > > >>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> > > > >>> As initial information for others, the look of this site is the
> > > > >>> standard issue 'forrest pelt theme' and if so wish, can be
> changed
> > > > >>> to have more unique feel to it. This can wait I think until the
> > > > >>> site is live and populated with docs.
> > > > >>>
> > > > >>>> Btw., it looks like a couple of typos snuck into index.xml and
> > > > >>>> bugs.xml. I corrected them to get forrest to generate the
> static
> > > > >>>> site (otherwise it fails)...
> > > > >>> Damn, sorry, I tested using 'forrest run' which ensures the
> > > > >>> site is mostly
> > > > >>> fine and working - but does not scrutinise the xdocs for
> > > > >>> validity against
> > > > >>> the DTD. Only when a 'forrest site' or 'forrest
> > > > >>> validate-xdocs' is run do
> > > > >>> the files get checked against the DTD.
> > > > >>>
> > > > >>>> ... but I still get the error below at the
> > > > >>>> end. It looks like a link is bad or something.
> > > > >>>>
> > > > >>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > > > >>>> X [0] favicon.ico BROKEN:
> > No
> > > > >>>> pipeline matched request: favicon.ico
> > > > >>>> at <map:mount> -
> > > > >>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > > > >>>> ...
> > > > >>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site
> pages:
> > > 42
> > > > >>>> Java Result: 1
> > > > >>>>
> > > > >>>> Copying broken links file to site root.
> > > > >>>>
> > > > >>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> > > > >>>>
> > > > >>>> BUILD FAILED
> > > > >>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180:
> Error
> > > > >>>> building site.
> > > > >>>>
> > > > >>>> There appears to be a problem with your site build.
> > > > >>> Easy one and my bad again. Automatically a favicon.ico is
> > > > >>> associated with
> > > > >>> the site and is in fact copied there when doing a 'forrest
> > > > >>> seed-sample'.
> > > > >>> As you found out though this produces many un-needed sample
> > > > >>> files. So I
> > > > >>> created the initial layout with a 'forrest seed-basic' which
> gives
> > > you
> > > > >>> a site structure but no files and in this case no favicon
> either.
> > > > >>>
> > > > >>> So the cure is to stick a favicon.ico directly into the xdocs
> > > folder.
> > > > >>> The site will then build successfully.
> > > > >>>
> > > > >>>> The two typos are: a missing underscore in the section id
> > > > >>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > > > >>>> gives rather cryptic errors for them.
> > > > >>> The error messages were mainly to do with why they did not
> > > > >>> conform with the
> > > > >>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> > > > >>> and points out
> > > > >>> that only <li> can go inside.
> > > > >>>
> > > > >>> Most of the time, we will use Forrests v2.0 DTD -
> > > > >>>
> > > > >>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> > > > >>>
> > > > >>> (it is working towards being more xhtml2 compliant)
> > > > >>>
> > > > >>>> So sounds like the next step is to commit the prototype into
> svn
> > > > >>>> and set up a cron job to get it periodically published into
> some
> > > > >>>> sandbox (such as my home directory) so we can work on the
> tables
> > > > >>>> etc. Is that how you'd like to proceed?
> > > > >>> Yep, fine by me, at least I'll be able to be useful with patches
> > > then.
> > > > >>> Once your happy with stability, completeness and the
> > > > >>> forrestbot publishing
> > > > >>> is working well, then it can be moved when your happy.
> > > > >>>
> > > > >>>> I'm also curious if you have a suggestion for our
> documentation.
> > > > >>>> Would it make sense to try to convert it as well or might some
> > > > >>>> other solution be more appropriate?
> > > > >>> I have referred this to the Forrest dev list. It should not
> > > > >>> be a problem
> > > > >>> in principle, convert the .html files into xdoc xml and then
> > > > >>> back into .html
> > > > >>> integrated into the rest of the generated site. Hopefully the
> > > initial
> > > > >>> conversion to xdoc can be automated. Once in xdoc xml format
> > > > >>> then they can
> > > > >>> be placed appropriately, added to the site.xml and tabs.xml
> > > > >>> files and from
> > > > >>> then on be part of the site proper.
> > > > >>>
> > > > >>>>> I notice Jira replies are set to issues@, is there a Jira
> > > > >>> ticket filed
> > > > >>>> to
> > > > >>>>> change this to dev@.
> > > > >>>> Not yet. I was hoping to get to it this week but lately time
> has
> > > > >>>> a habit of getting away from me... You don't happen to know
> where
> > > > >>>> to change this, do you?
> > > > >>> I don't have the access to do it, I've asked on #infra and
> > > > >>> will let you know
> > > > >>> if someone does it. Otherwise you need to send a mail to
> > > > >>> apmail@ and file a
> > > > >>> Jira Issue on infra for it to be done .
> > > > >>>
> > > > >>> (http://apache.org/dev/reporting-issues.html#mail-config)
> > > > >>>
> > > > >>>
> > > > >>> Gav...
> > > > >>>
> > > > >>>> Martin
> > > > >>>>
> > > > >>>>> Gav...
> > > > >>>>>
> > > > >>>>> <quote who="Martin Sebor (JIRA)">
> > > > >>>>>> [
> > > > >>>>>> https://issues.apache.org/jira/browse/STDCXX-
> > > > >>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> > > tabpanel
> > > > >>>>>> ]
> > > > >>>>>>
> > > > >>>>>> Martin Sebor reassigned STDCXX-686:
> > > > >>>>>> -----------------------------------
> > > > >>>>>>
> > > > >>>>>> Assignee: Martin Sebor
> > > > >>>>>>
> > > > >>>>>>> redesign web site
> > > > >>>>>>> -----------------
> > > > >>>>>>>
> > > > >>>>>>> Key: STDCXX-686
> > > > >>>>>>> URL:
> > > > >>> https://issues.apache.org/jira/browse/STDCXX-686
> > > > >>>>>>> Project: C++ Standard Library
> > > > >>>>>>> Issue Type: Improvement
> > > > >>>>>>> Components: Web
> > > > >>>>>>> Reporter: Martin Sebor
> > > > >>>>>>> Assignee: Martin Sebor
> > > > >>>>>>> Attachments: Copy of stdcxx.zip
> > > > >>>>>>>
> > > > >>>>>>> Original Estimate: 16h
> > > > >>>>>>> Remaining Estimate: 16h
> > > > >>>>>>>
> > > > >>>>>>> The current web site is a bunch of static HTML pages
> > > > >>> with a lot of
> > > > >>>>>>> difficult-to-maintain formatting cruft copied from
> > > > >>> pages of another
> > > > >>>>>>> incubator project. We should look into generating the site
> > from
> > > > >>>>>>> easier-to-maintain "sources" using a tool like Apache
> > > > >>> Forrest or some
> > > > >>>>>>> such.
> > > > >>>>>> --
> > > > >>>>>> This message is automatically generated by JIRA.
> > > > >>>>>> -
> > > > >>>>>> You can reply to this email to add a comment to the issue
> > online.
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> --
> > > > >>>> 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
> > > > >>
> > > > >>
> > > > >> --
> > > > >> 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
> > > >
> > > >
> > > >
> > > > --
> > > > Internal Virus Database is out-of-date.
> > > > Checked by AVG Free Edition.
> > > > Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
> > > 1/12/2008
> > > > 2:04 PM
> > >
> > >
> > > --
> > > No virus found in this incoming message.
> > > Checked by AVG.
> > > Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
> > 3/10/2008
> > > 11:07 AM
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG.
> > Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008
> 12:00
> > AM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
To add,
I just done another round of updating, and I reckon all but the
main index page and the new page is still to do which I should
finish tomorrow.
The Documentation Section, the Downloads Section, the Developers Section
mission statement page, bugs page should all be upto date and links
etc all enabled so are complete. Someone might want to check in case I made
mistakes.
Once the other two pages are done it should be good to go live, so please
let me know if I missed anything.
(the external docs of Class Reference and User Guide we can look to convert
and amalgamate into the site afterwards imho and think this is what
conclusion we came to earlier)
Gav...
> -----Original Message-----
> From: Gavin [mailto:gavin@16degrees.com.au]
> Sent: Sunday, 10 August 2008 8:20 PM
> To: dev@stdcxx.apache.org
> Subject: RE: Website Layout
>
>
> It's been a while since March, moving to the other side of the continent
> and
> other stuff etc..
>
> Anyway, I did some more to the Forrest site, for me to work a bit more
> freely I have put up a version at :-
>
> http://people.apache.org/~gmcdonald/stdcxx/index.html
>
> I realise I may be a bit behind as some content will have changed, but if
> your happy with the layout etc, we can move on - that is of course you
> haven't decided on another route yet.
>
> I'll continue on and get caught up on doc site content changes, then start
> activating links etc. (bugs page more or less done)
>
> Gav...
>
> > -----Original Message-----
> > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > Sent: Tuesday, 11 March 2008 11:25 PM
> > To: dev@stdcxx.apache.org
> > Subject: RE: Website Layout
> >
> >
> >
> > > -----Original Message-----
> > > From: Martin Sebor [mailto:sebor@roguewave.com]
> > > Sent: Wednesday, 6 February 2008 7:04 AM
> > > To: dev@stdcxx.apache.org
> > > Subject: Re: Website Layout
> > >
> > > Gav.... wrote:
> > > > Hi Eric/All,
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> > > >> Sent: Saturday, 2 February 2008 2:17 AM
> > > >> To: dev@stdcxx.apache.org
> > > >> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > > >>
> > > >>
> > > >> I like it. It follows the style of the current site so it's not
> > > >> too disruptive.
> > > >>
> > > >> Couple minor suggestions:
> > > >>
> > > >> 1. Move the Documentation nav up to a tab next to the Download tab.
> > > >
> > > > Yes, that can be done, no problem, I'll do that in my next patch if
> > > > no objections.
> > >
> > > Personally, I would probably try to tackle the migration of the
> > > site as it is to Forrest first so we can publish it as our default,
> > > and then work on improving the layout next. I don't know if this
> > > approach makes sense or it's less effort to restructure it at the
> > > same time.
> > >
> > > >
> > > >> 2. Move all links at the top of the home page to the nav bar,
> > > >> and subdivide them into groups (e.g. General [Objectives, About],
> > > >> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> > > >> License, Platforms, References]
> > > >
> > > > Those links are auto generated from <sections> in the source and are
> > > > internal links to the relative section on that page. Dividing them
> > > > would mean creating new pages and moving content out of the home
> page
> > > > onto the new ones. This is no problem either, but its not my site,
> so
> > > > do you guys want to discuss the layout how you want it and I'll make
> > > > the changes ?
> > >
> > > Sure. We don't have any design document or a rationale for the
> > > current site but it makes sense to discuss it before Gav puts
> > > in a whole lot of time into it. Btw., how difficult is it to
> > > restructure the site in Forrest if we change our mind? :)
> >
> > It's fairly easy, so no problem.
> >
> > >
> > > Here are some of my random thoughts on the subject...
> > >
> > > As far as tabs and menus go, I'd be inclined to follow the layout
> > > used by other projects. From what I see on the Forrest site, for
> > > instance, every tab is a menu with each menu item pointing to
> > > a separate page (although the Versioned Docs and Plugins tabs
> > > look like they're messed up). So if we expect each of Downloads
> > > and Documentation to break down into a number of menu items with
> > > a page for each, making them tabs sounds dandy.
> > >
> > > The one page I think is already way too long and that we should
> > > probably break up into a number of smaller ones is index.html
> > > (is there any kind of rule of thumb on how long the ideal page
> > > should be?) We should probably split it up into an About page
> > > (what is stdcxx), another one just for News, an another for
> > > our "mission statement" (current Objectives). I can see us also
> > > wanting to have a separate page or even a tab for Developers (as
> > > on the Forrest page), and split that one into a page (or more)
> > > for each of Committers, Contributors, and Users. And maybe also
> > > PMC. Then there is Communication and Mailing Lists which could
> > > be on the same page. I don't know how useful the References
> > > section is. Seems like keeping this on the Wiki might work
> > > better.
> >
> > I attached a diff to the issue making a start along the lines above.
> > Once that's committed, I'll carry on and do some more.
> >
> > >
> > > Btw., I should mention that during the restructuring of the site
> > > I think it's important to preserve all existing links and ideally
> > > also major anchors so we don't break links pointing to our site.
> >
> > If I do break any, I'll be sure to recheck and change them back where
> > possible.
> >
> > Incidently, I'll try and tackle the converting of the Class Reference
> > and User Guides last - there is a technique described at [1] , but lets
> > get everything else sorted first and happy, then I'll look at them.
> >
> > [1] -
> > http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
> > source.html#cust
> > om
> >
> >
> >
> > >
> > > Martin
> > >
> > > >
> > > >> 3. Where's the logo? :)
> > > >
> > > > I'll fix that.
> >
> > fixed.
> >
> > Gav...
> >
> >
> > > >
> > > > Gav...
> > > >
> > > >> Brad.
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > > >>> Sent: Friday, February 01, 2008 1:25 AM
> > > >>> To: dev@stdcxx.apache.org
> > > >>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > > >>>
> > > >>> G'Day,
> > > >>>
> > > >>>> -----Original Message-----
> > > >>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> > > >>> Martin Sebor
> > > >>>> Sent: Friday, 1 February 2008 3:00 PM
> > > >>>> To: dev@stdcxx.apache.org
> > > >>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> > > >>>>
> > > >>>> Gav... wrote:
> > > >>>>> Hi Martin,
> > > >>>>>
> > > >>>>> Let me know what info you need from me next.
> > > >>>>> Once the source files I sent are in svn, then I'll be
> > > >>> able to patch
> > > >>>>> properly against that.
> > > >>>> It looks quite good, thanks! I published it in my home directory
> > > >>>> to get some feedback from others:
> > > >>>>
> > > >>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> > > >>> As initial information for others, the look of this site is the
> > > >>> standard issue 'forrest pelt theme' and if so wish, can be changed
> > > >>> to have more unique feel to it. This can wait I think until the
> > > >>> site is live and populated with docs.
> > > >>>
> > > >>>> Btw., it looks like a couple of typos snuck into index.xml and
> > > >>>> bugs.xml. I corrected them to get forrest to generate the static
> > > >>>> site (otherwise it fails)...
> > > >>> Damn, sorry, I tested using 'forrest run' which ensures the
> > > >>> site is mostly
> > > >>> fine and working - but does not scrutinise the xdocs for
> > > >>> validity against
> > > >>> the DTD. Only when a 'forrest site' or 'forrest
> > > >>> validate-xdocs' is run do
> > > >>> the files get checked against the DTD.
> > > >>>
> > > >>>> ... but I still get the error below at the
> > > >>>> end. It looks like a link is bad or something.
> > > >>>>
> > > >>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > > >>>> X [0] favicon.ico BROKEN:
> No
> > > >>>> pipeline matched request: favicon.ico
> > > >>>> at <map:mount> -
> > > >>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > > >>>> ...
> > > >>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
> > 42
> > > >>>> Java Result: 1
> > > >>>>
> > > >>>> Copying broken links file to site root.
> > > >>>>
> > > >>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> > > >>>>
> > > >>>> BUILD FAILED
> > > >>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> > > >>>> building site.
> > > >>>>
> > > >>>> There appears to be a problem with your site build.
> > > >>> Easy one and my bad again. Automatically a favicon.ico is
> > > >>> associated with
> > > >>> the site and is in fact copied there when doing a 'forrest
> > > >>> seed-sample'.
> > > >>> As you found out though this produces many un-needed sample
> > > >>> files. So I
> > > >>> created the initial layout with a 'forrest seed-basic' which gives
> > you
> > > >>> a site structure but no files and in this case no favicon either.
> > > >>>
> > > >>> So the cure is to stick a favicon.ico directly into the xdocs
> > folder.
> > > >>> The site will then build successfully.
> > > >>>
> > > >>>> The two typos are: a missing underscore in the section id
> > > >>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > > >>>> gives rather cryptic errors for them.
> > > >>> The error messages were mainly to do with why they did not
> > > >>> conform with the
> > > >>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> > > >>> and points out
> > > >>> that only <li> can go inside.
> > > >>>
> > > >>> Most of the time, we will use Forrests v2.0 DTD -
> > > >>>
> > > >>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> > > >>>
> > > >>> (it is working towards being more xhtml2 compliant)
> > > >>>
> > > >>>> So sounds like the next step is to commit the prototype into svn
> > > >>>> and set up a cron job to get it periodically published into some
> > > >>>> sandbox (such as my home directory) so we can work on the tables
> > > >>>> etc. Is that how you'd like to proceed?
> > > >>> Yep, fine by me, at least I'll be able to be useful with patches
> > then.
> > > >>> Once your happy with stability, completeness and the
> > > >>> forrestbot publishing
> > > >>> is working well, then it can be moved when your happy.
> > > >>>
> > > >>>> I'm also curious if you have a suggestion for our documentation.
> > > >>>> Would it make sense to try to convert it as well or might some
> > > >>>> other solution be more appropriate?
> > > >>> I have referred this to the Forrest dev list. It should not
> > > >>> be a problem
> > > >>> in principle, convert the .html files into xdoc xml and then
> > > >>> back into .html
> > > >>> integrated into the rest of the generated site. Hopefully the
> > initial
> > > >>> conversion to xdoc can be automated. Once in xdoc xml format
> > > >>> then they can
> > > >>> be placed appropriately, added to the site.xml and tabs.xml
> > > >>> files and from
> > > >>> then on be part of the site proper.
> > > >>>
> > > >>>>> I notice Jira replies are set to issues@, is there a Jira
> > > >>> ticket filed
> > > >>>> to
> > > >>>>> change this to dev@.
> > > >>>> Not yet. I was hoping to get to it this week but lately time has
> > > >>>> a habit of getting away from me... You don't happen to know where
> > > >>>> to change this, do you?
> > > >>> I don't have the access to do it, I've asked on #infra and
> > > >>> will let you know
> > > >>> if someone does it. Otherwise you need to send a mail to
> > > >>> apmail@ and file a
> > > >>> Jira Issue on infra for it to be done .
> > > >>>
> > > >>> (http://apache.org/dev/reporting-issues.html#mail-config)
> > > >>>
> > > >>>
> > > >>> Gav...
> > > >>>
> > > >>>> Martin
> > > >>>>
> > > >>>>> Gav...
> > > >>>>>
> > > >>>>> <quote who="Martin Sebor (JIRA)">
> > > >>>>>> [
> > > >>>>>> https://issues.apache.org/jira/browse/STDCXX-
> > > >>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> > tabpanel
> > > >>>>>> ]
> > > >>>>>>
> > > >>>>>> Martin Sebor reassigned STDCXX-686:
> > > >>>>>> -----------------------------------
> > > >>>>>>
> > > >>>>>> Assignee: Martin Sebor
> > > >>>>>>
> > > >>>>>>> redesign web site
> > > >>>>>>> -----------------
> > > >>>>>>>
> > > >>>>>>> Key: STDCXX-686
> > > >>>>>>> URL:
> > > >>> https://issues.apache.org/jira/browse/STDCXX-686
> > > >>>>>>> Project: C++ Standard Library
> > > >>>>>>> Issue Type: Improvement
> > > >>>>>>> Components: Web
> > > >>>>>>> Reporter: Martin Sebor
> > > >>>>>>> Assignee: Martin Sebor
> > > >>>>>>> Attachments: Copy of stdcxx.zip
> > > >>>>>>>
> > > >>>>>>> Original Estimate: 16h
> > > >>>>>>> Remaining Estimate: 16h
> > > >>>>>>>
> > > >>>>>>> The current web site is a bunch of static HTML pages
> > > >>> with a lot of
> > > >>>>>>> difficult-to-maintain formatting cruft copied from
> > > >>> pages of another
> > > >>>>>>> incubator project. We should look into generating the site
> from
> > > >>>>>>> easier-to-maintain "sources" using a tool like Apache
> > > >>> Forrest or some
> > > >>>>>>> such.
> > > >>>>>> --
> > > >>>>>> This message is automatically generated by JIRA.
> > > >>>>>> -
> > > >>>>>> You can reply to this email to add a comment to the issue
> online.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>> 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
> > > >>
> > > >>
> > > >> --
> > > >> 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
> > >
> > >
> > >
> > > --
> > > Internal Virus Database is out-of-date.
> > > Checked by AVG Free Edition.
> > > Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
> > 1/12/2008
> > > 2:04 PM
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
> 3/10/2008
> > 11:07 AM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
Hi Guys, back again,
It's been a while since March, moving to the other side of the continent and
other stuff etc..
Anyway, I did some more to the Forrest site, for me to work a bit more
freely I have put up a version at :-
http://people.apache.org/~gmcdonald/stdcxx/index.html
I realise I may be a bit behind as some content will have changed, but if
your happy with the layout etc, we can move on - that is of course you
haven't decided on another route yet.
I'll continue on and get caught up on doc site content changes, then start
activating links etc. (bugs page more or less done)
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Tuesday, 11 March 2008 11:25 PM
> To: dev@stdcxx.apache.org
> Subject: RE: Website Layout
>
>
>
> > -----Original Message-----
> > From: Martin Sebor [mailto:sebor@roguewave.com]
> > Sent: Wednesday, 6 February 2008 7:04 AM
> > To: dev@stdcxx.apache.org
> > Subject: Re: Website Layout
> >
> > Gav.... wrote:
> > > Hi Eric/All,
> > >
> > >
> > >> -----Original Message-----
> > >> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> > >> Sent: Saturday, 2 February 2008 2:17 AM
> > >> To: dev@stdcxx.apache.org
> > >> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > >>
> > >>
> > >> I like it. It follows the style of the current site so it's not
> > >> too disruptive.
> > >>
> > >> Couple minor suggestions:
> > >>
> > >> 1. Move the Documentation nav up to a tab next to the Download tab.
> > >
> > > Yes, that can be done, no problem, I'll do that in my next patch if
> > > no objections.
> >
> > Personally, I would probably try to tackle the migration of the
> > site as it is to Forrest first so we can publish it as our default,
> > and then work on improving the layout next. I don't know if this
> > approach makes sense or it's less effort to restructure it at the
> > same time.
> >
> > >
> > >> 2. Move all links at the top of the home page to the nav bar,
> > >> and subdivide them into groups (e.g. General [Objectives, About],
> > >> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> > >> License, Platforms, References]
> > >
> > > Those links are auto generated from <sections> in the source and are
> > > internal links to the relative section on that page. Dividing them
> > > would mean creating new pages and moving content out of the home page
> > > onto the new ones. This is no problem either, but its not my site, so
> > > do you guys want to discuss the layout how you want it and I'll make
> > > the changes ?
> >
> > Sure. We don't have any design document or a rationale for the
> > current site but it makes sense to discuss it before Gav puts
> > in a whole lot of time into it. Btw., how difficult is it to
> > restructure the site in Forrest if we change our mind? :)
>
> It's fairly easy, so no problem.
>
> >
> > Here are some of my random thoughts on the subject...
> >
> > As far as tabs and menus go, I'd be inclined to follow the layout
> > used by other projects. From what I see on the Forrest site, for
> > instance, every tab is a menu with each menu item pointing to
> > a separate page (although the Versioned Docs and Plugins tabs
> > look like they're messed up). So if we expect each of Downloads
> > and Documentation to break down into a number of menu items with
> > a page for each, making them tabs sounds dandy.
> >
> > The one page I think is already way too long and that we should
> > probably break up into a number of smaller ones is index.html
> > (is there any kind of rule of thumb on how long the ideal page
> > should be?) We should probably split it up into an About page
> > (what is stdcxx), another one just for News, an another for
> > our "mission statement" (current Objectives). I can see us also
> > wanting to have a separate page or even a tab for Developers (as
> > on the Forrest page), and split that one into a page (or more)
> > for each of Committers, Contributors, and Users. And maybe also
> > PMC. Then there is Communication and Mailing Lists which could
> > be on the same page. I don't know how useful the References
> > section is. Seems like keeping this on the Wiki might work
> > better.
>
> I attached a diff to the issue making a start along the lines above.
> Once that's committed, I'll carry on and do some more.
>
> >
> > Btw., I should mention that during the restructuring of the site
> > I think it's important to preserve all existing links and ideally
> > also major anchors so we don't break links pointing to our site.
>
> If I do break any, I'll be sure to recheck and change them back where
> possible.
>
> Incidently, I'll try and tackle the converting of the Class Reference
> and User Guides last - there is a technique described at [1] , but lets
> get everything else sorted first and happy, then I'll look at them.
>
> [1] -
> http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
> source.html#cust
> om
>
>
>
> >
> > Martin
> >
> > >
> > >> 3. Where's the logo? :)
> > >
> > > I'll fix that.
>
> fixed.
>
> Gav...
>
>
> > >
> > > Gav...
> > >
> > >> Brad.
> > >>
> > >>> -----Original Message-----
> > >>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > >>> Sent: Friday, February 01, 2008 1:25 AM
> > >>> To: dev@stdcxx.apache.org
> > >>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > >>>
> > >>> G'Day,
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> > >>> Martin Sebor
> > >>>> Sent: Friday, 1 February 2008 3:00 PM
> > >>>> To: dev@stdcxx.apache.org
> > >>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> > >>>>
> > >>>> Gav... wrote:
> > >>>>> Hi Martin,
> > >>>>>
> > >>>>> Let me know what info you need from me next.
> > >>>>> Once the source files I sent are in svn, then I'll be
> > >>> able to patch
> > >>>>> properly against that.
> > >>>> It looks quite good, thanks! I published it in my home directory
> > >>>> to get some feedback from others:
> > >>>>
> > >>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> > >>> As initial information for others, the look of this site is the
> > >>> standard issue 'forrest pelt theme' and if so wish, can be changed
> > >>> to have more unique feel to it. This can wait I think until the
> > >>> site is live and populated with docs.
> > >>>
> > >>>> Btw., it looks like a couple of typos snuck into index.xml and
> > >>>> bugs.xml. I corrected them to get forrest to generate the static
> > >>>> site (otherwise it fails)...
> > >>> Damn, sorry, I tested using 'forrest run' which ensures the
> > >>> site is mostly
> > >>> fine and working - but does not scrutinise the xdocs for
> > >>> validity against
> > >>> the DTD. Only when a 'forrest site' or 'forrest
> > >>> validate-xdocs' is run do
> > >>> the files get checked against the DTD.
> > >>>
> > >>>> ... but I still get the error below at the
> > >>>> end. It looks like a link is bad or something.
> > >>>>
> > >>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > >>>> X [0] favicon.ico BROKEN: No
> > >>>> pipeline matched request: favicon.ico
> > >>>> at <map:mount> -
> > >>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > >>>> ...
> > >>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
> 42
> > >>>> Java Result: 1
> > >>>>
> > >>>> Copying broken links file to site root.
> > >>>>
> > >>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> > >>>>
> > >>>> BUILD FAILED
> > >>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> > >>>> building site.
> > >>>>
> > >>>> There appears to be a problem with your site build.
> > >>> Easy one and my bad again. Automatically a favicon.ico is
> > >>> associated with
> > >>> the site and is in fact copied there when doing a 'forrest
> > >>> seed-sample'.
> > >>> As you found out though this produces many un-needed sample
> > >>> files. So I
> > >>> created the initial layout with a 'forrest seed-basic' which gives
> you
> > >>> a site structure but no files and in this case no favicon either.
> > >>>
> > >>> So the cure is to stick a favicon.ico directly into the xdocs
> folder.
> > >>> The site will then build successfully.
> > >>>
> > >>>> The two typos are: a missing underscore in the section id
> > >>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > >>>> gives rather cryptic errors for them.
> > >>> The error messages were mainly to do with why they did not
> > >>> conform with the
> > >>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> > >>> and points out
> > >>> that only <li> can go inside.
> > >>>
> > >>> Most of the time, we will use Forrests v2.0 DTD -
> > >>>
> > >>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> > >>>
> > >>> (it is working towards being more xhtml2 compliant)
> > >>>
> > >>>> So sounds like the next step is to commit the prototype into svn
> > >>>> and set up a cron job to get it periodically published into some
> > >>>> sandbox (such as my home directory) so we can work on the tables
> > >>>> etc. Is that how you'd like to proceed?
> > >>> Yep, fine by me, at least I'll be able to be useful with patches
> then.
> > >>> Once your happy with stability, completeness and the
> > >>> forrestbot publishing
> > >>> is working well, then it can be moved when your happy.
> > >>>
> > >>>> I'm also curious if you have a suggestion for our documentation.
> > >>>> Would it make sense to try to convert it as well or might some
> > >>>> other solution be more appropriate?
> > >>> I have referred this to the Forrest dev list. It should not
> > >>> be a problem
> > >>> in principle, convert the .html files into xdoc xml and then
> > >>> back into .html
> > >>> integrated into the rest of the generated site. Hopefully the
> initial
> > >>> conversion to xdoc can be automated. Once in xdoc xml format
> > >>> then they can
> > >>> be placed appropriately, added to the site.xml and tabs.xml
> > >>> files and from
> > >>> then on be part of the site proper.
> > >>>
> > >>>>> I notice Jira replies are set to issues@, is there a Jira
> > >>> ticket filed
> > >>>> to
> > >>>>> change this to dev@.
> > >>>> Not yet. I was hoping to get to it this week but lately time has
> > >>>> a habit of getting away from me... You don't happen to know where
> > >>>> to change this, do you?
> > >>> I don't have the access to do it, I've asked on #infra and
> > >>> will let you know
> > >>> if someone does it. Otherwise you need to send a mail to
> > >>> apmail@ and file a
> > >>> Jira Issue on infra for it to be done .
> > >>>
> > >>> (http://apache.org/dev/reporting-issues.html#mail-config)
> > >>>
> > >>>
> > >>> Gav...
> > >>>
> > >>>> Martin
> > >>>>
> > >>>>> Gav...
> > >>>>>
> > >>>>> <quote who="Martin Sebor (JIRA)">
> > >>>>>> [
> > >>>>>> https://issues.apache.org/jira/browse/STDCXX-
> > >>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> tabpanel
> > >>>>>> ]
> > >>>>>>
> > >>>>>> Martin Sebor reassigned STDCXX-686:
> > >>>>>> -----------------------------------
> > >>>>>>
> > >>>>>> Assignee: Martin Sebor
> > >>>>>>
> > >>>>>>> redesign web site
> > >>>>>>> -----------------
> > >>>>>>>
> > >>>>>>> Key: STDCXX-686
> > >>>>>>> URL:
> > >>> https://issues.apache.org/jira/browse/STDCXX-686
> > >>>>>>> Project: C++ Standard Library
> > >>>>>>> Issue Type: Improvement
> > >>>>>>> Components: Web
> > >>>>>>> Reporter: Martin Sebor
> > >>>>>>> Assignee: Martin Sebor
> > >>>>>>> Attachments: Copy of stdcxx.zip
> > >>>>>>>
> > >>>>>>> Original Estimate: 16h
> > >>>>>>> Remaining Estimate: 16h
> > >>>>>>>
> > >>>>>>> The current web site is a bunch of static HTML pages
> > >>> with a lot of
> > >>>>>>> difficult-to-maintain formatting cruft copied from
> > >>> pages of another
> > >>>>>>> incubator project. We should look into generating the site from
> > >>>>>>> easier-to-maintain "sources" using a tool like Apache
> > >>> Forrest or some
> > >>>>>>> such.
> > >>>>>> --
> > >>>>>> This message is automatically generated by JIRA.
> > >>>>>> -
> > >>>>>> You can reply to this email to add a comment to the issue online.
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> 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
> > >>
> > >>
> > >> --
> > >> 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
> >
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
> 1/12/2008
> > 2:04 PM
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date: 3/10/2008
> 11:07 AM
Re: Website Layout
Posted by Martin Sebor <ms...@gmail.com>.
Gavin wrote:
>
>> -----Original Message-----
>> From: Gavin [mailto:gavin@16degrees.com.au]
>> Sent: Friday, 15 August 2008 3:34 PM
>> To: dev@stdcxx.apache.org
>> Subject: RE: Website Layout
>>
>> Hi Martin,
>>
>>> -----Original Message-----
>>> From: Martin Sebor [mailto:msebor@gmail.com]
>>> Sent: Friday, 15 August 2008 11:32 AM
>>> To: dev@stdcxx.apache.org
>>> Subject: Re: Website Layout
>>>
>>> Alright Gavin, thanks for your patience in discussing this.
>> No problem,
>>
>>> If you can point me at your sources I'll generate the HTML
>>> and commit the whole lot under
>>> http://svn.apache.org/repos/asf/stdcxx/site/forrest
>>> as you suggest, and work on replacing the existing site
>>> with the generated docs.
>> I was working on it from your trunk, so I exported it and zipped it up as
>> exported.zip in my home dir on people (gmcdonald).
>
> Would it work if I zipped up my versioned files? Could you then overwrite
> your versioned /forrest/ and svn up, never tried it before so don't know,
> just trying to make it easier.
I'm not sure I understand correctly what exactly you mean but
why don't we give it a try? If it doesn't work I'm sure we'll
find out ;-)
>
>> Just to recap, you should put those sources in /site/forrest/ and the
>> generated html should end up /site/deploy/ or whatever names you want to
>> call them.
>
> Well, as an update on the infra thread, it has revealed some sites deploy
> directly to their /www/$tlp.a.o/ directly. Joes has agreed to relax policy
> and allow this to continue. It also looks like (if volunteers emerge I
> guess) that a zone may eventually happen for projects to build sites on,
> before deploying to /www/$tlp.a.o/
I saw Joe's response and was going to follow up -- you beat me
to it :) I've never worked on these zones so I have no idea how
easy it will be to generate the docs there and then move them
over to people.a.o.
>
> So, as it stands then, currently you still have to build offline, but you
> can then deploy your generated docs directly if you wish. It is worth
> reading the latest posts in the thread, especially Roys comments on why it
> is still good to deploy to svn and keep your published site files versioned.
In case someone hijacks the site.
FWIW, my biggest concern is having to manually generate the docs.
I tend to work on different servers with no Forrest or even Java
installed. Having to remember to go to a machine with the software
installed, set it all up (it's never set up by default), then run
the tool, and only then check the output in is a hassle I'd like
to avoid. Ideally, I was hoping to take this step out of the
equation for everyone by automating it on the ASF side. If that
can't be done for administrative or technical reasons I might
set it up on one of our servers instead, and either commit the
generated HTML automatically, or scp them to their destination
on people.a.o. I've seen objections to the former approach on
infra. The latter seems like a cleaner approach (no need to
check in generated files), but it's vulnerable to the problem
Roy points out. It doesn't seem like a solution that will make
everyone happy exists. No matter which we choose, it will be
a compromise...
Martin
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Gavin [mailto:gavin@16degrees.com.au]
> Sent: Friday, 15 August 2008 3:34 PM
> To: dev@stdcxx.apache.org
> Subject: RE: Website Layout
>
> Hi Martin,
>
> > -----Original Message-----
> > From: Martin Sebor [mailto:msebor@gmail.com]
> > Sent: Friday, 15 August 2008 11:32 AM
> > To: dev@stdcxx.apache.org
> > Subject: Re: Website Layout
> >
> > Alright Gavin, thanks for your patience in discussing this.
>
> No problem,
>
> > If you can point me at your sources I'll generate the HTML
> > and commit the whole lot under
> > http://svn.apache.org/repos/asf/stdcxx/site/forrest
> > as you suggest, and work on replacing the existing site
> > with the generated docs.
>
> I was working on it from your trunk, so I exported it and zipped it up as
> exported.zip in my home dir on people (gmcdonald).
Would it work if I zipped up my versioned files? Could you then overwrite
your versioned /forrest/ and svn up, never tried it before so don't know,
just trying to make it easier.
>
> Just to recap, you should put those sources in /site/forrest/ and the
> generated html should end up /site/deploy/ or whatever names you want to
> call them.
Well, as an update on the infra thread, it has revealed some sites deploy
directly to their /www/$tlp.a.o/ directly. Joes has agreed to relax policy
and allow this to continue. It also looks like (if volunteers emerge I
guess) that a zone may eventually happen for projects to build sites on,
before deploying to /www/$tlp.a.o/
So, as it stands then, currently you still have to build offline, but you
can then deploy your generated docs directly if you wish. It is worth
reading the latest posts in the thread, especially Roys comments on why it
is still good to deploy to svn and keep your published site files versioned.
Gav...
>
> Let me know how you get on.
>
> Gav...
>
> >
> > Martin
> >
> > Gavin wrote:
> > >
> > >> -----Original Message-----
> > >> From: Martin Sebor [mailto:msebor@gmail.com]
> > >> Sent: Thursday, 14 August 2008 6:32 AM
> > >> To: dev@stdcxx.apache.org
> > >> Subject: Re: Website Layout
> > >>
> > >> Gavin wrote:
> > >>>> -----Original Message-----
> > >>>> From: Martin Sebor [mailto:msebor@gmail.com]
> > >>>> Sent: Wednesday, 13 August 2008 4:49 AM
> > >>>> To: dev@stdcxx.apache.org
> > >>>> Subject: Re: Website Layout
> > >>>>
> > >>>> Gavin wrote:
> > >>> <snip>
> > >>>
> > >>>>> So whilst we are at this level of even-ness (?) it is a good time
> to
> > >>>> swap it
> > >>>>> over and make it live. However, over the next day or two, I will
> add
> > >>>>> developer docs on how to go about updating the site,
> altering/adding
> > >>>> pages
> > >>>>> etc..
> > >>>>>
> > >>>>> Let me know what you think.
> > >>>> Sounds like a plan.
> > >>>>
> > >>>> I assume we'll commit just the Forrest sources into Subversion
> > >>>> and generate the site out of them on people.a.o using a cron
> > >>>> job, correct?
> > >>> Well, I'm sure various projects do things in slightly different
> ways.
> > >>> However I would not recommend doing any building on people.a.o , and
> > is
> > >> not
> > >>> necessary anyway.
> > >>>
> > >>> This is how Forrest, xmlgraphics and a few others do it :-
> > >>>
> > >>> 1. Alter xdocs locally to your needs.
> > >>> 2. svn ci to get sources upto date in svn
> > >>> 3. locally run 'forrest -f publish.xml build'
> > >>> 4. locally run 'forrest -f publish.xml deploy'
> > >>> 5. /x1/www/stdcxx.apache.org svn up
> > >>>
> > >>> That's the general gist, more fully,
> > >>>
> > >>> Forrest stores its site source files in
> > >>>
> > >>> http://svn.apache.org/repos/asf/forrest/trunk/site-author/
> > >>>
> > >>> and the generated site docs go to
> > >>>
> > >>> http://svn.apache.org/repos/asf/forrest/site/
> > >>>
> > >>> A cronjob on p.a.o then runs svn up hourly to
> > >>> /x1/www/forrest.apache.org
> > >>>
> > >>> The hourly sync to eos/aurora then picks that up and your updated
> docs
> > >> are
> > >>> then live.
> > >>>
> > >>> Again, with xmlgraphics, site source files stored in
> > >>>
> > >>> http://svn.apache.org/repos/asf/xmlgraphics/site/
> > >>>
> > >>> and the generated site docs go to
> > >>>
> > >>> http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
> > >>>
> > >>> /x1/www/xmgraphics.apache.org is svn of that deploy location, no
> idea
> > >> how
> > >>> often they run svn up or if it is done manually. Also no idea if
> they
> > >> use
> > >>> forrestbot (steps 2 and 3) or whether they svn ci the generated
> site,
> > >> you'd
> > >>> have to talk to Jeremias about that.
> > >>>
> > >>> So , possibly 2 slightly different methods.
> > >>>
> > >>> I'm happy to help show the way to Forrests' method. And of course I
> > will
> > >>> continue to be on this list for any help required afterwards. One
> > thing
> > >> to
> > >>> note for others listening, it is necessary to have Apache Forrest
> > >> installed
> > >>> on your local machine in order to alter the xdocs, test locally,
> build
> > >> and
> > >>> then deploy.
> > >>>
> > >>> There is a renewed talk on infra lists about having a shared zone or
> > >>> something else where projects can build sites using
> > Forrest/Maven/Anakia
> > >>> that would be installed on the zone, the idea I guess is that
> > generated
> > >>> source files would live there and be copied over to various projects
> > >>> /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
> > >>> following for now to see how it pans out, or how long it will take.
> > Just
> > >>> thought I'd mention it, in the meantime we need to do one of the
> > above.
> > >> I assume you're referring to the thread on Automating parts of
> > >> the web site publishing process. I've seen the discussion but
> > >> haven't had time to follow it closely enough to benefit from
> > >> it.
> > >>
> > >>> So, here's how I see it for stdcxx :-
> > >>>
> > >>> Have forrest and site source files where they are currently in
> > >>>
> > >>> http://svn.apache.org/repos/asf/stdcxx/site/forrest/
> > >>>
> > >>> Have the generated site files in
> > >>>
> > >>> http://svn.apache.org/repos/asf/stdcxx/site/deploy/
> > >>>
> > >>> and 'svn remove' the current content from /site/
> > >>>
> > >>> The above structure will remove the nasty side effect you currently
> > have
> > >> of
> > >>> forrest source files viewable on the web
> > >> (http://stdcxx.apache.org/forrest/)
> > >>> doesn't look good.
> > >>>
> > >>> Then create a cronjob to svn up hourly (or whatever delay you
> prefer)
> > to
> > >>> update your /x1/www/stdcxx.apache.org with the updated site files.
> > >>>
> > >>> That's about it for now, what do you think?
> > >> Thanks for the detailed info! The depot structure and the cron
> > >> job approach sound reasonable (we already have a cron job running
> > >> to periodically update the existing site). My only concern is the
> > >> requirement to run Forrest locally on each committer's machine.
> > >
> > > I understand that.
> > >
> > >> Do you happen to know the other projects' rationale for checking
> > >> the generated sites into Subversion instead of generating their
> > >> sites directly on people.a.o?
> > >
> > > Yes, Infra Policy.
> > >
> > > It seems that since the site is
> > >> generated from sources that already are in Subversion there
> > >> should be no reason to version the generated HTML as well, and
> > >> being able to update the site without having to have Forrest
> > >> install seems like a significant advantage. But given that most
> > >> other projects do it differently I suspect I must be missing
> > >> some significant disadvantages of the "simpler" approach. Is
> > >> there concern with the overhead o projects running Forrest too
> > >> often?
> > >
> > > Imagine 200+ projects all building their sites with
> > > forrest/maven/anakia/whatever on p.a.o , all no doubt installing their
> > own
> > > copy too. The overhead would be massive if it were allowed.
> > >
> > > Also, generated docs I guess are still files produced by ASF projects,
> > they
> > > would also differ in their content and structure to the source files.
> As
> > > such having the history would be a benefit.
> > >
> > > I'm just guessing at that last bit, what I do know is that infra
> > currently
> > > insists that
> > > a) no projects to run builds on infra,
> > > b) generated site docs are to be in svn.
> > >
> > > So, unless you can change that, and perhaps until that infra thread
> > produces
> > > something - join in as a usecase if you think it worthwile, then I'd
> go
> > with
> > > my suggestion.
> > >
> > > Those that don't contribute to the website docs wont need forrest.
> > >
> > > fwiw if you used Maven or any other build tool you'd be in the same
> > > situation.
> > >
> > >
> > >> FWIW, the way I originally set up this project was to generate
> > >> the Forrest site in:
> > >> http://people.apache.org/~sebor/stdcxx/forrest-site/
> > >>
> > >> The cron job that does the updating is in:
> > >> /people.apache.org:/home/sebor/bin/update-site.sh
> > >>
> > >
> > > Well, I'm not saying remove it , but ...
> > >
> > > At the end of the day, I've made my recommendation, its up to you guys
> > how
> > > you want to proceed.
> > >
> > > I have Forrest installed of course so there is no problem with me
> > applying
> > > doc patches and generating the site, if one or two others are happy to
> > have
> > > Forrest on their systems locally, then we don't really have a problem.
> > >
> > > Gav...
> > >
> > >> Martin
> > >>
> > >>> Gav...
> > >>>
> > >>>
> > >>>
> > >>
> > >> --
> > >> Internal Virus Database is out-of-date.
> > >> Checked by AVG.
> > >> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008
> > 12:00
> > >> AM
> > >
> > >
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG.
> > Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008
> 12:00
> > AM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
Hi Martin,
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com]
> Sent: Friday, 15 August 2008 11:32 AM
> To: dev@stdcxx.apache.org
> Subject: Re: Website Layout
>
> Alright Gavin, thanks for your patience in discussing this.
No problem,
> If you can point me at your sources I'll generate the HTML
> and commit the whole lot under
> http://svn.apache.org/repos/asf/stdcxx/site/forrest
> as you suggest, and work on replacing the existing site
> with the generated docs.
I was working on it from your trunk, so I exported it and zipped it up as
exported.zip in my home dir on people (gmcdonald).
Just to recap, you should put those sources in /site/forrest/ and the
generated html should end up /site/deploy/ or whatever names you want to
call them.
Let me know how you get on.
Gav...
>
> Martin
>
> Gavin wrote:
> >
> >> -----Original Message-----
> >> From: Martin Sebor [mailto:msebor@gmail.com]
> >> Sent: Thursday, 14 August 2008 6:32 AM
> >> To: dev@stdcxx.apache.org
> >> Subject: Re: Website Layout
> >>
> >> Gavin wrote:
> >>>> -----Original Message-----
> >>>> From: Martin Sebor [mailto:msebor@gmail.com]
> >>>> Sent: Wednesday, 13 August 2008 4:49 AM
> >>>> To: dev@stdcxx.apache.org
> >>>> Subject: Re: Website Layout
> >>>>
> >>>> Gavin wrote:
> >>> <snip>
> >>>
> >>>>> So whilst we are at this level of even-ness (?) it is a good time to
> >>>> swap it
> >>>>> over and make it live. However, over the next day or two, I will add
> >>>>> developer docs on how to go about updating the site, altering/adding
> >>>> pages
> >>>>> etc..
> >>>>>
> >>>>> Let me know what you think.
> >>>> Sounds like a plan.
> >>>>
> >>>> I assume we'll commit just the Forrest sources into Subversion
> >>>> and generate the site out of them on people.a.o using a cron
> >>>> job, correct?
> >>> Well, I'm sure various projects do things in slightly different ways.
> >>> However I would not recommend doing any building on people.a.o , and
> is
> >> not
> >>> necessary anyway.
> >>>
> >>> This is how Forrest, xmlgraphics and a few others do it :-
> >>>
> >>> 1. Alter xdocs locally to your needs.
> >>> 2. svn ci to get sources upto date in svn
> >>> 3. locally run 'forrest -f publish.xml build'
> >>> 4. locally run 'forrest -f publish.xml deploy'
> >>> 5. /x1/www/stdcxx.apache.org svn up
> >>>
> >>> That's the general gist, more fully,
> >>>
> >>> Forrest stores its site source files in
> >>>
> >>> http://svn.apache.org/repos/asf/forrest/trunk/site-author/
> >>>
> >>> and the generated site docs go to
> >>>
> >>> http://svn.apache.org/repos/asf/forrest/site/
> >>>
> >>> A cronjob on p.a.o then runs svn up hourly to
> >>> /x1/www/forrest.apache.org
> >>>
> >>> The hourly sync to eos/aurora then picks that up and your updated docs
> >> are
> >>> then live.
> >>>
> >>> Again, with xmlgraphics, site source files stored in
> >>>
> >>> http://svn.apache.org/repos/asf/xmlgraphics/site/
> >>>
> >>> and the generated site docs go to
> >>>
> >>> http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
> >>>
> >>> /x1/www/xmgraphics.apache.org is svn of that deploy location, no idea
> >> how
> >>> often they run svn up or if it is done manually. Also no idea if they
> >> use
> >>> forrestbot (steps 2 and 3) or whether they svn ci the generated site,
> >> you'd
> >>> have to talk to Jeremias about that.
> >>>
> >>> So , possibly 2 slightly different methods.
> >>>
> >>> I'm happy to help show the way to Forrests' method. And of course I
> will
> >>> continue to be on this list for any help required afterwards. One
> thing
> >> to
> >>> note for others listening, it is necessary to have Apache Forrest
> >> installed
> >>> on your local machine in order to alter the xdocs, test locally, build
> >> and
> >>> then deploy.
> >>>
> >>> There is a renewed talk on infra lists about having a shared zone or
> >>> something else where projects can build sites using
> Forrest/Maven/Anakia
> >>> that would be installed on the zone, the idea I guess is that
> generated
> >>> source files would live there and be copied over to various projects
> >>> /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
> >>> following for now to see how it pans out, or how long it will take.
> Just
> >>> thought I'd mention it, in the meantime we need to do one of the
> above.
> >> I assume you're referring to the thread on Automating parts of
> >> the web site publishing process. I've seen the discussion but
> >> haven't had time to follow it closely enough to benefit from
> >> it.
> >>
> >>> So, here's how I see it for stdcxx :-
> >>>
> >>> Have forrest and site source files where they are currently in
> >>>
> >>> http://svn.apache.org/repos/asf/stdcxx/site/forrest/
> >>>
> >>> Have the generated site files in
> >>>
> >>> http://svn.apache.org/repos/asf/stdcxx/site/deploy/
> >>>
> >>> and 'svn remove' the current content from /site/
> >>>
> >>> The above structure will remove the nasty side effect you currently
> have
> >> of
> >>> forrest source files viewable on the web
> >> (http://stdcxx.apache.org/forrest/)
> >>> doesn't look good.
> >>>
> >>> Then create a cronjob to svn up hourly (or whatever delay you prefer)
> to
> >>> update your /x1/www/stdcxx.apache.org with the updated site files.
> >>>
> >>> That's about it for now, what do you think?
> >> Thanks for the detailed info! The depot structure and the cron
> >> job approach sound reasonable (we already have a cron job running
> >> to periodically update the existing site). My only concern is the
> >> requirement to run Forrest locally on each committer's machine.
> >
> > I understand that.
> >
> >> Do you happen to know the other projects' rationale for checking
> >> the generated sites into Subversion instead of generating their
> >> sites directly on people.a.o?
> >
> > Yes, Infra Policy.
> >
> > It seems that since the site is
> >> generated from sources that already are in Subversion there
> >> should be no reason to version the generated HTML as well, and
> >> being able to update the site without having to have Forrest
> >> install seems like a significant advantage. But given that most
> >> other projects do it differently I suspect I must be missing
> >> some significant disadvantages of the "simpler" approach. Is
> >> there concern with the overhead o projects running Forrest too
> >> often?
> >
> > Imagine 200+ projects all building their sites with
> > forrest/maven/anakia/whatever on p.a.o , all no doubt installing their
> own
> > copy too. The overhead would be massive if it were allowed.
> >
> > Also, generated docs I guess are still files produced by ASF projects,
> they
> > would also differ in their content and structure to the source files. As
> > such having the history would be a benefit.
> >
> > I'm just guessing at that last bit, what I do know is that infra
> currently
> > insists that
> > a) no projects to run builds on infra,
> > b) generated site docs are to be in svn.
> >
> > So, unless you can change that, and perhaps until that infra thread
> produces
> > something - join in as a usecase if you think it worthwile, then I'd go
> with
> > my suggestion.
> >
> > Those that don't contribute to the website docs wont need forrest.
> >
> > fwiw if you used Maven or any other build tool you'd be in the same
> > situation.
> >
> >
> >> FWIW, the way I originally set up this project was to generate
> >> the Forrest site in:
> >> http://people.apache.org/~sebor/stdcxx/forrest-site/
> >>
> >> The cron job that does the updating is in:
> >> /people.apache.org:/home/sebor/bin/update-site.sh
> >>
> >
> > Well, I'm not saying remove it , but ...
> >
> > At the end of the day, I've made my recommendation, its up to you guys
> how
> > you want to proceed.
> >
> > I have Forrest installed of course so there is no problem with me
> applying
> > doc patches and generating the site, if one or two others are happy to
> have
> > Forrest on their systems locally, then we don't really have a problem.
> >
> > Gav...
> >
> >> Martin
> >>
> >>> Gav...
> >>>
> >>>
> >>>
> >>
> >> --
> >> Internal Virus Database is out-of-date.
> >> Checked by AVG.
> >> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008
> 12:00
> >> AM
> >
> >
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
Re: Website Layout
Posted by Martin Sebor <ms...@gmail.com>.
Alright Gavin, thanks for your patience in discussing this.
If you can point me at your sources I'll generate the HTML
and commit the whole lot under
http://svn.apache.org/repos/asf/stdcxx/site/forrest
as you suggest, and work on replacing the existing site
with the generated docs.
Martin
Gavin wrote:
>
>> -----Original Message-----
>> From: Martin Sebor [mailto:msebor@gmail.com]
>> Sent: Thursday, 14 August 2008 6:32 AM
>> To: dev@stdcxx.apache.org
>> Subject: Re: Website Layout
>>
>> Gavin wrote:
>>>> -----Original Message-----
>>>> From: Martin Sebor [mailto:msebor@gmail.com]
>>>> Sent: Wednesday, 13 August 2008 4:49 AM
>>>> To: dev@stdcxx.apache.org
>>>> Subject: Re: Website Layout
>>>>
>>>> Gavin wrote:
>>> <snip>
>>>
>>>>> So whilst we are at this level of even-ness (?) it is a good time to
>>>> swap it
>>>>> over and make it live. However, over the next day or two, I will add
>>>>> developer docs on how to go about updating the site, altering/adding
>>>> pages
>>>>> etc..
>>>>>
>>>>> Let me know what you think.
>>>> Sounds like a plan.
>>>>
>>>> I assume we'll commit just the Forrest sources into Subversion
>>>> and generate the site out of them on people.a.o using a cron
>>>> job, correct?
>>> Well, I'm sure various projects do things in slightly different ways.
>>> However I would not recommend doing any building on people.a.o , and is
>> not
>>> necessary anyway.
>>>
>>> This is how Forrest, xmlgraphics and a few others do it :-
>>>
>>> 1. Alter xdocs locally to your needs.
>>> 2. svn ci to get sources upto date in svn
>>> 3. locally run 'forrest -f publish.xml build'
>>> 4. locally run 'forrest -f publish.xml deploy'
>>> 5. /x1/www/stdcxx.apache.org svn up
>>>
>>> That's the general gist, more fully,
>>>
>>> Forrest stores its site source files in
>>>
>>> http://svn.apache.org/repos/asf/forrest/trunk/site-author/
>>>
>>> and the generated site docs go to
>>>
>>> http://svn.apache.org/repos/asf/forrest/site/
>>>
>>> A cronjob on p.a.o then runs svn up hourly to
>>> /x1/www/forrest.apache.org
>>>
>>> The hourly sync to eos/aurora then picks that up and your updated docs
>> are
>>> then live.
>>>
>>> Again, with xmlgraphics, site source files stored in
>>>
>>> http://svn.apache.org/repos/asf/xmlgraphics/site/
>>>
>>> and the generated site docs go to
>>>
>>> http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
>>>
>>> /x1/www/xmgraphics.apache.org is svn of that deploy location, no idea
>> how
>>> often they run svn up or if it is done manually. Also no idea if they
>> use
>>> forrestbot (steps 2 and 3) or whether they svn ci the generated site,
>> you'd
>>> have to talk to Jeremias about that.
>>>
>>> So , possibly 2 slightly different methods.
>>>
>>> I'm happy to help show the way to Forrests' method. And of course I will
>>> continue to be on this list for any help required afterwards. One thing
>> to
>>> note for others listening, it is necessary to have Apache Forrest
>> installed
>>> on your local machine in order to alter the xdocs, test locally, build
>> and
>>> then deploy.
>>>
>>> There is a renewed talk on infra lists about having a shared zone or
>>> something else where projects can build sites using Forrest/Maven/Anakia
>>> that would be installed on the zone, the idea I guess is that generated
>>> source files would live there and be copied over to various projects
>>> /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
>>> following for now to see how it pans out, or how long it will take. Just
>>> thought I'd mention it, in the meantime we need to do one of the above.
>> I assume you're referring to the thread on Automating parts of
>> the web site publishing process. I've seen the discussion but
>> haven't had time to follow it closely enough to benefit from
>> it.
>>
>>> So, here's how I see it for stdcxx :-
>>>
>>> Have forrest and site source files where they are currently in
>>>
>>> http://svn.apache.org/repos/asf/stdcxx/site/forrest/
>>>
>>> Have the generated site files in
>>>
>>> http://svn.apache.org/repos/asf/stdcxx/site/deploy/
>>>
>>> and 'svn remove' the current content from /site/
>>>
>>> The above structure will remove the nasty side effect you currently have
>> of
>>> forrest source files viewable on the web
>> (http://stdcxx.apache.org/forrest/)
>>> doesn't look good.
>>>
>>> Then create a cronjob to svn up hourly (or whatever delay you prefer) to
>>> update your /x1/www/stdcxx.apache.org with the updated site files.
>>>
>>> That's about it for now, what do you think?
>> Thanks for the detailed info! The depot structure and the cron
>> job approach sound reasonable (we already have a cron job running
>> to periodically update the existing site). My only concern is the
>> requirement to run Forrest locally on each committer's machine.
>
> I understand that.
>
>> Do you happen to know the other projects' rationale for checking
>> the generated sites into Subversion instead of generating their
>> sites directly on people.a.o?
>
> Yes, Infra Policy.
>
> It seems that since the site is
>> generated from sources that already are in Subversion there
>> should be no reason to version the generated HTML as well, and
>> being able to update the site without having to have Forrest
>> install seems like a significant advantage. But given that most
>> other projects do it differently I suspect I must be missing
>> some significant disadvantages of the "simpler" approach. Is
>> there concern with the overhead o projects running Forrest too
>> often?
>
> Imagine 200+ projects all building their sites with
> forrest/maven/anakia/whatever on p.a.o , all no doubt installing their own
> copy too. The overhead would be massive if it were allowed.
>
> Also, generated docs I guess are still files produced by ASF projects, they
> would also differ in their content and structure to the source files. As
> such having the history would be a benefit.
>
> I'm just guessing at that last bit, what I do know is that infra currently
> insists that
> a) no projects to run builds on infra,
> b) generated site docs are to be in svn.
>
> So, unless you can change that, and perhaps until that infra thread produces
> something - join in as a usecase if you think it worthwile, then I'd go with
> my suggestion.
>
> Those that don't contribute to the website docs wont need forrest.
>
> fwiw if you used Maven or any other build tool you'd be in the same
> situation.
>
>
>> FWIW, the way I originally set up this project was to generate
>> the Forrest site in:
>> http://people.apache.org/~sebor/stdcxx/forrest-site/
>>
>> The cron job that does the updating is in:
>> /people.apache.org:/home/sebor/bin/update-site.sh
>>
>
> Well, I'm not saying remove it , but ...
>
> At the end of the day, I've made my recommendation, its up to you guys how
> you want to proceed.
>
> I have Forrest installed of course so there is no problem with me applying
> doc patches and generating the site, if one or two others are happy to have
> Forrest on their systems locally, then we don't really have a problem.
>
> Gav...
>
>> Martin
>>
>>> Gav...
>>>
>>>
>>>
>>
>> --
>> Internal Virus Database is out-of-date.
>> Checked by AVG.
>> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
>> AM
>
>
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com]
> Sent: Thursday, 14 August 2008 6:32 AM
> To: dev@stdcxx.apache.org
> Subject: Re: Website Layout
>
> Gavin wrote:
> >
> >> -----Original Message-----
> >> From: Martin Sebor [mailto:msebor@gmail.com]
> >> Sent: Wednesday, 13 August 2008 4:49 AM
> >> To: dev@stdcxx.apache.org
> >> Subject: Re: Website Layout
> >>
> >> Gavin wrote:
> >
> > <snip>
> >
> >>> So whilst we are at this level of even-ness (?) it is a good time to
> >> swap it
> >>> over and make it live. However, over the next day or two, I will add
> >>> developer docs on how to go about updating the site, altering/adding
> >> pages
> >>> etc..
> >>>
> >>> Let me know what you think.
> >> Sounds like a plan.
> >>
> >> I assume we'll commit just the Forrest sources into Subversion
> >> and generate the site out of them on people.a.o using a cron
> >> job, correct?
> >
> > Well, I'm sure various projects do things in slightly different ways.
> > However I would not recommend doing any building on people.a.o , and is
> not
> > necessary anyway.
> >
> > This is how Forrest, xmlgraphics and a few others do it :-
> >
> > 1. Alter xdocs locally to your needs.
> > 2. svn ci to get sources upto date in svn
> > 3. locally run 'forrest -f publish.xml build'
> > 4. locally run 'forrest -f publish.xml deploy'
> > 5. /x1/www/stdcxx.apache.org svn up
> >
> > That's the general gist, more fully,
> >
> > Forrest stores its site source files in
> >
> > http://svn.apache.org/repos/asf/forrest/trunk/site-author/
> >
> > and the generated site docs go to
> >
> > http://svn.apache.org/repos/asf/forrest/site/
> >
> > A cronjob on p.a.o then runs svn up hourly to
> > /x1/www/forrest.apache.org
> >
> > The hourly sync to eos/aurora then picks that up and your updated docs
> are
> > then live.
> >
> > Again, with xmlgraphics, site source files stored in
> >
> > http://svn.apache.org/repos/asf/xmlgraphics/site/
> >
> > and the generated site docs go to
> >
> > http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
> >
> > /x1/www/xmgraphics.apache.org is svn of that deploy location, no idea
> how
> > often they run svn up or if it is done manually. Also no idea if they
> use
> > forrestbot (steps 2 and 3) or whether they svn ci the generated site,
> you'd
> > have to talk to Jeremias about that.
> >
> > So , possibly 2 slightly different methods.
> >
> > I'm happy to help show the way to Forrests' method. And of course I will
> > continue to be on this list for any help required afterwards. One thing
> to
> > note for others listening, it is necessary to have Apache Forrest
> installed
> > on your local machine in order to alter the xdocs, test locally, build
> and
> > then deploy.
> >
> > There is a renewed talk on infra lists about having a shared zone or
> > something else where projects can build sites using Forrest/Maven/Anakia
> > that would be installed on the zone, the idea I guess is that generated
> > source files would live there and be copied over to various projects
> > /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
> > following for now to see how it pans out, or how long it will take. Just
> > thought I'd mention it, in the meantime we need to do one of the above.
>
> I assume you're referring to the thread on Automating parts of
> the web site publishing process. I've seen the discussion but
> haven't had time to follow it closely enough to benefit from
> it.
>
> >
> > So, here's how I see it for stdcxx :-
> >
> > Have forrest and site source files where they are currently in
> >
> > http://svn.apache.org/repos/asf/stdcxx/site/forrest/
> >
> > Have the generated site files in
> >
> > http://svn.apache.org/repos/asf/stdcxx/site/deploy/
> >
> > and 'svn remove' the current content from /site/
> >
> > The above structure will remove the nasty side effect you currently have
> of
> > forrest source files viewable on the web
> (http://stdcxx.apache.org/forrest/)
> > doesn't look good.
> >
> > Then create a cronjob to svn up hourly (or whatever delay you prefer) to
> > update your /x1/www/stdcxx.apache.org with the updated site files.
> >
> > That's about it for now, what do you think?
>
> Thanks for the detailed info! The depot structure and the cron
> job approach sound reasonable (we already have a cron job running
> to periodically update the existing site). My only concern is the
> requirement to run Forrest locally on each committer's machine.
I understand that.
> Do you happen to know the other projects' rationale for checking
> the generated sites into Subversion instead of generating their
> sites directly on people.a.o?
Yes, Infra Policy.
It seems that since the site is
> generated from sources that already are in Subversion there
> should be no reason to version the generated HTML as well, and
> being able to update the site without having to have Forrest
> install seems like a significant advantage. But given that most
> other projects do it differently I suspect I must be missing
> some significant disadvantages of the "simpler" approach. Is
> there concern with the overhead o projects running Forrest too
> often?
Imagine 200+ projects all building their sites with
forrest/maven/anakia/whatever on p.a.o , all no doubt installing their own
copy too. The overhead would be massive if it were allowed.
Also, generated docs I guess are still files produced by ASF projects, they
would also differ in their content and structure to the source files. As
such having the history would be a benefit.
I'm just guessing at that last bit, what I do know is that infra currently
insists that
a) no projects to run builds on infra,
b) generated site docs are to be in svn.
So, unless you can change that, and perhaps until that infra thread produces
something - join in as a usecase if you think it worthwile, then I'd go with
my suggestion.
Those that don't contribute to the website docs wont need forrest.
fwiw if you used Maven or any other build tool you'd be in the same
situation.
>
> FWIW, the way I originally set up this project was to generate
> the Forrest site in:
> http://people.apache.org/~sebor/stdcxx/forrest-site/
>
> The cron job that does the updating is in:
> /people.apache.org:/home/sebor/bin/update-site.sh
>
Well, I'm not saying remove it , but ...
At the end of the day, I've made my recommendation, its up to you guys how
you want to proceed.
I have Forrest installed of course so there is no problem with me applying
doc patches and generating the site, if one or two others are happy to have
Forrest on their systems locally, then we don't really have a problem.
Gav...
> Martin
>
> >
> > Gav...
> >
> >
> >
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
Re: Website Layout
Posted by Martin Sebor <ms...@gmail.com>.
Gavin wrote:
>
>> -----Original Message-----
>> From: Martin Sebor [mailto:msebor@gmail.com]
>> Sent: Wednesday, 13 August 2008 4:49 AM
>> To: dev@stdcxx.apache.org
>> Subject: Re: Website Layout
>>
>> Gavin wrote:
>
> <snip>
>
>>> So whilst we are at this level of even-ness (?) it is a good time to
>> swap it
>>> over and make it live. However, over the next day or two, I will add
>>> developer docs on how to go about updating the site, altering/adding
>> pages
>>> etc..
>>>
>>> Let me know what you think.
>> Sounds like a plan.
>>
>> I assume we'll commit just the Forrest sources into Subversion
>> and generate the site out of them on people.a.o using a cron
>> job, correct?
>
> Well, I'm sure various projects do things in slightly different ways.
> However I would not recommend doing any building on people.a.o , and is not
> necessary anyway.
>
> This is how Forrest, xmlgraphics and a few others do it :-
>
> 1. Alter xdocs locally to your needs.
> 2. svn ci to get sources upto date in svn
> 3. locally run 'forrest -f publish.xml build'
> 4. locally run 'forrest -f publish.xml deploy'
> 5. /x1/www/stdcxx.apache.org svn up
>
> That's the general gist, more fully,
>
> Forrest stores its site source files in
>
> http://svn.apache.org/repos/asf/forrest/trunk/site-author/
>
> and the generated site docs go to
>
> http://svn.apache.org/repos/asf/forrest/site/
>
> A cronjob on p.a.o then runs svn up hourly to
> /x1/www/forrest.apache.org
>
> The hourly sync to eos/aurora then picks that up and your updated docs are
> then live.
>
> Again, with xmlgraphics, site source files stored in
>
> http://svn.apache.org/repos/asf/xmlgraphics/site/
>
> and the generated site docs go to
>
> http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
>
> /x1/www/xmgraphics.apache.org is svn of that deploy location, no idea how
> often they run svn up or if it is done manually. Also no idea if they use
> forrestbot (steps 2 and 3) or whether they svn ci the generated site, you'd
> have to talk to Jeremias about that.
>
> So , possibly 2 slightly different methods.
>
> I'm happy to help show the way to Forrests' method. And of course I will
> continue to be on this list for any help required afterwards. One thing to
> note for others listening, it is necessary to have Apache Forrest installed
> on your local machine in order to alter the xdocs, test locally, build and
> then deploy.
>
> There is a renewed talk on infra lists about having a shared zone or
> something else where projects can build sites using Forrest/Maven/Anakia
> that would be installed on the zone, the idea I guess is that generated
> source files would live there and be copied over to various projects
> /x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
> following for now to see how it pans out, or how long it will take. Just
> thought I'd mention it, in the meantime we need to do one of the above.
I assume you're referring to the thread on Automating parts of
the web site publishing process. I've seen the discussion but
haven't had time to follow it closely enough to benefit from
it.
>
> So, here's how I see it for stdcxx :-
>
> Have forrest and site source files where they are currently in
>
> http://svn.apache.org/repos/asf/stdcxx/site/forrest/
>
> Have the generated site files in
>
> http://svn.apache.org/repos/asf/stdcxx/site/deploy/
>
> and 'svn remove' the current content from /site/
>
> The above structure will remove the nasty side effect you currently have of
> forrest source files viewable on the web (http://stdcxx.apache.org/forrest/)
> doesn't look good.
>
> Then create a cronjob to svn up hourly (or whatever delay you prefer) to
> update your /x1/www/stdcxx.apache.org with the updated site files.
>
> That's about it for now, what do you think?
Thanks for the detailed info! The depot structure and the cron
job approach sound reasonable (we already have a cron job running
to periodically update the existing site). My only concern is the
requirement to run Forrest locally on each committer's machine.
Do you happen to know the other projects' rationale for checking
the generated sites into Subversion instead of generating their
sites directly on people.a.o? It seems that since the site is
generated from sources that already are in Subversion there
should be no reason to version the generated HTML as well, and
being able to update the site without having to have Forrest
install seems like a significant advantage. But given that most
other projects do it differently I suspect I must be missing
some significant disadvantages of the "simpler" approach. Is
there concern with the overhead o projects running Forrest too
often?
FWIW, the way I originally set up this project was to generate
the Forrest site in:
http://people.apache.org/~sebor/stdcxx/forrest-site/
The cron job that does the updating is in:
/people.apache.org:/home/sebor/bin/update-site.sh
Martin
>
> Gav...
>
>
>
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com]
> Sent: Wednesday, 13 August 2008 4:49 AM
> To: dev@stdcxx.apache.org
> Subject: Re: Website Layout
>
> Gavin wrote:
<snip>
> >
> > So whilst we are at this level of even-ness (?) it is a good time to
> swap it
> > over and make it live. However, over the next day or two, I will add
> > developer docs on how to go about updating the site, altering/adding
> pages
> > etc..
> >
> > Let me know what you think.
>
> Sounds like a plan.
>
> I assume we'll commit just the Forrest sources into Subversion
> and generate the site out of them on people.a.o using a cron
> job, correct?
Well, I'm sure various projects do things in slightly different ways.
However I would not recommend doing any building on people.a.o , and is not
necessary anyway.
This is how Forrest, xmlgraphics and a few others do it :-
1. Alter xdocs locally to your needs.
2. svn ci to get sources upto date in svn
3. locally run 'forrest -f publish.xml build'
4. locally run 'forrest -f publish.xml deploy'
5. /x1/www/stdcxx.apache.org svn up
That's the general gist, more fully,
Forrest stores its site source files in
http://svn.apache.org/repos/asf/forrest/trunk/site-author/
and the generated site docs go to
http://svn.apache.org/repos/asf/forrest/site/
A cronjob on p.a.o then runs svn up hourly to
/x1/www/forrest.apache.org
The hourly sync to eos/aurora then picks that up and your updated docs are
then live.
Again, with xmlgraphics, site source files stored in
http://svn.apache.org/repos/asf/xmlgraphics/site/
and the generated site docs go to
http://svn.apache.org/repos/asf/xmlgraphics/site/deploy/
/x1/www/xmgraphics.apache.org is svn of that deploy location, no idea how
often they run svn up or if it is done manually. Also no idea if they use
forrestbot (steps 2 and 3) or whether they svn ci the generated site, you'd
have to talk to Jeremias about that.
So , possibly 2 slightly different methods.
I'm happy to help show the way to Forrests' method. And of course I will
continue to be on this list for any help required afterwards. One thing to
note for others listening, it is necessary to have Apache Forrest installed
on your local machine in order to alter the xdocs, test locally, build and
then deploy.
There is a renewed talk on infra lists about having a shared zone or
something else where projects can build sites using Forrest/Maven/Anakia
that would be installed on the zone, the idea I guess is that generated
source files would live there and be copied over to various projects
/x1/www/*.a.o/ area. I'm not sure how it would work exactly but I'm
following for now to see how it pans out, or how long it will take. Just
thought I'd mention it, in the meantime we need to do one of the above.
So, here's how I see it for stdcxx :-
Have forrest and site source files where they are currently in
http://svn.apache.org/repos/asf/stdcxx/site/forrest/
Have the generated site files in
http://svn.apache.org/repos/asf/stdcxx/site/deploy/
and 'svn remove' the current content from /site/
The above structure will remove the nasty side effect you currently have of
forrest source files viewable on the web (http://stdcxx.apache.org/forrest/)
doesn't look good.
Then create a cronjob to svn up hourly (or whatever delay you prefer) to
update your /x1/www/stdcxx.apache.org with the updated site files.
That's about it for now, what do you think?
Gav...
Re: Website Layout
Posted by Martin Sebor <ms...@gmail.com>.
Gavin wrote:
>
>> -----Original Message-----
>> From: Martin Sebor [mailto:msebor@gmail.com]
>> Sent: Tuesday, 12 August 2008 12:51 PM
>> To: dev@stdcxx.apache.org
>> Subject: Re: Website Layout
>>
>> Gav.... wrote:
>>> Hi Guys, back again,
>>>
>>> It's been a while since March, moving to the other side of the continent
>> and
>>> other stuff etc..
>>>
>>> Anyway, I did some more to the Forrest site, for me to work a bit more
>>> freely I have put up a version at :-
>>>
>>> http://people.apache.org/~gmcdonald/stdcxx/index.html
>> This looks fantastic!
>>
>>> I realise I may be a bit behind as some content will have changed, but
>> if
>>> your happy with the layout etc, we can move on - that is of course you
>>> haven't decided on another route yet.
>> Other than a few minor updates I don't think we've made any
>> significant changes.
>>
>>> I'll continue on and get caught up on doc site content changes, then
>> start
>>> activating links etc.
>> Let me know if there's I/we can do to help.
>
> I'm not sure if you got my other emails to this list, I'm subscribed using a
> new one now.
There are 4 emails from you on the subject in the archives,
so unless you sent more we've got'em all :)
http://stdcxx.markmail.org/search/?q=type%3Adevelopment+from%3AGavin
I did a quick review and everything looks a-ok. I spotted
just one tiny little typo in Project Roles where "Standard
c++ project" should read "C++ Standard Library project" or
just stdcxx. But we can fix that after the site is rolled
out.
>
> Anyway, in summary, I think it is now ready, I've converted all pages and as
> far as I can see have also brought it bang up to date.
>
> So whilst we are at this level of even-ness (?) it is a good time to swap it
> over and make it live. However, over the next day or two, I will add
> developer docs on how to go about updating the site, altering/adding pages
> etc..
>
> Let me know what you think.
Sounds like a plan.
I assume we'll commit just the Forrest sources into Subversion
and generate the site out of them on people.a.o using a cron
job, correct?
Martin
>
> Gav...
>
>> Martin
>>
>>> Gav...
>>>
>>>
>>>> -----Original Message-----
>>>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>>>> Sent: Tuesday, 11 March 2008 11:25 PM
>>>> To: dev@stdcxx.apache.org
>>>> Subject: RE: Website Layout
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Martin Sebor [mailto:sebor@roguewave.com]
>>>>> Sent: Wednesday, 6 February 2008 7:04 AM
>>>>> To: dev@stdcxx.apache.org
>>>>> Subject: Re: Website Layout
>>>>>
>>>>> Gav.... wrote:
>>>>>> Hi Eric/All,
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
>>>>>>> Sent: Saturday, 2 February 2008 2:17 AM
>>>>>>> To: dev@stdcxx.apache.org
>>>>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>>>
>>>>>>>
>>>>>>> I like it. It follows the style of the current site so it's not
>>>>>>> too disruptive.
>>>>>>>
>>>>>>> Couple minor suggestions:
>>>>>>>
>>>>>>> 1. Move the Documentation nav up to a tab next to the Download tab.
>>>>>> Yes, that can be done, no problem, I'll do that in my next patch if
>>>>>> no objections.
>>>>> Personally, I would probably try to tackle the migration of the
>>>>> site as it is to Forrest first so we can publish it as our default,
>>>>> and then work on improving the layout next. I don't know if this
>>>>> approach makes sense or it's less effort to restructure it at the
>>>>> same time.
>>>>>
>>>>>>> 2. Move all links at the top of the home page to the nav bar,
>>>>>>> and subdivide them into groups (e.g. General [Objectives, About],
>>>>>>> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
>>>>>>> License, Platforms, References]
>>>>>> Those links are auto generated from <sections> in the source and are
>>>>>> internal links to the relative section on that page. Dividing them
>>>>>> would mean creating new pages and moving content out of the home page
>>>>>> onto the new ones. This is no problem either, but its not my site, so
>>>>>> do you guys want to discuss the layout how you want it and I'll make
>>>>>> the changes ?
>>>>> Sure. We don't have any design document or a rationale for the
>>>>> current site but it makes sense to discuss it before Gav puts
>>>>> in a whole lot of time into it. Btw., how difficult is it to
>>>>> restructure the site in Forrest if we change our mind? :)
>>>> It's fairly easy, so no problem.
>>>>
>>>>> Here are some of my random thoughts on the subject...
>>>>>
>>>>> As far as tabs and menus go, I'd be inclined to follow the layout
>>>>> used by other projects. From what I see on the Forrest site, for
>>>>> instance, every tab is a menu with each menu item pointing to
>>>>> a separate page (although the Versioned Docs and Plugins tabs
>>>>> look like they're messed up). So if we expect each of Downloads
>>>>> and Documentation to break down into a number of menu items with
>>>>> a page for each, making them tabs sounds dandy.
>>>>>
>>>>> The one page I think is already way too long and that we should
>>>>> probably break up into a number of smaller ones is index.html
>>>>> (is there any kind of rule of thumb on how long the ideal page
>>>>> should be?) We should probably split it up into an About page
>>>>> (what is stdcxx), another one just for News, an another for
>>>>> our "mission statement" (current Objectives). I can see us also
>>>>> wanting to have a separate page or even a tab for Developers (as
>>>>> on the Forrest page), and split that one into a page (or more)
>>>>> for each of Committers, Contributors, and Users. And maybe also
>>>>> PMC. Then there is Communication and Mailing Lists which could
>>>>> be on the same page. I don't know how useful the References
>>>>> section is. Seems like keeping this on the Wiki might work
>>>>> better.
>>>> I attached a diff to the issue making a start along the lines above.
>>>> Once that's committed, I'll carry on and do some more.
>>>>
>>>>> Btw., I should mention that during the restructuring of the site
>>>>> I think it's important to preserve all existing links and ideally
>>>>> also major anchors so we don't break links pointing to our site.
>>>> If I do break any, I'll be sure to recheck and change them back where
>>>> possible.
>>>>
>>>> Incidently, I'll try and tackle the converting of the Class Reference
>>>> and User Guides last - there is a technique described at [1] , but lets
>>>> get everything else sorted first and happy, then I'll look at them.
>>>>
>>>> [1] -
>>>> http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
>>>> source.html#cust
>>>> om
>>>>
>>>>
>>>>
>>>>> Martin
>>>>>
>>>>>>> 3. Where's the logo? :)
>>>>>> I'll fix that.
>>>> fixed.
>>>>
>>>> Gav...
>>>>
>>>>
>>>>>> Gav...
>>>>>>
>>>>>>> Brad.
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>>>>>>>> Sent: Friday, February 01, 2008 1:25 AM
>>>>>>>> To: dev@stdcxx.apache.org
>>>>>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>>>>
>>>>>>>> G'Day,
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
>>>>>>>> Martin Sebor
>>>>>>>>> Sent: Friday, 1 February 2008 3:00 PM
>>>>>>>>> To: dev@stdcxx.apache.org
>>>>>>>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>>>>>
>>>>>>>>> Gav... wrote:
>>>>>>>>>> Hi Martin,
>>>>>>>>>>
>>>>>>>>>> Let me know what info you need from me next.
>>>>>>>>>> Once the source files I sent are in svn, then I'll be
>>>>>>>> able to patch
>>>>>>>>>> properly against that.
>>>>>>>>> It looks quite good, thanks! I published it in my home directory
>>>>>>>>> to get some feedback from others:
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
>>>>>>>> As initial information for others, the look of this site is the
>>>>>>>> standard issue 'forrest pelt theme' and if so wish, can be changed
>>>>>>>> to have more unique feel to it. This can wait I think until the
>>>>>>>> site is live and populated with docs.
>>>>>>>>
>>>>>>>>> Btw., it looks like a couple of typos snuck into index.xml and
>>>>>>>>> bugs.xml. I corrected them to get forrest to generate the static
>>>>>>>>> site (otherwise it fails)...
>>>>>>>> Damn, sorry, I tested using 'forrest run' which ensures the
>>>>>>>> site is mostly
>>>>>>>> fine and working - but does not scrutinise the xdocs for
>>>>>>>> validity against
>>>>>>>> the DTD. Only when a 'forrest site' or 'forrest
>>>>>>>> validate-xdocs' is run do
>>>>>>>> the files get checked against the DTD.
>>>>>>>>
>>>>>>>>> ... but I still get the error below at the
>>>>>>>>> end. It looks like a link is bad or something.
>>>>>>>>>
>>>>>>>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
>>>>>>>>> X [0] favicon.ico BROKEN: No
>>>>>>>>> pipeline matched request: favicon.ico
>>>>>>>>> at <map:mount> -
>>>>>>>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
>>>>>>>>> ...
>>>>>>>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
>>>> 42
>>>>>>>>> Java Result: 1
>>>>>>>>>
>>>>>>>>> Copying broken links file to site root.
>>>>>>>>>
>>>>>>>>> Copying 1 file to /build/sebor/tmp/site2/build/site
>>>>>>>>>
>>>>>>>>> BUILD FAILED
>>>>>>>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
>>>>>>>>> building site.
>>>>>>>>>
>>>>>>>>> There appears to be a problem with your site build.
>>>>>>>> Easy one and my bad again. Automatically a favicon.ico is
>>>>>>>> associated with
>>>>>>>> the site and is in fact copied there when doing a 'forrest
>>>>>>>> seed-sample'.
>>>>>>>> As you found out though this produces many un-needed sample
>>>>>>>> files. So I
>>>>>>>> created the initial layout with a 'forrest seed-basic' which gives
>>>> you
>>>>>>>> a site structure but no files and in this case no favicon either.
>>>>>>>>
>>>>>>>> So the cure is to stick a favicon.ico directly into the xdocs
>>>> folder.
>>>>>>>> The site will then build successfully.
>>>>>>>>
>>>>>>>>> The two typos are: a missing underscore in the section id
>>>>>>>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
>>>>>>>>> gives rather cryptic errors for them.
>>>>>>>> The error messages were mainly to do with why they did not
>>>>>>>> conform with the
>>>>>>>> DTD - i.e the # symbol is not allowed directly beneath <ol>
>>>>>>>> and points out
>>>>>>>> that only <li> can go inside.
>>>>>>>>
>>>>>>>> Most of the time, we will use Forrests v2.0 DTD -
>>>>>>>>
>>>>>>>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
>>>>>>>>
>>>>>>>> (it is working towards being more xhtml2 compliant)
>>>>>>>>
>>>>>>>>> So sounds like the next step is to commit the prototype into svn
>>>>>>>>> and set up a cron job to get it periodically published into some
>>>>>>>>> sandbox (such as my home directory) so we can work on the tables
>>>>>>>>> etc. Is that how you'd like to proceed?
>>>>>>>> Yep, fine by me, at least I'll be able to be useful with patches
>>>> then.
>>>>>>>> Once your happy with stability, completeness and the
>>>>>>>> forrestbot publishing
>>>>>>>> is working well, then it can be moved when your happy.
>>>>>>>>
>>>>>>>>> I'm also curious if you have a suggestion for our documentation.
>>>>>>>>> Would it make sense to try to convert it as well or might some
>>>>>>>>> other solution be more appropriate?
>>>>>>>> I have referred this to the Forrest dev list. It should not
>>>>>>>> be a problem
>>>>>>>> in principle, convert the .html files into xdoc xml and then
>>>>>>>> back into .html
>>>>>>>> integrated into the rest of the generated site. Hopefully the
>>>> initial
>>>>>>>> conversion to xdoc can be automated. Once in xdoc xml format
>>>>>>>> then they can
>>>>>>>> be placed appropriately, added to the site.xml and tabs.xml
>>>>>>>> files and from
>>>>>>>> then on be part of the site proper.
>>>>>>>>
>>>>>>>>>> I notice Jira replies are set to issues@, is there a Jira
>>>>>>>> ticket filed
>>>>>>>>> to
>>>>>>>>>> change this to dev@.
>>>>>>>>> Not yet. I was hoping to get to it this week but lately time has
>>>>>>>>> a habit of getting away from me... You don't happen to know where
>>>>>>>>> to change this, do you?
>>>>>>>> I don't have the access to do it, I've asked on #infra and
>>>>>>>> will let you know
>>>>>>>> if someone does it. Otherwise you need to send a mail to
>>>>>>>> apmail@ and file a
>>>>>>>> Jira Issue on infra for it to be done .
>>>>>>>>
>>>>>>>> (http://apache.org/dev/reporting-issues.html#mail-config)
>>>>>>>>
>>>>>>>>
>>>>>>>> Gav...
>>>>>>>>
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>> Gav...
>>>>>>>>>>
>>>>>>>>>> <quote who="Martin Sebor (JIRA)">
>>>>>>>>>>> [
>>>>>>>>>>> https://issues.apache.org/jira/browse/STDCXX-
>>>>>>>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
>>>> tabpanel
>>>>>>>>>>> ]
>>>>>>>>>>>
>>>>>>>>>>> Martin Sebor reassigned STDCXX-686:
>>>>>>>>>>> -----------------------------------
>>>>>>>>>>>
>>>>>>>>>>> Assignee: Martin Sebor
>>>>>>>>>>>
>>>>>>>>>>>> redesign web site
>>>>>>>>>>>> -----------------
>>>>>>>>>>>>
>>>>>>>>>>>> Key: STDCXX-686
>>>>>>>>>>>> URL:
>>>>>>>> https://issues.apache.org/jira/browse/STDCXX-686
>>>>>>>>>>>> Project: C++ Standard Library
>>>>>>>>>>>> Issue Type: Improvement
>>>>>>>>>>>> Components: Web
>>>>>>>>>>>> Reporter: Martin Sebor
>>>>>>>>>>>> Assignee: Martin Sebor
>>>>>>>>>>>> Attachments: Copy of stdcxx.zip
>>>>>>>>>>>>
>>>>>>>>>>>> Original Estimate: 16h
>>>>>>>>>>>> Remaining Estimate: 16h
>>>>>>>>>>>>
>>>>>>>>>>>> The current web site is a bunch of static HTML pages
>>>>>>>> with a lot of
>>>>>>>>>>>> difficult-to-maintain formatting cruft copied from
>>>>>>>> pages of another
>>>>>>>>>>>> incubator project. We should look into generating the site from
>>>>>>>>>>>> easier-to-maintain "sources" using a tool like Apache
>>>>>>>> Forrest or some
>>>>>>>>>>>> such.
>>>>>>>>>>> --
>>>>>>>>>>> This message is automatically generated by JIRA.
>>>>>>>>>>> -
>>>>>>>>>>> You can reply to this email to add a comment to the issue
>> online.
>>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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
>>>>>>> --
>>>>>>> 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
>>>>>
>>>>> --
>>>>> Internal Virus Database is out-of-date.
>>>>> Checked by AVG Free Edition.
>>>>> Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
>>>> 1/12/2008
>>>>> 2:04 PM
>>>> --
>>>> No virus found in this incoming message.
>>>> Checked by AVG.
>>>> Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
>> 3/10/2008
>>>> 11:07 AM
>>>
>>
>> --
>> Internal Virus Database is out-of-date.
>> Checked by AVG.
>> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
>> AM
>
>
RE: Website Layout
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com]
> Sent: Tuesday, 12 August 2008 12:51 PM
> To: dev@stdcxx.apache.org
> Subject: Re: Website Layout
>
> Gav.... wrote:
> > Hi Guys, back again,
> >
> > It's been a while since March, moving to the other side of the continent
> and
> > other stuff etc..
> >
> > Anyway, I did some more to the Forrest site, for me to work a bit more
> > freely I have put up a version at :-
> >
> > http://people.apache.org/~gmcdonald/stdcxx/index.html
>
> This looks fantastic!
>
> >
> > I realise I may be a bit behind as some content will have changed, but
> if
> > your happy with the layout etc, we can move on - that is of course you
> > haven't decided on another route yet.
>
> Other than a few minor updates I don't think we've made any
> significant changes.
>
> >
> > I'll continue on and get caught up on doc site content changes, then
> start
> > activating links etc.
>
> Let me know if there's I/we can do to help.
I'm not sure if you got my other emails to this list, I'm subscribed using a
new one now.
Anyway, in summary, I think it is now ready, I've converted all pages and as
far as I can see have also brought it bang up to date.
So whilst we are at this level of even-ness (?) it is a good time to swap it
over and make it live. However, over the next day or two, I will add
developer docs on how to go about updating the site, altering/adding pages
etc..
Let me know what you think.
Gav...
>
> Martin
>
> >
> > Gav...
> >
> >
> >> -----Original Message-----
> >> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> >> Sent: Tuesday, 11 March 2008 11:25 PM
> >> To: dev@stdcxx.apache.org
> >> Subject: RE: Website Layout
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Martin Sebor [mailto:sebor@roguewave.com]
> >>> Sent: Wednesday, 6 February 2008 7:04 AM
> >>> To: dev@stdcxx.apache.org
> >>> Subject: Re: Website Layout
> >>>
> >>> Gav.... wrote:
> >>>> Hi Eric/All,
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> >>>>> Sent: Saturday, 2 February 2008 2:17 AM
> >>>>> To: dev@stdcxx.apache.org
> >>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> >>>>>
> >>>>>
> >>>>> I like it. It follows the style of the current site so it's not
> >>>>> too disruptive.
> >>>>>
> >>>>> Couple minor suggestions:
> >>>>>
> >>>>> 1. Move the Documentation nav up to a tab next to the Download tab.
> >>>> Yes, that can be done, no problem, I'll do that in my next patch if
> >>>> no objections.
> >>> Personally, I would probably try to tackle the migration of the
> >>> site as it is to Forrest first so we can publish it as our default,
> >>> and then work on improving the layout next. I don't know if this
> >>> approach makes sense or it's less effort to restructure it at the
> >>> same time.
> >>>
> >>>>> 2. Move all links at the top of the home page to the nav bar,
> >>>>> and subdivide them into groups (e.g. General [Objectives, About],
> >>>>> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> >>>>> License, Platforms, References]
> >>>> Those links are auto generated from <sections> in the source and are
> >>>> internal links to the relative section on that page. Dividing them
> >>>> would mean creating new pages and moving content out of the home page
> >>>> onto the new ones. This is no problem either, but its not my site, so
> >>>> do you guys want to discuss the layout how you want it and I'll make
> >>>> the changes ?
> >>> Sure. We don't have any design document or a rationale for the
> >>> current site but it makes sense to discuss it before Gav puts
> >>> in a whole lot of time into it. Btw., how difficult is it to
> >>> restructure the site in Forrest if we change our mind? :)
> >> It's fairly easy, so no problem.
> >>
> >>> Here are some of my random thoughts on the subject...
> >>>
> >>> As far as tabs and menus go, I'd be inclined to follow the layout
> >>> used by other projects. From what I see on the Forrest site, for
> >>> instance, every tab is a menu with each menu item pointing to
> >>> a separate page (although the Versioned Docs and Plugins tabs
> >>> look like they're messed up). So if we expect each of Downloads
> >>> and Documentation to break down into a number of menu items with
> >>> a page for each, making them tabs sounds dandy.
> >>>
> >>> The one page I think is already way too long and that we should
> >>> probably break up into a number of smaller ones is index.html
> >>> (is there any kind of rule of thumb on how long the ideal page
> >>> should be?) We should probably split it up into an About page
> >>> (what is stdcxx), another one just for News, an another for
> >>> our "mission statement" (current Objectives). I can see us also
> >>> wanting to have a separate page or even a tab for Developers (as
> >>> on the Forrest page), and split that one into a page (or more)
> >>> for each of Committers, Contributors, and Users. And maybe also
> >>> PMC. Then there is Communication and Mailing Lists which could
> >>> be on the same page. I don't know how useful the References
> >>> section is. Seems like keeping this on the Wiki might work
> >>> better.
> >> I attached a diff to the issue making a start along the lines above.
> >> Once that's committed, I'll carry on and do some more.
> >>
> >>> Btw., I should mention that during the restructuring of the site
> >>> I think it's important to preserve all existing links and ideally
> >>> also major anchors so we don't break links pointing to our site.
> >> If I do break any, I'll be sure to recheck and change them back where
> >> possible.
> >>
> >> Incidently, I'll try and tackle the converting of the Class Reference
> >> and User Guides last - there is a technique described at [1] , but lets
> >> get everything else sorted first and happy, then I'll look at them.
> >>
> >> [1] -
> >> http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
> >> source.html#cust
> >> om
> >>
> >>
> >>
> >>> Martin
> >>>
> >>>>> 3. Where's the logo? :)
> >>>> I'll fix that.
> >> fixed.
> >>
> >> Gav...
> >>
> >>
> >>>> Gav...
> >>>>
> >>>>> Brad.
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> >>>>>> Sent: Friday, February 01, 2008 1:25 AM
> >>>>>> To: dev@stdcxx.apache.org
> >>>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> >>>>>>
> >>>>>> G'Day,
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> >>>>>> Martin Sebor
> >>>>>>> Sent: Friday, 1 February 2008 3:00 PM
> >>>>>>> To: dev@stdcxx.apache.org
> >>>>>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> >>>>>>>
> >>>>>>> Gav... wrote:
> >>>>>>>> Hi Martin,
> >>>>>>>>
> >>>>>>>> Let me know what info you need from me next.
> >>>>>>>> Once the source files I sent are in svn, then I'll be
> >>>>>> able to patch
> >>>>>>>> properly against that.
> >>>>>>> It looks quite good, thanks! I published it in my home directory
> >>>>>>> to get some feedback from others:
> >>>>>>>
> >>>>>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> >>>>>> As initial information for others, the look of this site is the
> >>>>>> standard issue 'forrest pelt theme' and if so wish, can be changed
> >>>>>> to have more unique feel to it. This can wait I think until the
> >>>>>> site is live and populated with docs.
> >>>>>>
> >>>>>>> Btw., it looks like a couple of typos snuck into index.xml and
> >>>>>>> bugs.xml. I corrected them to get forrest to generate the static
> >>>>>>> site (otherwise it fails)...
> >>>>>> Damn, sorry, I tested using 'forrest run' which ensures the
> >>>>>> site is mostly
> >>>>>> fine and working - but does not scrutinise the xdocs for
> >>>>>> validity against
> >>>>>> the DTD. Only when a 'forrest site' or 'forrest
> >>>>>> validate-xdocs' is run do
> >>>>>> the files get checked against the DTD.
> >>>>>>
> >>>>>>> ... but I still get the error below at the
> >>>>>>> end. It looks like a link is bad or something.
> >>>>>>>
> >>>>>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> >>>>>>> X [0] favicon.ico BROKEN: No
> >>>>>>> pipeline matched request: favicon.ico
> >>>>>>> at <map:mount> -
> >>>>>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> >>>>>>> ...
> >>>>>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
> >> 42
> >>>>>>> Java Result: 1
> >>>>>>>
> >>>>>>> Copying broken links file to site root.
> >>>>>>>
> >>>>>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> >>>>>>>
> >>>>>>> BUILD FAILED
> >>>>>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> >>>>>>> building site.
> >>>>>>>
> >>>>>>> There appears to be a problem with your site build.
> >>>>>> Easy one and my bad again. Automatically a favicon.ico is
> >>>>>> associated with
> >>>>>> the site and is in fact copied there when doing a 'forrest
> >>>>>> seed-sample'.
> >>>>>> As you found out though this produces many un-needed sample
> >>>>>> files. So I
> >>>>>> created the initial layout with a 'forrest seed-basic' which gives
> >> you
> >>>>>> a site structure but no files and in this case no favicon either.
> >>>>>>
> >>>>>> So the cure is to stick a favicon.ico directly into the xdocs
> >> folder.
> >>>>>> The site will then build successfully.
> >>>>>>
> >>>>>>> The two typos are: a missing underscore in the section id
> >>>>>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> >>>>>>> gives rather cryptic errors for them.
> >>>>>> The error messages were mainly to do with why they did not
> >>>>>> conform with the
> >>>>>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> >>>>>> and points out
> >>>>>> that only <li> can go inside.
> >>>>>>
> >>>>>> Most of the time, we will use Forrests v2.0 DTD -
> >>>>>>
> >>>>>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> >>>>>>
> >>>>>> (it is working towards being more xhtml2 compliant)
> >>>>>>
> >>>>>>> So sounds like the next step is to commit the prototype into svn
> >>>>>>> and set up a cron job to get it periodically published into some
> >>>>>>> sandbox (such as my home directory) so we can work on the tables
> >>>>>>> etc. Is that how you'd like to proceed?
> >>>>>> Yep, fine by me, at least I'll be able to be useful with patches
> >> then.
> >>>>>> Once your happy with stability, completeness and the
> >>>>>> forrestbot publishing
> >>>>>> is working well, then it can be moved when your happy.
> >>>>>>
> >>>>>>> I'm also curious if you have a suggestion for our documentation.
> >>>>>>> Would it make sense to try to convert it as well or might some
> >>>>>>> other solution be more appropriate?
> >>>>>> I have referred this to the Forrest dev list. It should not
> >>>>>> be a problem
> >>>>>> in principle, convert the .html files into xdoc xml and then
> >>>>>> back into .html
> >>>>>> integrated into the rest of the generated site. Hopefully the
> >> initial
> >>>>>> conversion to xdoc can be automated. Once in xdoc xml format
> >>>>>> then they can
> >>>>>> be placed appropriately, added to the site.xml and tabs.xml
> >>>>>> files and from
> >>>>>> then on be part of the site proper.
> >>>>>>
> >>>>>>>> I notice Jira replies are set to issues@, is there a Jira
> >>>>>> ticket filed
> >>>>>>> to
> >>>>>>>> change this to dev@.
> >>>>>>> Not yet. I was hoping to get to it this week but lately time has
> >>>>>>> a habit of getting away from me... You don't happen to know where
> >>>>>>> to change this, do you?
> >>>>>> I don't have the access to do it, I've asked on #infra and
> >>>>>> will let you know
> >>>>>> if someone does it. Otherwise you need to send a mail to
> >>>>>> apmail@ and file a
> >>>>>> Jira Issue on infra for it to be done .
> >>>>>>
> >>>>>> (http://apache.org/dev/reporting-issues.html#mail-config)
> >>>>>>
> >>>>>>
> >>>>>> Gav...
> >>>>>>
> >>>>>>> Martin
> >>>>>>>
> >>>>>>>> Gav...
> >>>>>>>>
> >>>>>>>> <quote who="Martin Sebor (JIRA)">
> >>>>>>>>> [
> >>>>>>>>> https://issues.apache.org/jira/browse/STDCXX-
> >>>>>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> >> tabpanel
> >>>>>>>>> ]
> >>>>>>>>>
> >>>>>>>>> Martin Sebor reassigned STDCXX-686:
> >>>>>>>>> -----------------------------------
> >>>>>>>>>
> >>>>>>>>> Assignee: Martin Sebor
> >>>>>>>>>
> >>>>>>>>>> redesign web site
> >>>>>>>>>> -----------------
> >>>>>>>>>>
> >>>>>>>>>> Key: STDCXX-686
> >>>>>>>>>> URL:
> >>>>>> https://issues.apache.org/jira/browse/STDCXX-686
> >>>>>>>>>> Project: C++ Standard Library
> >>>>>>>>>> Issue Type: Improvement
> >>>>>>>>>> Components: Web
> >>>>>>>>>> Reporter: Martin Sebor
> >>>>>>>>>> Assignee: Martin Sebor
> >>>>>>>>>> Attachments: Copy of stdcxx.zip
> >>>>>>>>>>
> >>>>>>>>>> Original Estimate: 16h
> >>>>>>>>>> Remaining Estimate: 16h
> >>>>>>>>>>
> >>>>>>>>>> The current web site is a bunch of static HTML pages
> >>>>>> with a lot of
> >>>>>>>>>> difficult-to-maintain formatting cruft copied from
> >>>>>> pages of another
> >>>>>>>>>> incubator project. We should look into generating the site from
> >>>>>>>>>> easier-to-maintain "sources" using a tool like Apache
> >>>>>> Forrest or some
> >>>>>>>>>> such.
> >>>>>>>>> --
> >>>>>>>>> This message is automatically generated by JIRA.
> >>>>>>>>> -
> >>>>>>>>> You can reply to this email to add a comment to the issue
> online.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> 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
> >>>>>
> >>>>> --
> >>>>> 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
> >>>
> >>>
> >>> --
> >>> Internal Virus Database is out-of-date.
> >>> Checked by AVG Free Edition.
> >>> Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
> >> 1/12/2008
> >>> 2:04 PM
> >>
> >> --
> >> No virus found in this incoming message.
> >> Checked by AVG.
> >> Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
> 3/10/2008
> >> 11:07 AM
> >
> >
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.12 - Release Date: 8/3/2008 12:00
> AM
Re: Website Layout
Posted by Martin Sebor <ms...@gmail.com>.
Gav.... wrote:
> Hi Guys, back again,
>
> It's been a while since March, moving to the other side of the continent and
> other stuff etc..
>
> Anyway, I did some more to the Forrest site, for me to work a bit more
> freely I have put up a version at :-
>
> http://people.apache.org/~gmcdonald/stdcxx/index.html
This looks fantastic!
>
> I realise I may be a bit behind as some content will have changed, but if
> your happy with the layout etc, we can move on - that is of course you
> haven't decided on another route yet.
Other than a few minor updates I don't think we've made any
significant changes.
>
> I'll continue on and get caught up on doc site content changes, then start
> activating links etc.
Let me know if there's I/we can do to help.
Martin
>
> Gav...
>
>
>> -----Original Message-----
>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>> Sent: Tuesday, 11 March 2008 11:25 PM
>> To: dev@stdcxx.apache.org
>> Subject: RE: Website Layout
>>
>>
>>
>>> -----Original Message-----
>>> From: Martin Sebor [mailto:sebor@roguewave.com]
>>> Sent: Wednesday, 6 February 2008 7:04 AM
>>> To: dev@stdcxx.apache.org
>>> Subject: Re: Website Layout
>>>
>>> Gav.... wrote:
>>>> Hi Eric/All,
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
>>>>> Sent: Saturday, 2 February 2008 2:17 AM
>>>>> To: dev@stdcxx.apache.org
>>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>
>>>>>
>>>>> I like it. It follows the style of the current site so it's not
>>>>> too disruptive.
>>>>>
>>>>> Couple minor suggestions:
>>>>>
>>>>> 1. Move the Documentation nav up to a tab next to the Download tab.
>>>> Yes, that can be done, no problem, I'll do that in my next patch if
>>>> no objections.
>>> Personally, I would probably try to tackle the migration of the
>>> site as it is to Forrest first so we can publish it as our default,
>>> and then work on improving the layout next. I don't know if this
>>> approach makes sense or it's less effort to restructure it at the
>>> same time.
>>>
>>>>> 2. Move all links at the top of the home page to the nav bar,
>>>>> and subdivide them into groups (e.g. General [Objectives, About],
>>>>> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
>>>>> License, Platforms, References]
>>>> Those links are auto generated from <sections> in the source and are
>>>> internal links to the relative section on that page. Dividing them
>>>> would mean creating new pages and moving content out of the home page
>>>> onto the new ones. This is no problem either, but its not my site, so
>>>> do you guys want to discuss the layout how you want it and I'll make
>>>> the changes ?
>>> Sure. We don't have any design document or a rationale for the
>>> current site but it makes sense to discuss it before Gav puts
>>> in a whole lot of time into it. Btw., how difficult is it to
>>> restructure the site in Forrest if we change our mind? :)
>> It's fairly easy, so no problem.
>>
>>> Here are some of my random thoughts on the subject...
>>>
>>> As far as tabs and menus go, I'd be inclined to follow the layout
>>> used by other projects. From what I see on the Forrest site, for
>>> instance, every tab is a menu with each menu item pointing to
>>> a separate page (although the Versioned Docs and Plugins tabs
>>> look like they're messed up). So if we expect each of Downloads
>>> and Documentation to break down into a number of menu items with
>>> a page for each, making them tabs sounds dandy.
>>>
>>> The one page I think is already way too long and that we should
>>> probably break up into a number of smaller ones is index.html
>>> (is there any kind of rule of thumb on how long the ideal page
>>> should be?) We should probably split it up into an About page
>>> (what is stdcxx), another one just for News, an another for
>>> our "mission statement" (current Objectives). I can see us also
>>> wanting to have a separate page or even a tab for Developers (as
>>> on the Forrest page), and split that one into a page (or more)
>>> for each of Committers, Contributors, and Users. And maybe also
>>> PMC. Then there is Communication and Mailing Lists which could
>>> be on the same page. I don't know how useful the References
>>> section is. Seems like keeping this on the Wiki might work
>>> better.
>> I attached a diff to the issue making a start along the lines above.
>> Once that's committed, I'll carry on and do some more.
>>
>>> Btw., I should mention that during the restructuring of the site
>>> I think it's important to preserve all existing links and ideally
>>> also major anchors so we don't break links pointing to our site.
>> If I do break any, I'll be sure to recheck and change them back where
>> possible.
>>
>> Incidently, I'll try and tackle the converting of the Class Reference
>> and User Guides last - there is a technique described at [1] , but lets
>> get everything else sorted first and happy, then I'll look at them.
>>
>> [1] -
>> http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
>> source.html#cust
>> om
>>
>>
>>
>>> Martin
>>>
>>>>> 3. Where's the logo? :)
>>>> I'll fix that.
>> fixed.
>>
>> Gav...
>>
>>
>>>> Gav...
>>>>
>>>>> Brad.
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>>>>>> Sent: Friday, February 01, 2008 1:25 AM
>>>>>> To: dev@stdcxx.apache.org
>>>>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>>
>>>>>> G'Day,
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
>>>>>> Martin Sebor
>>>>>>> Sent: Friday, 1 February 2008 3:00 PM
>>>>>>> To: dev@stdcxx.apache.org
>>>>>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
>>>>>>>
>>>>>>> Gav... wrote:
>>>>>>>> Hi Martin,
>>>>>>>>
>>>>>>>> Let me know what info you need from me next.
>>>>>>>> Once the source files I sent are in svn, then I'll be
>>>>>> able to patch
>>>>>>>> properly against that.
>>>>>>> It looks quite good, thanks! I published it in my home directory
>>>>>>> to get some feedback from others:
>>>>>>>
>>>>>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
>>>>>> As initial information for others, the look of this site is the
>>>>>> standard issue 'forrest pelt theme' and if so wish, can be changed
>>>>>> to have more unique feel to it. This can wait I think until the
>>>>>> site is live and populated with docs.
>>>>>>
>>>>>>> Btw., it looks like a couple of typos snuck into index.xml and
>>>>>>> bugs.xml. I corrected them to get forrest to generate the static
>>>>>>> site (otherwise it fails)...
>>>>>> Damn, sorry, I tested using 'forrest run' which ensures the
>>>>>> site is mostly
>>>>>> fine and working - but does not scrutinise the xdocs for
>>>>>> validity against
>>>>>> the DTD. Only when a 'forrest site' or 'forrest
>>>>>> validate-xdocs' is run do
>>>>>> the files get checked against the DTD.
>>>>>>
>>>>>>> ... but I still get the error below at the
>>>>>>> end. It looks like a link is bad or something.
>>>>>>>
>>>>>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
>>>>>>> X [0] favicon.ico BROKEN: No
>>>>>>> pipeline matched request: favicon.ico
>>>>>>> at <map:mount> -
>>>>>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
>>>>>>> ...
>>>>>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
>> 42
>>>>>>> Java Result: 1
>>>>>>>
>>>>>>> Copying broken links file to site root.
>>>>>>>
>>>>>>> Copying 1 file to /build/sebor/tmp/site2/build/site
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
>>>>>>> building site.
>>>>>>>
>>>>>>> There appears to be a problem with your site build.
>>>>>> Easy one and my bad again. Automatically a favicon.ico is
>>>>>> associated with
>>>>>> the site and is in fact copied there when doing a 'forrest
>>>>>> seed-sample'.
>>>>>> As you found out though this produces many un-needed sample
>>>>>> files. So I
>>>>>> created the initial layout with a 'forrest seed-basic' which gives
>> you
>>>>>> a site structure but no files and in this case no favicon either.
>>>>>>
>>>>>> So the cure is to stick a favicon.ico directly into the xdocs
>> folder.
>>>>>> The site will then build successfully.
>>>>>>
>>>>>>> The two typos are: a missing underscore in the section id
>>>>>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
>>>>>>> gives rather cryptic errors for them.
>>>>>> The error messages were mainly to do with why they did not
>>>>>> conform with the
>>>>>> DTD - i.e the # symbol is not allowed directly beneath <ol>
>>>>>> and points out
>>>>>> that only <li> can go inside.
>>>>>>
>>>>>> Most of the time, we will use Forrests v2.0 DTD -
>>>>>>
>>>>>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
>>>>>>
>>>>>> (it is working towards being more xhtml2 compliant)
>>>>>>
>>>>>>> So sounds like the next step is to commit the prototype into svn
>>>>>>> and set up a cron job to get it periodically published into some
>>>>>>> sandbox (such as my home directory) so we can work on the tables
>>>>>>> etc. Is that how you'd like to proceed?
>>>>>> Yep, fine by me, at least I'll be able to be useful with patches
>> then.
>>>>>> Once your happy with stability, completeness and the
>>>>>> forrestbot publishing
>>>>>> is working well, then it can be moved when your happy.
>>>>>>
>>>>>>> I'm also curious if you have a suggestion for our documentation.
>>>>>>> Would it make sense to try to convert it as well or might some
>>>>>>> other solution be more appropriate?
>>>>>> I have referred this to the Forrest dev list. It should not
>>>>>> be a problem
>>>>>> in principle, convert the .html files into xdoc xml and then
>>>>>> back into .html
>>>>>> integrated into the rest of the generated site. Hopefully the
>> initial
>>>>>> conversion to xdoc can be automated. Once in xdoc xml format
>>>>>> then they can
>>>>>> be placed appropriately, added to the site.xml and tabs.xml
>>>>>> files and from
>>>>>> then on be part of the site proper.
>>>>>>
>>>>>>>> I notice Jira replies are set to issues@, is there a Jira
>>>>>> ticket filed
>>>>>>> to
>>>>>>>> change this to dev@.
>>>>>>> Not yet. I was hoping to get to it this week but lately time has
>>>>>>> a habit of getting away from me... You don't happen to know where
>>>>>>> to change this, do you?
>>>>>> I don't have the access to do it, I've asked on #infra and
>>>>>> will let you know
>>>>>> if someone does it. Otherwise you need to send a mail to
>>>>>> apmail@ and file a
>>>>>> Jira Issue on infra for it to be done .
>>>>>>
>>>>>> (http://apache.org/dev/reporting-issues.html#mail-config)
>>>>>>
>>>>>>
>>>>>> Gav...
>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>>> Gav...
>>>>>>>>
>>>>>>>> <quote who="Martin Sebor (JIRA)">
>>>>>>>>> [
>>>>>>>>> https://issues.apache.org/jira/browse/STDCXX-
>>>>>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
>> tabpanel
>>>>>>>>> ]
>>>>>>>>>
>>>>>>>>> Martin Sebor reassigned STDCXX-686:
>>>>>>>>> -----------------------------------
>>>>>>>>>
>>>>>>>>> Assignee: Martin Sebor
>>>>>>>>>
>>>>>>>>>> redesign web site
>>>>>>>>>> -----------------
>>>>>>>>>>
>>>>>>>>>> Key: STDCXX-686
>>>>>>>>>> URL:
>>>>>> https://issues.apache.org/jira/browse/STDCXX-686
>>>>>>>>>> Project: C++ Standard Library
>>>>>>>>>> Issue Type: Improvement
>>>>>>>>>> Components: Web
>>>>>>>>>> Reporter: Martin Sebor
>>>>>>>>>> Assignee: Martin Sebor
>>>>>>>>>> Attachments: Copy of stdcxx.zip
>>>>>>>>>>
>>>>>>>>>> Original Estimate: 16h
>>>>>>>>>> Remaining Estimate: 16h
>>>>>>>>>>
>>>>>>>>>> The current web site is a bunch of static HTML pages
>>>>>> with a lot of
>>>>>>>>>> difficult-to-maintain formatting cruft copied from
>>>>>> pages of another
>>>>>>>>>> incubator project. We should look into generating the site from
>>>>>>>>>> easier-to-maintain "sources" using a tool like Apache
>>>>>> Forrest or some
>>>>>>>>>> such.
>>>>>>>>> --
>>>>>>>>> This message is automatically generated by JIRA.
>>>>>>>>> -
>>>>>>>>> You can reply to this email to add a comment to the issue online.
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>
>>>>> --
>>>>> 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
>>>
>>>
>>> --
>>> Internal Virus Database is out-of-date.
>>> Checked by AVG Free Edition.
>>> Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
>> 1/12/2008
>>> 2:04 PM
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG.
>> Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date: 3/10/2008
>> 11:07 AM
>
>
RE: Website Layout
Posted by "Gav...." <br...@brightontown.com.au>.
Hi Guys, back again,
It's been a while since March, moving to the other side of the continent and
other stuff etc..
Anyway, I did some more to the Forrest site, for me to work a bit more
freely I have put up a version at :-
http://people.apache.org/~gmcdonald/stdcxx/index.html
I realise I may be a bit behind as some content will have changed, but if
your happy with the layout etc, we can move on - that is of course you
haven't decided on another route yet.
I'll continue on and get caught up on doc site content changes, then start
activating links etc.
Gav...
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Tuesday, 11 March 2008 11:25 PM
> To: dev@stdcxx.apache.org
> Subject: RE: Website Layout
>
>
>
> > -----Original Message-----
> > From: Martin Sebor [mailto:sebor@roguewave.com]
> > Sent: Wednesday, 6 February 2008 7:04 AM
> > To: dev@stdcxx.apache.org
> > Subject: Re: Website Layout
> >
> > Gav.... wrote:
> > > Hi Eric/All,
> > >
> > >
> > >> -----Original Message-----
> > >> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> > >> Sent: Saturday, 2 February 2008 2:17 AM
> > >> To: dev@stdcxx.apache.org
> > >> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > >>
> > >>
> > >> I like it. It follows the style of the current site so it's not
> > >> too disruptive.
> > >>
> > >> Couple minor suggestions:
> > >>
> > >> 1. Move the Documentation nav up to a tab next to the Download tab.
> > >
> > > Yes, that can be done, no problem, I'll do that in my next patch if
> > > no objections.
> >
> > Personally, I would probably try to tackle the migration of the
> > site as it is to Forrest first so we can publish it as our default,
> > and then work on improving the layout next. I don't know if this
> > approach makes sense or it's less effort to restructure it at the
> > same time.
> >
> > >
> > >> 2. Move all links at the top of the home page to the nav bar,
> > >> and subdivide them into groups (e.g. General [Objectives, About],
> > >> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> > >> License, Platforms, References]
> > >
> > > Those links are auto generated from <sections> in the source and are
> > > internal links to the relative section on that page. Dividing them
> > > would mean creating new pages and moving content out of the home page
> > > onto the new ones. This is no problem either, but its not my site, so
> > > do you guys want to discuss the layout how you want it and I'll make
> > > the changes ?
> >
> > Sure. We don't have any design document or a rationale for the
> > current site but it makes sense to discuss it before Gav puts
> > in a whole lot of time into it. Btw., how difficult is it to
> > restructure the site in Forrest if we change our mind? :)
>
> It's fairly easy, so no problem.
>
> >
> > Here are some of my random thoughts on the subject...
> >
> > As far as tabs and menus go, I'd be inclined to follow the layout
> > used by other projects. From what I see on the Forrest site, for
> > instance, every tab is a menu with each menu item pointing to
> > a separate page (although the Versioned Docs and Plugins tabs
> > look like they're messed up). So if we expect each of Downloads
> > and Documentation to break down into a number of menu items with
> > a page for each, making them tabs sounds dandy.
> >
> > The one page I think is already way too long and that we should
> > probably break up into a number of smaller ones is index.html
> > (is there any kind of rule of thumb on how long the ideal page
> > should be?) We should probably split it up into an About page
> > (what is stdcxx), another one just for News, an another for
> > our "mission statement" (current Objectives). I can see us also
> > wanting to have a separate page or even a tab for Developers (as
> > on the Forrest page), and split that one into a page (or more)
> > for each of Committers, Contributors, and Users. And maybe also
> > PMC. Then there is Communication and Mailing Lists which could
> > be on the same page. I don't know how useful the References
> > section is. Seems like keeping this on the Wiki might work
> > better.
>
> I attached a diff to the issue making a start along the lines above.
> Once that's committed, I'll carry on and do some more.
>
> >
> > Btw., I should mention that during the restructuring of the site
> > I think it's important to preserve all existing links and ideally
> > also major anchors so we don't break links pointing to our site.
>
> If I do break any, I'll be sure to recheck and change them back where
> possible.
>
> Incidently, I'll try and tackle the converting of the Class Reference
> and User Guides last - there is a technique described at [1] , but lets
> get everything else sorted first and happy, then I'll look at them.
>
> [1] -
> http://forrest.apache.org/docs_0_90/howto/howto-custom-html-
> source.html#cust
> om
>
>
>
> >
> > Martin
> >
> > >
> > >> 3. Where's the logo? :)
> > >
> > > I'll fix that.
>
> fixed.
>
> Gav...
>
>
> > >
> > > Gav...
> > >
> > >> Brad.
> > >>
> > >>> -----Original Message-----
> > >>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > >>> Sent: Friday, February 01, 2008 1:25 AM
> > >>> To: dev@stdcxx.apache.org
> > >>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> > >>>
> > >>> G'Day,
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> > >>> Martin Sebor
> > >>>> Sent: Friday, 1 February 2008 3:00 PM
> > >>>> To: dev@stdcxx.apache.org
> > >>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> > >>>>
> > >>>> Gav... wrote:
> > >>>>> Hi Martin,
> > >>>>>
> > >>>>> Let me know what info you need from me next.
> > >>>>> Once the source files I sent are in svn, then I'll be
> > >>> able to patch
> > >>>>> properly against that.
> > >>>> It looks quite good, thanks! I published it in my home directory
> > >>>> to get some feedback from others:
> > >>>>
> > >>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> > >>> As initial information for others, the look of this site is the
> > >>> standard issue 'forrest pelt theme' and if so wish, can be changed
> > >>> to have more unique feel to it. This can wait I think until the
> > >>> site is live and populated with docs.
> > >>>
> > >>>> Btw., it looks like a couple of typos snuck into index.xml and
> > >>>> bugs.xml. I corrected them to get forrest to generate the static
> > >>>> site (otherwise it fails)...
> > >>> Damn, sorry, I tested using 'forrest run' which ensures the
> > >>> site is mostly
> > >>> fine and working - but does not scrutinise the xdocs for
> > >>> validity against
> > >>> the DTD. Only when a 'forrest site' or 'forrest
> > >>> validate-xdocs' is run do
> > >>> the files get checked against the DTD.
> > >>>
> > >>>> ... but I still get the error below at the
> > >>>> end. It looks like a link is bad or something.
> > >>>>
> > >>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > >>>> X [0] favicon.ico BROKEN: No
> > >>>> pipeline matched request: favicon.ico
> > >>>> at <map:mount> -
> > >>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > >>>> ...
> > >>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages:
> 42
> > >>>> Java Result: 1
> > >>>>
> > >>>> Copying broken links file to site root.
> > >>>>
> > >>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> > >>>>
> > >>>> BUILD FAILED
> > >>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> > >>>> building site.
> > >>>>
> > >>>> There appears to be a problem with your site build.
> > >>> Easy one and my bad again. Automatically a favicon.ico is
> > >>> associated with
> > >>> the site and is in fact copied there when doing a 'forrest
> > >>> seed-sample'.
> > >>> As you found out though this produces many un-needed sample
> > >>> files. So I
> > >>> created the initial layout with a 'forrest seed-basic' which gives
> you
> > >>> a site structure but no files and in this case no favicon either.
> > >>>
> > >>> So the cure is to stick a favicon.ico directly into the xdocs
> folder.
> > >>> The site will then build successfully.
> > >>>
> > >>>> The two typos are: a missing underscore in the section id
> > >>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > >>>> gives rather cryptic errors for them.
> > >>> The error messages were mainly to do with why they did not
> > >>> conform with the
> > >>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> > >>> and points out
> > >>> that only <li> can go inside.
> > >>>
> > >>> Most of the time, we will use Forrests v2.0 DTD -
> > >>>
> > >>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> > >>>
> > >>> (it is working towards being more xhtml2 compliant)
> > >>>
> > >>>> So sounds like the next step is to commit the prototype into svn
> > >>>> and set up a cron job to get it periodically published into some
> > >>>> sandbox (such as my home directory) so we can work on the tables
> > >>>> etc. Is that how you'd like to proceed?
> > >>> Yep, fine by me, at least I'll be able to be useful with patches
> then.
> > >>> Once your happy with stability, completeness and the
> > >>> forrestbot publishing
> > >>> is working well, then it can be moved when your happy.
> > >>>
> > >>>> I'm also curious if you have a suggestion for our documentation.
> > >>>> Would it make sense to try to convert it as well or might some
> > >>>> other solution be more appropriate?
> > >>> I have referred this to the Forrest dev list. It should not
> > >>> be a problem
> > >>> in principle, convert the .html files into xdoc xml and then
> > >>> back into .html
> > >>> integrated into the rest of the generated site. Hopefully the
> initial
> > >>> conversion to xdoc can be automated. Once in xdoc xml format
> > >>> then they can
> > >>> be placed appropriately, added to the site.xml and tabs.xml
> > >>> files and from
> > >>> then on be part of the site proper.
> > >>>
> > >>>>> I notice Jira replies are set to issues@, is there a Jira
> > >>> ticket filed
> > >>>> to
> > >>>>> change this to dev@.
> > >>>> Not yet. I was hoping to get to it this week but lately time has
> > >>>> a habit of getting away from me... You don't happen to know where
> > >>>> to change this, do you?
> > >>> I don't have the access to do it, I've asked on #infra and
> > >>> will let you know
> > >>> if someone does it. Otherwise you need to send a mail to
> > >>> apmail@ and file a
> > >>> Jira Issue on infra for it to be done .
> > >>>
> > >>> (http://apache.org/dev/reporting-issues.html#mail-config)
> > >>>
> > >>>
> > >>> Gav...
> > >>>
> > >>>> Martin
> > >>>>
> > >>>>> Gav...
> > >>>>>
> > >>>>> <quote who="Martin Sebor (JIRA)">
> > >>>>>> [
> > >>>>>> https://issues.apache.org/jira/browse/STDCXX-
> > >>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-
> tabpanel
> > >>>>>> ]
> > >>>>>>
> > >>>>>> Martin Sebor reassigned STDCXX-686:
> > >>>>>> -----------------------------------
> > >>>>>>
> > >>>>>> Assignee: Martin Sebor
> > >>>>>>
> > >>>>>>> redesign web site
> > >>>>>>> -----------------
> > >>>>>>>
> > >>>>>>> Key: STDCXX-686
> > >>>>>>> URL:
> > >>> https://issues.apache.org/jira/browse/STDCXX-686
> > >>>>>>> Project: C++ Standard Library
> > >>>>>>> Issue Type: Improvement
> > >>>>>>> Components: Web
> > >>>>>>> Reporter: Martin Sebor
> > >>>>>>> Assignee: Martin Sebor
> > >>>>>>> Attachments: Copy of stdcxx.zip
> > >>>>>>>
> > >>>>>>> Original Estimate: 16h
> > >>>>>>> Remaining Estimate: 16h
> > >>>>>>>
> > >>>>>>> The current web site is a bunch of static HTML pages
> > >>> with a lot of
> > >>>>>>> difficult-to-maintain formatting cruft copied from
> > >>> pages of another
> > >>>>>>> incubator project. We should look into generating the site from
> > >>>>>>> easier-to-maintain "sources" using a tool like Apache
> > >>> Forrest or some
> > >>>>>>> such.
> > >>>>>> --
> > >>>>>> This message is automatically generated by JIRA.
> > >>>>>> -
> > >>>>>> You can reply to this email to add a comment to the issue online.
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> 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
> > >>
> > >>
> > >> --
> > >> 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
> >
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date:
> 1/12/2008
> > 2:04 PM
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date: 3/10/2008
> 11:07 AM
RE: Website Layout
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Wednesday, 6 February 2008 7:04 AM
> To: dev@stdcxx.apache.org
> Subject: Re: Website Layout
>
> Gav.... wrote:
> > Hi Eric/All,
> >
> >
> >> -----Original Message-----
> >> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> >> Sent: Saturday, 2 February 2008 2:17 AM
> >> To: dev@stdcxx.apache.org
> >> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> >>
> >>
> >> I like it. It follows the style of the current site so it's not
> >> too disruptive.
> >>
> >> Couple minor suggestions:
> >>
> >> 1. Move the Documentation nav up to a tab next to the Download tab.
> >
> > Yes, that can be done, no problem, I'll do that in my next patch if
> > no objections.
>
> Personally, I would probably try to tackle the migration of the
> site as it is to Forrest first so we can publish it as our default,
> and then work on improving the layout next. I don't know if this
> approach makes sense or it's less effort to restructure it at the
> same time.
>
> >
> >> 2. Move all links at the top of the home page to the nav bar,
> >> and subdivide them into groups (e.g. General [Objectives, About],
> >> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> >> License, Platforms, References]
> >
> > Those links are auto generated from <sections> in the source and are
> > internal links to the relative section on that page. Dividing them
> > would mean creating new pages and moving content out of the home page
> > onto the new ones. This is no problem either, but its not my site, so
> > do you guys want to discuss the layout how you want it and I'll make
> > the changes ?
>
> Sure. We don't have any design document or a rationale for the
> current site but it makes sense to discuss it before Gav puts
> in a whole lot of time into it. Btw., how difficult is it to
> restructure the site in Forrest if we change our mind? :)
It's fairly easy, so no problem.
>
> Here are some of my random thoughts on the subject...
>
> As far as tabs and menus go, I'd be inclined to follow the layout
> used by other projects. From what I see on the Forrest site, for
> instance, every tab is a menu with each menu item pointing to
> a separate page (although the Versioned Docs and Plugins tabs
> look like they're messed up). So if we expect each of Downloads
> and Documentation to break down into a number of menu items with
> a page for each, making them tabs sounds dandy.
>
> The one page I think is already way too long and that we should
> probably break up into a number of smaller ones is index.html
> (is there any kind of rule of thumb on how long the ideal page
> should be?) We should probably split it up into an About page
> (what is stdcxx), another one just for News, an another for
> our "mission statement" (current Objectives). I can see us also
> wanting to have a separate page or even a tab for Developers (as
> on the Forrest page), and split that one into a page (or more)
> for each of Committers, Contributors, and Users. And maybe also
> PMC. Then there is Communication and Mailing Lists which could
> be on the same page. I don't know how useful the References
> section is. Seems like keeping this on the Wiki might work
> better.
I attached a diff to the issue making a start along the lines above.
Once that's committed, I'll carry on and do some more.
>
> Btw., I should mention that during the restructuring of the site
> I think it's important to preserve all existing links and ideally
> also major anchors so we don't break links pointing to our site.
If I do break any, I'll be sure to recheck and change them back where
possible.
Incidently, I'll try and tackle the converting of the Class Reference
and User Guides last - there is a technique described at [1] , but lets
get everything else sorted first and happy, then I'll look at them.
[1] -
http://forrest.apache.org/docs_0_90/howto/howto-custom-html-source.html#cust
om
>
> Martin
>
> >
> >> 3. Where's the logo? :)
> >
> > I'll fix that.
fixed.
Gav...
> >
> > Gav...
> >
> >> Brad.
> >>
> >>> -----Original Message-----
> >>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> >>> Sent: Friday, February 01, 2008 1:25 AM
> >>> To: dev@stdcxx.apache.org
> >>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> >>>
> >>> G'Day,
> >>>
> >>>> -----Original Message-----
> >>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> >>> Martin Sebor
> >>>> Sent: Friday, 1 February 2008 3:00 PM
> >>>> To: dev@stdcxx.apache.org
> >>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> >>>>
> >>>> Gav... wrote:
> >>>>> Hi Martin,
> >>>>>
> >>>>> Let me know what info you need from me next.
> >>>>> Once the source files I sent are in svn, then I'll be
> >>> able to patch
> >>>>> properly against that.
> >>>> It looks quite good, thanks! I published it in my home directory
> >>>> to get some feedback from others:
> >>>>
> >>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
> >>> As initial information for others, the look of this site is the
> >>> standard issue 'forrest pelt theme' and if so wish, can be changed
> >>> to have more unique feel to it. This can wait I think until the
> >>> site is live and populated with docs.
> >>>
> >>>> Btw., it looks like a couple of typos snuck into index.xml and
> >>>> bugs.xml. I corrected them to get forrest to generate the static
> >>>> site (otherwise it fails)...
> >>> Damn, sorry, I tested using 'forrest run' which ensures the
> >>> site is mostly
> >>> fine and working - but does not scrutinise the xdocs for
> >>> validity against
> >>> the DTD. Only when a 'forrest site' or 'forrest
> >>> validate-xdocs' is run do
> >>> the files get checked against the DTD.
> >>>
> >>>> ... but I still get the error below at the
> >>>> end. It looks like a link is bad or something.
> >>>>
> >>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> >>>> X [0] favicon.ico BROKEN: No
> >>>> pipeline matched request: favicon.ico
> >>>> at <map:mount> -
> >>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> >>>> ...
> >>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
> >>>> Java Result: 1
> >>>>
> >>>> Copying broken links file to site root.
> >>>>
> >>>> Copying 1 file to /build/sebor/tmp/site2/build/site
> >>>>
> >>>> BUILD FAILED
> >>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> >>>> building site.
> >>>>
> >>>> There appears to be a problem with your site build.
> >>> Easy one and my bad again. Automatically a favicon.ico is
> >>> associated with
> >>> the site and is in fact copied there when doing a 'forrest
> >>> seed-sample'.
> >>> As you found out though this produces many un-needed sample
> >>> files. So I
> >>> created the initial layout with a 'forrest seed-basic' which gives you
> >>> a site structure but no files and in this case no favicon either.
> >>>
> >>> So the cure is to stick a favicon.ico directly into the xdocs folder.
> >>> The site will then build successfully.
> >>>
> >>>> The two typos are: a missing underscore in the section id
> >>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> >>>> gives rather cryptic errors for them.
> >>> The error messages were mainly to do with why they did not
> >>> conform with the
> >>> DTD - i.e the # symbol is not allowed directly beneath <ol>
> >>> and points out
> >>> that only <li> can go inside.
> >>>
> >>> Most of the time, we will use Forrests v2.0 DTD -
> >>>
> >>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
> >>>
> >>> (it is working towards being more xhtml2 compliant)
> >>>
> >>>> So sounds like the next step is to commit the prototype into svn
> >>>> and set up a cron job to get it periodically published into some
> >>>> sandbox (such as my home directory) so we can work on the tables
> >>>> etc. Is that how you'd like to proceed?
> >>> Yep, fine by me, at least I'll be able to be useful with patches then.
> >>> Once your happy with stability, completeness and the
> >>> forrestbot publishing
> >>> is working well, then it can be moved when your happy.
> >>>
> >>>> I'm also curious if you have a suggestion for our documentation.
> >>>> Would it make sense to try to convert it as well or might some
> >>>> other solution be more appropriate?
> >>> I have referred this to the Forrest dev list. It should not
> >>> be a problem
> >>> in principle, convert the .html files into xdoc xml and then
> >>> back into .html
> >>> integrated into the rest of the generated site. Hopefully the initial
> >>> conversion to xdoc can be automated. Once in xdoc xml format
> >>> then they can
> >>> be placed appropriately, added to the site.xml and tabs.xml
> >>> files and from
> >>> then on be part of the site proper.
> >>>
> >>>>> I notice Jira replies are set to issues@, is there a Jira
> >>> ticket filed
> >>>> to
> >>>>> change this to dev@.
> >>>> Not yet. I was hoping to get to it this week but lately time has
> >>>> a habit of getting away from me... You don't happen to know where
> >>>> to change this, do you?
> >>> I don't have the access to do it, I've asked on #infra and
> >>> will let you know
> >>> if someone does it. Otherwise you need to send a mail to
> >>> apmail@ and file a
> >>> Jira Issue on infra for it to be done .
> >>>
> >>> (http://apache.org/dev/reporting-issues.html#mail-config)
> >>>
> >>>
> >>> Gav...
> >>>
> >>>> Martin
> >>>>
> >>>>> Gav...
> >>>>>
> >>>>> <quote who="Martin Sebor (JIRA)">
> >>>>>> [
> >>>>>> https://issues.apache.org/jira/browse/STDCXX-
> >>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >>>>>> ]
> >>>>>>
> >>>>>> Martin Sebor reassigned STDCXX-686:
> >>>>>> -----------------------------------
> >>>>>>
> >>>>>> Assignee: Martin Sebor
> >>>>>>
> >>>>>>> redesign web site
> >>>>>>> -----------------
> >>>>>>>
> >>>>>>> Key: STDCXX-686
> >>>>>>> URL:
> >>> https://issues.apache.org/jira/browse/STDCXX-686
> >>>>>>> Project: C++ Standard Library
> >>>>>>> Issue Type: Improvement
> >>>>>>> Components: Web
> >>>>>>> Reporter: Martin Sebor
> >>>>>>> Assignee: Martin Sebor
> >>>>>>> Attachments: Copy of stdcxx.zip
> >>>>>>>
> >>>>>>> Original Estimate: 16h
> >>>>>>> Remaining Estimate: 16h
> >>>>>>>
> >>>>>>> The current web site is a bunch of static HTML pages
> >>> with a lot of
> >>>>>>> difficult-to-maintain formatting cruft copied from
> >>> pages of another
> >>>>>>> incubator project. We should look into generating the site from
> >>>>>>> easier-to-maintain "sources" using a tool like Apache
> >>> Forrest or some
> >>>>>>> such.
> >>>>>> --
> >>>>>> This message is automatically generated by JIRA.
> >>>>>> -
> >>>>>> You can reply to this email to add a comment to the issue online.
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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
> >>
> >>
> >> --
> >> 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
>
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.19.2/1221 - Release Date: 1/12/2008
> 2:04 PM
Re: Website Layout
Posted by Martin Sebor <se...@roguewave.com>.
Gav.... wrote:
> Hi Eric/All,
>
>
>> -----Original Message-----
>> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
>> Sent: Saturday, 2 February 2008 2:17 AM
>> To: dev@stdcxx.apache.org
>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>
>>
>> I like it. It follows the style of the current site so it's not
>> too disruptive.
>>
>> Couple minor suggestions:
>>
>> 1. Move the Documentation nav up to a tab next to the Download tab.
>
> Yes, that can be done, no problem, I'll do that in my next patch if
> no objections.
Personally, I would probably try to tackle the migration of the
site as it is to Forrest first so we can publish it as our default,
and then work on improving the layout next. I don't know if this
approach makes sense or it's less effort to restructure it at the
same time.
>
>> 2. Move all links at the top of the home page to the nav bar,
>> and subdivide them into groups (e.g. General [Objectives, About],
>> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
>> License, Platforms, References]
>
> Those links are auto generated from <sections> in the source and are
> internal links to the relative section on that page. Dividing them
> would mean creating new pages and moving content out of the home page
> onto the new ones. This is no problem either, but its not my site, so
> do you guys want to discuss the layout how you want it and I'll make
> the changes ?
Sure. We don't have any design document or a rationale for the
current site but it makes sense to discuss it before Gav puts
in a whole lot of time into it. Btw., how difficult is it to
restructure the site in Forrest if we change our mind? :)
Here are some of my random thoughts on the subject...
As far as tabs and menus go, I'd be inclined to follow the layout
used by other projects. From what I see on the Forrest site, for
instance, every tab is a menu with each menu item pointing to
a separate page (although the Versioned Docs and Plugins tabs
look like they're messed up). So if we expect each of Downloads
and Documentation to break down into a number of menu items with
a page for each, making them tabs sounds dandy.
The one page I think is already way too long and that we should
probably break up into a number of smaller ones is index.html
(is there any kind of rule of thumb on how long the ideal page
should be?) We should probably split it up into an About page
(what is stdcxx), another one just for News, an another for
our "mission statement" (current Objectives). I can see us also
wanting to have a separate page or even a tab for Developers (as
on the Forrest page), and split that one into a page (or more)
for each of Committers, Contributors, and Users. And maybe also
PMC. Then there is Communication and Mailing Lists which could
be on the same page. I don't know how useful the References
section is. Seems like keeping this on the Wiki might work
better.
Btw., I should mention that during the restructuring of the site
I think it's important to preserve all existing links and ideally
also major anchors so we don't break links pointing to our site.
Martin
>
>> 3. Where's the logo? :)
>
> I'll fix that.
>
> Gav...
>
>> Brad.
>>
>>> -----Original Message-----
>>> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
>>> Sent: Friday, February 01, 2008 1:25 AM
>>> To: dev@stdcxx.apache.org
>>> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>>>
>>> G'Day,
>>>
>>>> -----Original Message-----
>>>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
>>> Martin Sebor
>>>> Sent: Friday, 1 February 2008 3:00 PM
>>>> To: dev@stdcxx.apache.org
>>>> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
>>>>
>>>> Gav... wrote:
>>>>> Hi Martin,
>>>>>
>>>>> Let me know what info you need from me next.
>>>>> Once the source files I sent are in svn, then I'll be
>>> able to patch
>>>>> properly against that.
>>>> It looks quite good, thanks! I published it in my home directory
>>>> to get some feedback from others:
>>>>
>>>> http://people.apache.org/~sebor/stdcxx/forrest-site/
>>> As initial information for others, the look of this site is the
>>> standard issue 'forrest pelt theme' and if so wish, can be changed
>>> to have more unique feel to it. This can wait I think until the
>>> site is live and populated with docs.
>>>
>>>> Btw., it looks like a couple of typos snuck into index.xml and
>>>> bugs.xml. I corrected them to get forrest to generate the static
>>>> site (otherwise it fails)...
>>> Damn, sorry, I tested using 'forrest run' which ensures the
>>> site is mostly
>>> fine and working - but does not scrutinise the xdocs for
>>> validity against
>>> the DTD. Only when a 'forrest site' or 'forrest
>>> validate-xdocs' is run do
>>> the files get checked against the DTD.
>>>
>>>> ... but I still get the error below at the
>>>> end. It looks like a link is bad or something.
>>>>
>>>> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
>>>> X [0] favicon.ico BROKEN: No
>>>> pipeline matched request: favicon.ico
>>>> at <map:mount> -
>>>> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
>>>> ...
>>>> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
>>>> Java Result: 1
>>>>
>>>> Copying broken links file to site root.
>>>>
>>>> Copying 1 file to /build/sebor/tmp/site2/build/site
>>>>
>>>> BUILD FAILED
>>>> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
>>>> building site.
>>>>
>>>> There appears to be a problem with your site build.
>>> Easy one and my bad again. Automatically a favicon.ico is
>>> associated with
>>> the site and is in fact copied there when doing a 'forrest
>>> seed-sample'.
>>> As you found out though this produces many un-needed sample
>>> files. So I
>>> created the initial layout with a 'forrest seed-basic' which gives you
>>> a site structure but no files and in this case no favicon either.
>>>
>>> So the cure is to stick a favicon.ico directly into the xdocs folder.
>>> The site will then build successfully.
>>>
>>>> The two typos are: a missing underscore in the section id
>>>> mailing_list in index.xml and a stray # in bugs.xml. Forrest
>>>> gives rather cryptic errors for them.
>>> The error messages were mainly to do with why they did not
>>> conform with the
>>> DTD - i.e the # symbol is not allowed directly beneath <ol>
>>> and points out
>>> that only <li> can go inside.
>>>
>>> Most of the time, we will use Forrests v2.0 DTD -
>>>
>>> http://forrest.apache.org/dtdx/document-v20.dtdx.html
>>>
>>> (it is working towards being more xhtml2 compliant)
>>>
>>>> So sounds like the next step is to commit the prototype into svn
>>>> and set up a cron job to get it periodically published into some
>>>> sandbox (such as my home directory) so we can work on the tables
>>>> etc. Is that how you'd like to proceed?
>>> Yep, fine by me, at least I'll be able to be useful with patches then.
>>> Once your happy with stability, completeness and the
>>> forrestbot publishing
>>> is working well, then it can be moved when your happy.
>>>
>>>> I'm also curious if you have a suggestion for our documentation.
>>>> Would it make sense to try to convert it as well or might some
>>>> other solution be more appropriate?
>>> I have referred this to the Forrest dev list. It should not
>>> be a problem
>>> in principle, convert the .html files into xdoc xml and then
>>> back into .html
>>> integrated into the rest of the generated site. Hopefully the initial
>>> conversion to xdoc can be automated. Once in xdoc xml format
>>> then they can
>>> be placed appropriately, added to the site.xml and tabs.xml
>>> files and from
>>> then on be part of the site proper.
>>>
>>>>> I notice Jira replies are set to issues@, is there a Jira
>>> ticket filed
>>>> to
>>>>> change this to dev@.
>>>> Not yet. I was hoping to get to it this week but lately time has
>>>> a habit of getting away from me... You don't happen to know where
>>>> to change this, do you?
>>> I don't have the access to do it, I've asked on #infra and
>>> will let you know
>>> if someone does it. Otherwise you need to send a mail to
>>> apmail@ and file a
>>> Jira Issue on infra for it to be done .
>>>
>>> (http://apache.org/dev/reporting-issues.html#mail-config)
>>>
>>>
>>> Gav...
>>>
>>>> Martin
>>>>
>>>>> Gav...
>>>>>
>>>>> <quote who="Martin Sebor (JIRA)">
>>>>>> [
>>>>>> https://issues.apache.org/jira/browse/STDCXX-
>>> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>>>>> ]
>>>>>>
>>>>>> Martin Sebor reassigned STDCXX-686:
>>>>>> -----------------------------------
>>>>>>
>>>>>> Assignee: Martin Sebor
>>>>>>
>>>>>>> redesign web site
>>>>>>> -----------------
>>>>>>>
>>>>>>> Key: STDCXX-686
>>>>>>> URL:
>>> https://issues.apache.org/jira/browse/STDCXX-686
>>>>>>> Project: C++ Standard Library
>>>>>>> Issue Type: Improvement
>>>>>>> Components: Web
>>>>>>> Reporter: Martin Sebor
>>>>>>> Assignee: Martin Sebor
>>>>>>> Attachments: Copy of stdcxx.zip
>>>>>>>
>>>>>>> Original Estimate: 16h
>>>>>>> Remaining Estimate: 16h
>>>>>>>
>>>>>>> The current web site is a bunch of static HTML pages
>>> with a lot of
>>>>>>> difficult-to-maintain formatting cruft copied from
>>> pages of another
>>>>>>> incubator project. We should look into generating the site from
>>>>>>> easier-to-maintain "sources" using a tool like Apache
>>> Forrest or some
>>>>>>> such.
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> -
>>>>>> You can reply to this email to add a comment to the issue online.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>
>>
>> --
>> 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
Website Layout (was: RE: [jira] Assigned: (STDCXX-686) redesign web site)
Posted by "Gav...." <br...@brightontown.com.au>.
Hi Eric/All,
> -----Original Message-----
> From: Eric Lemings [mailto:Eric.Lemings@roguewave.com]
> Sent: Saturday, 2 February 2008 2:17 AM
> To: dev@stdcxx.apache.org
> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>
>
> I like it. It follows the style of the current site so it's not
> too disruptive.
>
> Couple minor suggestions:
>
> 1. Move the Documentation nav up to a tab next to the Download tab.
Yes, that can be done, no problem, I'll do that in my next patch if
no objections.
>
> 2. Move all links at the top of the home page to the nav bar,
> and subdivide them into groups (e.g. General [Objectives, About],
> Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
> License, Platforms, References]
Those links are auto generated from <sections> in the source and are
internal links to the relative section on that page. Dividing them
would mean creating new pages and moving content out of the home page
onto the new ones. This is no problem either, but its not my site, so
do you guys want to discuss the layout how you want it and I'll make
the changes ?
>
> 3. Where's the logo? :)
I'll fix that.
Gav...
>
> Brad.
>
> > -----Original Message-----
> > From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> > Sent: Friday, February 01, 2008 1:25 AM
> > To: dev@stdcxx.apache.org
> > Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
> >
> > G'Day,
> >
> > > -----Original Message-----
> > > From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> > Martin Sebor
> > > Sent: Friday, 1 February 2008 3:00 PM
> > > To: dev@stdcxx.apache.org
> > > Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> > >
> > > Gav... wrote:
> > > > Hi Martin,
> > > >
> > > > Let me know what info you need from me next.
> > > > Once the source files I sent are in svn, then I'll be
> > able to patch
> > > > properly against that.
> > >
> > > It looks quite good, thanks! I published it in my home directory
> > > to get some feedback from others:
> > >
> > > http://people.apache.org/~sebor/stdcxx/forrest-site/
> >
> > As initial information for others, the look of this site is the
> > standard issue 'forrest pelt theme' and if so wish, can be changed
> > to have more unique feel to it. This can wait I think until the
> > site is live and populated with docs.
> >
> > >
> > > Btw., it looks like a couple of typos snuck into index.xml and
> > > bugs.xml. I corrected them to get forrest to generate the static
> > > site (otherwise it fails)...
> >
> > Damn, sorry, I tested using 'forrest run' which ensures the
> > site is mostly
> > fine and working - but does not scrutinise the xdocs for
> > validity against
> > the DTD. Only when a 'forrest site' or 'forrest
> > validate-xdocs' is run do
> > the files get checked against the DTD.
> >
> > > ... but I still get the error below at the
> > > end. It looks like a link is bad or something.
> > >
> > > * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > > X [0] favicon.ico BROKEN: No
> > > pipeline matched request: favicon.ico
> > > at <map:mount> -
> > > file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > > ...
> > > Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
> > > Java Result: 1
> > >
> > > Copying broken links file to site root.
> > >
> > > Copying 1 file to /build/sebor/tmp/site2/build/site
> > >
> > > BUILD FAILED
> > > /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> > > building site.
> > >
> > > There appears to be a problem with your site build.
> >
> > Easy one and my bad again. Automatically a favicon.ico is
> > associated with
> > the site and is in fact copied there when doing a 'forrest
> > seed-sample'.
> > As you found out though this produces many un-needed sample
> > files. So I
> > created the initial layout with a 'forrest seed-basic' which gives you
> > a site structure but no files and in this case no favicon either.
> >
> > So the cure is to stick a favicon.ico directly into the xdocs folder.
> > The site will then build successfully.
> >
> > >
> > > The two typos are: a missing underscore in the section id
> > > mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > > gives rather cryptic errors for them.
> >
> > The error messages were mainly to do with why they did not
> > conform with the
> > DTD - i.e the # symbol is not allowed directly beneath <ol>
> > and points out
> > that only <li> can go inside.
> >
> > Most of the time, we will use Forrests v2.0 DTD -
> >
> > http://forrest.apache.org/dtdx/document-v20.dtdx.html
> >
> > (it is working towards being more xhtml2 compliant)
> >
> > >
> > > So sounds like the next step is to commit the prototype into svn
> > > and set up a cron job to get it periodically published into some
> > > sandbox (such as my home directory) so we can work on the tables
> > > etc. Is that how you'd like to proceed?
> >
> > Yep, fine by me, at least I'll be able to be useful with patches then.
> > Once your happy with stability, completeness and the
> > forrestbot publishing
> > is working well, then it can be moved when your happy.
> >
> > >
> > > I'm also curious if you have a suggestion for our documentation.
> > > Would it make sense to try to convert it as well or might some
> > > other solution be more appropriate?
> >
> > I have referred this to the Forrest dev list. It should not
> > be a problem
> > in principle, convert the .html files into xdoc xml and then
> > back into .html
> > integrated into the rest of the generated site. Hopefully the initial
> > conversion to xdoc can be automated. Once in xdoc xml format
> > then they can
> > be placed appropriately, added to the site.xml and tabs.xml
> > files and from
> > then on be part of the site proper.
> >
> > >
> > > >
> > > > I notice Jira replies are set to issues@, is there a Jira
> > ticket filed
> > > to
> > > > change this to dev@.
> > >
> > > Not yet. I was hoping to get to it this week but lately time has
> > > a habit of getting away from me... You don't happen to know where
> > > to change this, do you?
> >
> > I don't have the access to do it, I've asked on #infra and
> > will let you know
> > if someone does it. Otherwise you need to send a mail to
> > apmail@ and file a
> > Jira Issue on infra for it to be done .
> >
> > (http://apache.org/dev/reporting-issues.html#mail-config)
> >
> >
> > Gav...
> >
> > >
> > > Martin
> > >
> > > >
> > > > Gav...
> > > >
> > > > <quote who="Martin Sebor (JIRA)">
> > > >> [
> > > >> https://issues.apache.org/jira/browse/STDCXX-
> > >
> > 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > > >> ]
> > > >>
> > > >> Martin Sebor reassigned STDCXX-686:
> > > >> -----------------------------------
> > > >>
> > > >> Assignee: Martin Sebor
> > > >>
> > > >>> redesign web site
> > > >>> -----------------
> > > >>>
> > > >>> Key: STDCXX-686
> > > >>> URL:
> > https://issues.apache.org/jira/browse/STDCXX-686
> > > >>> Project: C++ Standard Library
> > > >>> Issue Type: Improvement
> > > >>> Components: Web
> > > >>> Reporter: Martin Sebor
> > > >>> Assignee: Martin Sebor
> > > >>> Attachments: Copy of stdcxx.zip
> > > >>>
> > > >>> Original Estimate: 16h
> > > >>> Remaining Estimate: 16h
> > > >>>
> > > >>> The current web site is a bunch of static HTML pages
> > with a lot of
> > > >>> difficult-to-maintain formatting cruft copied from
> > pages of another
> > > >>> incubator project. We should look into generating the site from
> > > >>> easier-to-maintain "sources" using a tool like Apache
> > Forrest or some
> > > >>> such.
> > > >> --
> > > >> This message is automatically generated by JIRA.
> > > >> -
> > > >> You can reply to this email to add a comment to the issue online.
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > 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
> >
>
>
>
> --
> 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: [jira] Assigned: (STDCXX-686) redesign web site
Posted by Eric Lemings <Er...@roguewave.com>.
I like it. It follows the style of the current site so it's not
too disruptive.
Couple minor suggestions:
1. Move the Documentation nav up to a tab next to the Download tab.
2. Move all links at the top of the home page to the nav bar,
and subdivide them into groups (e.g. General [Objectives, About],
Project [Lists, Wiki, Status, News, Team], Technical (Bugs, Readme,
License, Platforms, References]
3. Where's the logo? :)
Brad.
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Friday, February 01, 2008 1:25 AM
> To: dev@stdcxx.apache.org
> Subject: RE: [jira] Assigned: (STDCXX-686) redesign web site
>
> G'Day,
>
> > -----Original Message-----
> > From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of
> Martin Sebor
> > Sent: Friday, 1 February 2008 3:00 PM
> > To: dev@stdcxx.apache.org
> > Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
> >
> > Gav... wrote:
> > > Hi Martin,
> > >
> > > Let me know what info you need from me next.
> > > Once the source files I sent are in svn, then I'll be
> able to patch
> > > properly against that.
> >
> > It looks quite good, thanks! I published it in my home directory
> > to get some feedback from others:
> >
> > http://people.apache.org/~sebor/stdcxx/forrest-site/
>
> As initial information for others, the look of this site is the
> standard issue 'forrest pelt theme' and if so wish, can be changed
> to have more unique feel to it. This can wait I think until the
> site is live and populated with docs.
>
> >
> > Btw., it looks like a couple of typos snuck into index.xml and
> > bugs.xml. I corrected them to get forrest to generate the static
> > site (otherwise it fails)...
>
> Damn, sorry, I tested using 'forrest run' which ensures the
> site is mostly
> fine and working - but does not scrutinise the xdocs for
> validity against
> the DTD. Only when a 'forrest site' or 'forrest
> validate-xdocs' is run do
> the files get checked against the DTD.
>
> > ... but I still get the error below at the
> > end. It looks like a link is bad or something.
> >
> > * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> > X [0] favicon.ico BROKEN: No
> > pipeline matched request: favicon.ico
> > at <map:mount> -
> > file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> > ...
> > Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
> > Java Result: 1
> >
> > Copying broken links file to site root.
> >
> > Copying 1 file to /build/sebor/tmp/site2/build/site
> >
> > BUILD FAILED
> > /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> > building site.
> >
> > There appears to be a problem with your site build.
>
> Easy one and my bad again. Automatically a favicon.ico is
> associated with
> the site and is in fact copied there when doing a 'forrest
> seed-sample'.
> As you found out though this produces many un-needed sample
> files. So I
> created the initial layout with a 'forrest seed-basic' which gives you
> a site structure but no files and in this case no favicon either.
>
> So the cure is to stick a favicon.ico directly into the xdocs folder.
> The site will then build successfully.
>
> >
> > The two typos are: a missing underscore in the section id
> > mailing_list in index.xml and a stray # in bugs.xml. Forrest
> > gives rather cryptic errors for them.
>
> The error messages were mainly to do with why they did not
> conform with the
> DTD - i.e the # symbol is not allowed directly beneath <ol>
> and points out
> that only <li> can go inside.
>
> Most of the time, we will use Forrests v2.0 DTD -
>
> http://forrest.apache.org/dtdx/document-v20.dtdx.html
>
> (it is working towards being more xhtml2 compliant)
>
> >
> > So sounds like the next step is to commit the prototype into svn
> > and set up a cron job to get it periodically published into some
> > sandbox (such as my home directory) so we can work on the tables
> > etc. Is that how you'd like to proceed?
>
> Yep, fine by me, at least I'll be able to be useful with patches then.
> Once your happy with stability, completeness and the
> forrestbot publishing
> is working well, then it can be moved when your happy.
>
> >
> > I'm also curious if you have a suggestion for our documentation.
> > Would it make sense to try to convert it as well or might some
> > other solution be more appropriate?
>
> I have referred this to the Forrest dev list. It should not
> be a problem
> in principle, convert the .html files into xdoc xml and then
> back into .html
> integrated into the rest of the generated site. Hopefully the initial
> conversion to xdoc can be automated. Once in xdoc xml format
> then they can
> be placed appropriately, added to the site.xml and tabs.xml
> files and from
> then on be part of the site proper.
>
> >
> > >
> > > I notice Jira replies are set to issues@, is there a Jira
> ticket filed
> > to
> > > change this to dev@.
> >
> > Not yet. I was hoping to get to it this week but lately time has
> > a habit of getting away from me... You don't happen to know where
> > to change this, do you?
>
> I don't have the access to do it, I've asked on #infra and
> will let you know
> if someone does it. Otherwise you need to send a mail to
> apmail@ and file a
> Jira Issue on infra for it to be done .
>
> (http://apache.org/dev/reporting-issues.html#mail-config)
>
>
> Gav...
>
> >
> > Martin
> >
> > >
> > > Gav...
> > >
> > > <quote who="Martin Sebor (JIRA)">
> > >> [
> > >> https://issues.apache.org/jira/browse/STDCXX-
> >
> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > >> ]
> > >>
> > >> Martin Sebor reassigned STDCXX-686:
> > >> -----------------------------------
> > >>
> > >> Assignee: Martin Sebor
> > >>
> > >>> redesign web site
> > >>> -----------------
> > >>>
> > >>> Key: STDCXX-686
> > >>> URL:
> https://issues.apache.org/jira/browse/STDCXX-686
> > >>> Project: C++ Standard Library
> > >>> Issue Type: Improvement
> > >>> Components: Web
> > >>> Reporter: Martin Sebor
> > >>> Assignee: Martin Sebor
> > >>> Attachments: Copy of stdcxx.zip
> > >>>
> > >>> Original Estimate: 16h
> > >>> Remaining Estimate: 16h
> > >>>
> > >>> The current web site is a bunch of static HTML pages
> with a lot of
> > >>> difficult-to-maintain formatting cruft copied from
> pages of another
> > >>> incubator project. We should look into generating the site from
> > >>> easier-to-maintain "sources" using a tool like Apache
> Forrest or some
> > >>> such.
> > >> --
> > >> This message is automatically generated by JIRA.
> > >> -
> > >> You can reply to this email to add a comment to the issue online.
> > >>
> > >>
> > >
> > >
> >
> >
> >
> > --
> > 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: [jira] Assigned: (STDCXX-686) redesign web site
Posted by "Gav...." <br...@brightontown.com.au>.
G'Day,
> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
> Sent: Friday, 1 February 2008 3:00 PM
> To: dev@stdcxx.apache.org
> Subject: Re: [jira] Assigned: (STDCXX-686) redesign web site
>
> Gav... wrote:
> > Hi Martin,
> >
> > Let me know what info you need from me next.
> > Once the source files I sent are in svn, then I'll be able to patch
> > properly against that.
>
> It looks quite good, thanks! I published it in my home directory
> to get some feedback from others:
>
> http://people.apache.org/~sebor/stdcxx/forrest-site/
As initial information for others, the look of this site is the
standard issue 'forrest pelt theme' and if so wish, can be changed
to have more unique feel to it. This can wait I think until the
site is live and populated with docs.
>
> Btw., it looks like a couple of typos snuck into index.xml and
> bugs.xml. I corrected them to get forrest to generate the static
> site (otherwise it fails)...
Damn, sorry, I tested using 'forrest run' which ensures the site is mostly
fine and working - but does not scrutinise the xdocs for validity against
the DTD. Only when a 'forrest site' or 'forrest validate-xdocs' is run do
the files get checked against the DTD.
> ... but I still get the error below at the
> end. It looks like a link is bad or something.
>
> * [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
> X [0] favicon.ico BROKEN: No
> pipeline matched request: favicon.ico
> at <map:mount> -
> file:/build/sebor/apache-forrest-0.8/main/webapp/./site
> ...
> Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
> Java Result: 1
>
> Copying broken links file to site root.
>
> Copying 1 file to /build/sebor/tmp/site2/build/site
>
> BUILD FAILED
> /build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
> building site.
>
> There appears to be a problem with your site build.
Easy one and my bad again. Automatically a favicon.ico is associated with
the site and is in fact copied there when doing a 'forrest seed-sample'.
As you found out though this produces many un-needed sample files. So I
created the initial layout with a 'forrest seed-basic' which gives you
a site structure but no files and in this case no favicon either.
So the cure is to stick a favicon.ico directly into the xdocs folder.
The site will then build successfully.
>
> The two typos are: a missing underscore in the section id
> mailing_list in index.xml and a stray # in bugs.xml. Forrest
> gives rather cryptic errors for them.
The error messages were mainly to do with why they did not conform with the
DTD - i.e the # symbol is not allowed directly beneath <ol> and points out
that only <li> can go inside.
Most of the time, we will use Forrests v2.0 DTD -
http://forrest.apache.org/dtdx/document-v20.dtdx.html
(it is working towards being more xhtml2 compliant)
>
> So sounds like the next step is to commit the prototype into svn
> and set up a cron job to get it periodically published into some
> sandbox (such as my home directory) so we can work on the tables
> etc. Is that how you'd like to proceed?
Yep, fine by me, at least I'll be able to be useful with patches then.
Once your happy with stability, completeness and the forrestbot publishing
is working well, then it can be moved when your happy.
>
> I'm also curious if you have a suggestion for our documentation.
> Would it make sense to try to convert it as well or might some
> other solution be more appropriate?
I have referred this to the Forrest dev list. It should not be a problem
in principle, convert the .html files into xdoc xml and then back into .html
integrated into the rest of the generated site. Hopefully the initial
conversion to xdoc can be automated. Once in xdoc xml format then they can
be placed appropriately, added to the site.xml and tabs.xml files and from
then on be part of the site proper.
>
> >
> > I notice Jira replies are set to issues@, is there a Jira ticket filed
> to
> > change this to dev@.
>
> Not yet. I was hoping to get to it this week but lately time has
> a habit of getting away from me... You don't happen to know where
> to change this, do you?
I don't have the access to do it, I've asked on #infra and will let you know
if someone does it. Otherwise you need to send a mail to apmail@ and file a
Jira Issue on infra for it to be done .
(http://apache.org/dev/reporting-issues.html#mail-config)
Gav...
>
> Martin
>
> >
> > Gav...
> >
> > <quote who="Martin Sebor (JIRA)">
> >> [
> >> https://issues.apache.org/jira/browse/STDCXX-
> 686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >> ]
> >>
> >> Martin Sebor reassigned STDCXX-686:
> >> -----------------------------------
> >>
> >> Assignee: Martin Sebor
> >>
> >>> redesign web site
> >>> -----------------
> >>>
> >>> Key: STDCXX-686
> >>> URL: https://issues.apache.org/jira/browse/STDCXX-686
> >>> Project: C++ Standard Library
> >>> Issue Type: Improvement
> >>> Components: Web
> >>> Reporter: Martin Sebor
> >>> Assignee: Martin Sebor
> >>> Attachments: Copy of stdcxx.zip
> >>>
> >>> Original Estimate: 16h
> >>> Remaining Estimate: 16h
> >>>
> >>> The current web site is a bunch of static HTML pages with a lot of
> >>> difficult-to-maintain formatting cruft copied from pages of another
> >>> incubator project. We should look into generating the site from
> >>> easier-to-maintain "sources" using a tool like Apache Forrest or some
> >>> such.
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> You can reply to this email to add a comment to the issue online.
> >>
> >>
> >
> >
>
>
>
> --
> 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: [jira] Assigned: (STDCXX-686) redesign web site
Posted by Martin Sebor <se...@roguewave.com>.
Gav... wrote:
> Hi Martin,
>
> Let me know what info you need from me next.
> Once the source files I sent are in svn, then I'll be able to patch
> properly against that.
It looks quite good, thanks! I published it in my home directory
to get some feedback from others:
http://people.apache.org/~sebor/stdcxx/forrest-site/
Btw., it looks like a couple of typos snuck into index.xml and
bugs.xml. I corrected them to get forrest to generate the static
site (otherwise it fails) but I still get the error below at the
end. It looks like a link is bad or something.
* [6/30] [0/0] 0.016s 1.5Kb themes/getBlank.js
X [0] favicon.ico BROKEN: No
pipeline matched request: favicon.ico
at <map:mount> -
file:/build/sebor/apache-forrest-0.8/main/webapp/./site
...
Total time: 0 minutes 15 seconds, Site size: 182,695 Site pages: 42
Java Result: 1
Copying broken links file to site root.
Copying 1 file to /build/sebor/tmp/site2/build/site
BUILD FAILED
/build/sebor/apache-forrest-0.8/main/targets/site.xml:180: Error
building site.
There appears to be a problem with your site build.
The two typos are: a missing underscore in the section id
mailing_list in index.xml and a stray # in bugs.xml. Forrest
gives rather cryptic errors for them.
So sounds like the next step is to commit the prototype into svn
and set up a cron job to get it periodically published into some
sandbox (such as my home directory) so we can work on the tables
etc. Is that how you'd like to proceed?
I'm also curious if you have a suggestion for our documentation.
Would it make sense to try to convert it as well or might some
other solution be more appropriate?
>
> I notice Jira replies are set to issues@, is there a Jira ticket filed to
> change this to dev@.
Not yet. I was hoping to get to it this week but lately time has
a habit of getting away from me... You don't happen to know where
to change this, do you?
Martin
>
> Gav...
>
> <quote who="Martin Sebor (JIRA)">
>> [
>> https://issues.apache.org/jira/browse/STDCXX-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Martin Sebor reassigned STDCXX-686:
>> -----------------------------------
>>
>> Assignee: Martin Sebor
>>
>>> redesign web site
>>> -----------------
>>>
>>> Key: STDCXX-686
>>> URL: https://issues.apache.org/jira/browse/STDCXX-686
>>> Project: C++ Standard Library
>>> Issue Type: Improvement
>>> Components: Web
>>> Reporter: Martin Sebor
>>> Assignee: Martin Sebor
>>> Attachments: Copy of stdcxx.zip
>>>
>>> Original Estimate: 16h
>>> Remaining Estimate: 16h
>>>
>>> The current web site is a bunch of static HTML pages with a lot of
>>> difficult-to-maintain formatting cruft copied from pages of another
>>> incubator project. We should look into generating the site from
>>> easier-to-maintain "sources" using a tool like Apache Forrest or some
>>> such.
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
>