Sure. The wiki space will be automatically exported to static HTML files that you can just grab.
Other export options are available (e.g. PDF) but must be triggered manually.
Cheers,
Uli
On 01.04.2010 11:08, Christophe Cordenier wrote:
Hi
Do you mind if we (in the fututre and if you are interested in our proposal)
mirror the conluence wiki to wookicentral for feedback feature ? Is it
possible in terms of license, has confluence an API to extract wikis content
so we can automatically import it on wooki
The book will be read-only and only comments will be allowed so you can have
access to user direct feedback through RSS
Best Regards,
Christophe.
2010/4/1 Ulrich Stärk<[email protected]>
OK, if the PMC votes on that, I'll take care of it. The vote just has to
mention for me to get a confluence admin account as those are normally
granted only to PMC members.
Uli
On 31.03.2010 22:44, Howard Lewis Ship wrote:
I'm fine with anything that doesn't end up as a giant unresolved TODO
item in my list :-) I have more than enough of those already.
On Wed, Mar 31, 2010 at 1:26 PM, Ulrich Stärk<[email protected]> wrote:
Publishing the website from a confluence wiki is already set up
throughout
the ASF and works quite well. That would also be seperated from the
"real"
wiki. We could move that one to a confluence instance as well and clean
it
up.
On 31.03.2010 22:12, Sebastian Hennebrueder wrote:
I believe that the main site could be generated as well. I update my
site for every article and it is just a git push command.
What do you think about leveraging the current wiki? The last time, I
looked the articles had different quality and structure. The
organization has already improved but we could provide a better layout
as well and move the stuff to a confluence wiki.
Ulrich Stärk schrieb:
Yeah, but do we also need and want it for the site itself or will it
be enough for the docs? I believe that a confluence backed up site
seperated from the docs themselves can have benefits, e.g. easier
publishing of news, articles and so on. We'd become more dynamic.
On 31.03.2010 21:07, Howard Lewis Ship wrote:
I prefer the textile approach, just making it easier to write& deploy
docs.
On Wed, Mar 31, 2010 at 10:36 AM, Ulrich Stärk<[email protected]>
wrote:
I guess we should decide first whether we want the whole site in
source
control and done with Textile (or some other tool) or if we want to
split
documentation and site and have site in some content management
system like
the confluence wiki.
Uli
On 31.03.2010 18:49, Sebastian Hennebrueder wrote:
Hi all,
I am sorry for not being present at the moment. I am extremely busy
in a
new project. I will try to provide a Prototype using Textile as
rendering base for the end of next week.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
