Rafael, Couple of things I'd recommend.
- We should put the documentation adoc's in a documentation folder. This will allow us to upload to different folders, as I'm sure we'll want to cut over the remaining parts of the site to adoc to make it more consistent and easier to update. We'll also have to turn on the preserveDirectories option in the maven plugin. - Can we upgrade to asciidoctor 1.5.0? The only issue I saw was a removed import in the template erb file. - I'm a bit concerned with us uploading to the doc site before the source files are checked in. this is something we'll likely need to work out via process. - To delete the current files, we need to update the links on the page to go to /documentation. I'm also wondering if we should now introduce a top level pom that can be used during releases to ensure the docs get properly versioned. Then we can execute a release and upload the site during the release process. John On Thu, Sep 11, 2014 at 1:49 PM, Rafael Benevides <[email protected]> wrote: > Hi all, > > I worked on documentation migration from MarkDown to Asciidoc. > > - The syntax-highlighter was checked > - The intra-document links was checked > - The the anchor links was checked > - The table format was checked > - Minor adjustments needed > > The sources were placed here until we complete the review: > https://github.com/rafabene/deltaspike/tree/asciidoc-migration/documentation/src/main/asciidoc > > They were published at http://deltaspike.apache.org/documentation/ > > Once that they got merged to Git, the SVN files should be removed to avoid > any misunderstood. > > Please, let me know if you find any issues. > > Thanks > > > -- > > *Rafael Benevides | Senior Software Engineer* > JBoss Developer > M: +55-61-9269-6576 > > [image: Red Hat] > > Better technology. Faster innovation. Powered by community collaboration. > See how it works at www.redhat.com > > [image: LinkedIn] <http://www.linkedin.com/company/3258288> [image: > Youtube] <https://www.youtube.com/redhatlatam> >
