I'd like to re-open the discussion on documentation format, as there
seems to have been a decision slip through the cracks on this that many
of us missed. My greatest concern is that the selected tool needs to
meet the requirements stated in DELTASPIKE-13 [1]. Does the choice of
Apache CMS for hosting documentation meet the following requirements?
1) Making available the documentation for previously released versions
of DeltaSpike.
2) Making available the documentation in offline formats, such as HTML
or PDF available for download.
[1] https://issues.apache.org/jira/browse/DELTASPIKE-13
- Shane
On 29/06/12 03:21, Mark Struberg wrote:
Hi!
Good topic!
finally we have our CMS!
It's really ugly as I don't have an eye for good web pages, but at least it
exists ;)
But ignore the layout for now. We can easily change this later.
http://incubator.apache.org/deltaspike
You can find more infos at [1].
If you like to edit a page then simply add the following to your bookmarks:
javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))
add this manually as bookmark. Then visit any CMS page and click on the
bookmark. You will get an auth window where you need to login via your apacheId
and pwd.
Saving the change will do a svn commit in the background and publish the
changes.
LieGrue,
strub
[1] http://wiki.apache.org/general/ApacheCms2010
----- Original Message -----
From: Jason Porter <[email protected]>
To: [email protected]
Cc:
Sent: Thursday, June 28, 2012 7:09 PM
Subject: Re: [suggestion] - Documentation
Maybe we need to finish the documentation discussion and just be done with
it. I really like asciidoc there's lots of tools for it and it renders
docbook which we can take and do whatever with. The only problem right now
is that there's no maven plugin for it and jython is really slow :( The
GitHub guys are doing a ruby port which would work really well with jruby,
but I don't think they've released it yet.
For now the temporary wiki I think works decently.
On Thu, Jun 14, 2012 at 4:43 AM, Gerhard Petracek <
[email protected]> wrote:
hi charles,
thx for the feedback!
@documentation:
this part of the wiki is called "Temporary Documentation" because
we don't
plan to keep the documentation in the wiki.
-> for now we just collect information there (in a very simple style) to
avoid a lack of information.
regards,
gerhard
2012/6/14 Charles Moulliard <[email protected]>
> Hi,
>
> I would like to suggest that we split the page user documentation in
> several
> chapters - pages to provide more visibility on the project DeltaSpike
>
> - Introduction - goals,
> - Getting started,
> - Modules
> - jpa,
> - security,
> - Developers,
> - Community
>
> What do you think about that ?
>
> Remark :
> - Also, we should allow people to have access to this web page -->
> http://incubator.apache.org/deltaspike/ which is not the case today
except
> the wiki page
> - To build the documentation, we could use scalate (templating engine
-
> http://scalate.fusesource.org/)) which is used by Apache Karaf, Apache
> Camel
> and Apache ServiceMix to generate static web sites but also PDF doc.
> - GitHub repo has not link to the project
> (https://github.com/apache/incubator-deltaspike)
>
>
> Regards,
>
> Charles
>
> --
> View this message in context:
>
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/suggestion-Documentation-tp4652767.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list
archive
> at Nabble.com.
>
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
