[
https://issues.apache.org/jira/browse/WHIRR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877475#action_12877475
]
Tom White commented on WHIRR-19:
--------------------------------
+1 for using Maven site generation and for putting site and docs in trunk. Can
we have a skin like Tapestry's or Maven's?
I noticed that Doxia (which is what Maven uses for content generation) supports
a number of markup formats, including Confluence wiki markup, so we might use
that one for consistency with our wiki (one fewer markup type to learn).
If we do this, I'll open up the wiki for editing by anyone with a confluence
account.
We might use Tapestry's release checklist as a basis for Whirr's. Note in
particular that they use Ant to build the release artifacts - I can understand
this as I've had problems in the past getting Maven to build tarballs with the
file layout I wanted.
> Create project website
> ----------------------
>
> Key: WHIRR-19
> URL: https://issues.apache.org/jira/browse/WHIRR-19
> Project: Whirr
> Issue Type: Task
> Components: documentation
> Reporter: Tom White
> Priority: Blocker
> Fix For: 0.1.0
>
>
> Whirr needs a website at http://incubator.apache.org/whirr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
