[
https://issues.apache.org/jira/browse/LUCENE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080628#comment-13080628
]
Hoss Man commented on LUCENE-2748:
----------------------------------
bq. We'll still need to figure out per release docs, but I suspect it won't be
that hard to convert that stuff to Markdown going forward and having our
deploy/release mechanism just publish it to the CMS.
I would actually argue that the "per release" docs don't need to have the same
look/feel as the site -- probably better actually moving forward to make them
clearly distinct so there is an obvious distinction between "the site" and "the
docs" (which may also help to prevent us from inadvertently putting relative
links in the "per release" docs that wont work from a local install of a
release)
On the java side of things, moving all of the per-release docs into the javadoc
process (using the doc-files dir, and linking to them from overview.html) would
be one good way to keep everything encapsulated nicely.
I haven't dug into it, but the Apache CMS Ref guide has an details on how to
publish a big tar ball of auto-generated docs into the CMS, with an example of
how to automate the process with a script (ie: from hudson for nightly docs or
as part of a release manager script)
https://www.apache.org/dev/cmsref.html#generated-docs
> Convert all Lucene web properties to use the ASF CMS
> ----------------------------------------------------
>
> Key: LUCENE-2748
> URL: https://issues.apache.org/jira/browse/LUCENE-2748
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
>
> The new CMS has a lot of nice features (and some kinks to still work out) and
> Forrest just doesn't cut it anymore, so we should move to the ASF CMS:
> http://apache.org/dev/cms.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
