[
https://issues.apache.org/jira/browse/WICKET-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Dashorst closed WICKET-25.
----------------------------------
Resolution: Fixed
we have a site on http://incubator.apache.org/wicket
> Create Wicket web presence on Apache turf
> -----------------------------------------
>
> Key: WICKET-25
> URL: https://issues.apache.org/jira/browse/WICKET-25
> Project: Wicket
> Issue Type: Task
> Components: site
> Reporter: Martijn Dashorst
>
> We don't have much to show on http://incubator.apache.org/wicket which will
> be our Apach based website while during the incubator. This site has to be
> published through the use of svn, and has to be static (i.e. generated).
> Until now we used the maven xdoc format for generating the website of Wicket
> and related projects. This is very cumbersome to make it work, not only
> because of the format but also due to the intermediate steps necessary to get
> the thing published. Publishing news, blogs, etc. should be very easy and
> straightforward in this day and age of Content Management Systems. Heck,
> there are tons of great php or Java based CMS systems available in general,
> and only moin moin or confluence at Apache.
> Using one system as our CMS will enable us to create and add content to our
> website quickly, and will help integrating user content with the website
> seamlessly.
> In some discussions on our dev list, we decided to use confluence as our CMS
> and are willing to lend a hand to support confluence as part of the infratax.
> Confluence uses a special plugin to constantly generate a website after an
> update, so that the site is static, and not backed by a database. This is
> rather overkill for a project of Wicket's stature, but for a bohemoth like
> the whole of Apache, it actually makes sense to use a static website rather
> than a dynamically generated one.
> This issue is used to track the progress of our migration from the maven
> generated website to a confluence based website. See the subtasks for more
> information on what is and needs to be done.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
