I committed the site in SVN and created a ticket for Infra: https://issues.apache.org/jira/browse/INFRA-5683
The new home for documentation is now https://svn.apache.org/repos/asf/poi/site/publish/ Source XML for Forrest is in ./src Compiled .html is in ./publish See https://svn.apache.org/repos/asf/poi/site/README.txt for instructions. > Make it https://svn.apache.org/repos/asf/poi/site/content/. and we will be > more ready to switch to the CMS. I followed the pattern that other projects use. I may be wrong, but there is no point to put .html generated from Forrest into CMS. If we allow online-editing of the docs via CMS then we will need to refactor out .xml into a form compatible with the Apache CMS. Am I wrong? P.S. I'm in the middle of uploading javadocs. For unknown reasons my svn refuses to commit all in one go and I have to chop apidocs into smaller parts. Yegor On Tue, Dec 18, 2012 at 12:48 AM, Dave Fisher <[email protected]> wrote: > > On Dec 17, 2012, at 12:44 AM, Yegor Kozlov wrote: > >>> I'd suggest not under trunk, but alongside >> >> OK, it will be https://svn.apache.org/repos/asf/poi/site. > > Make it https://svn.apache.org/repos/asf/poi/site/content/. and we will be > more ready to switch to the CMS. > >> I will try to find time this week to do the first pass. > > I have been thinking about this as well. Let me know how I can help. > > Regards, > Dave > >> >> Yegor >> >> On Mon, Dec 17, 2012 at 12:16 PM, Nick Burch <[email protected]> wrote: >>> On Mon, 17 Dec 2012, Yegor Kozlov wrote: >>>> >>>> I'm for svnpubsub, as it seems the shortest way. >>> >>> >>> I guess we could move to that, and plan to do it in a way that we can use >>> the cms later with minimal changes? >>> >>> >>>> As I understand, we will need to keep the generated html somewhere in >>>> svn and then ask Infra to enable svnpubsub for our site . >>> >>> >>> Yup >>> >>> >>>> Migration of the Forrest part seems easy: >>>> 1. create a new directory "site" under >>>> https://svn.apache.org/repos/asf/poi/trunk >>> >>> >>> I'd suggest not under trunk, but alongside >>> >>> >>>> 2. create two sub-directories: >>>> site/docs <-- Forrest .xml files, copy them from >>>> trunk/src/documentation >>>> /site/publish <-- generated html >>> >>> >>> We don't actually need to copy the source files, just tell forest where to >>> put the resulting published files (likely with a delete first to clean out, >>> so old files don't get stuck). Then you svn add/remove as needed and commit, >>> then a few secs later it's live! >>> >>> >>> Nick >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
