How would this change translate to product branch ?
Would it also make sense to extract parts of documentation related to "Servlet-Only
Distribution" provided on http://wildfly.org/downloads/
I think current documentation presumes full app server distribution.
Maybe going further it would also make sense to compose docs via provisioning tool
) so users could have up to date documentation related
to stuff they are using in their setup ... e.g. when they compose server just with
undertow + resteasy + hibernate they wouldn't get documentation for clustering, soap
webservices, messaging, ...
The same could also happen for Quickstarts, have them provisioned via pm (or similar) tool
based on the selected components/feature packs.
----- Original Message -----
I've converted confluence docs asciidoc   ones that will be part of
take a look at them and let me know if there are any big issues.
as most of you already know, I was working on moving our confluence based 
documentation to asciidoc based one.
result can be seen at  or rendered to html at 
A good side effect of conversion is that now docs are also browsable directly
For example  or 
Currently I kept same structure as we had in confluence, which in practice
we have set of "guides" that than have lots of sub pages / includes that
produce "big" guides.
Currently such guides are:
- Admin Guide
- Developer Guide
- Getting started guide
- Getting Started Developing Applications Guide
- High Availability Guide
- Extending WildFly guide
- JavaEE 7(6 actually) Tutorial
- Elytron security guide
Problem is that some of this guide as such make sense, but not all of them
In some cases we have duplicated docs for same thing, in others we content in
For example instead of having all subsystem reference docs under admin guide,
some are under Developer Guide and some even under HA guide.
Going forward we should "refactor" docs a bit, so we would end up with 3-4
high quality guides.
We should also go trough all docs and remove/update the outdated content.
Plan is also to have documentation now part of WildFly codebase.
So when we would submit PR with new feature, it would also include
documentation for it as well.
Rendered docs can be build as part of our build / release process and can be
rendered to different formats.
for example default is HTML  or PDF 
I've send experimental PR to show how docs would fit into WildFly build 
Please take look at current docs and if you have any comments / suggestions
what we can improve before merging it let me know.
At this point I've not done much content-wise changes but just conversion +
Content updates can come after this is merged.
wildfly-dev mailing list