Well I just set it up to publish the content once. We can have a look at it then.
I generally set it up to scm:svn:https://svn.apache.org/repos/infra/websites/production/flex/content/maven/flexjs/${website.path} While website-path is always set to "latest-dev" during development and to the version of the release for a release. So for now it would probably be: https://flex.apache.org/maven/flexjs/latest-dev But we'll just have a look. Hope I don't have to setup anything magical for the Subversion commit. Chris ________________________________ Von: Alex Harui <[email protected]> Gesendet: Dienstag, 13. September 2016 17:20:35 An: [email protected] Betreff: Re: AW: AW: AW: [FlexJS] Starting with the Docs On 9/13/16, 12:07 AM, "Christofer Dutz" <[email protected]> wrote: >Hi all, > > >How about me turning on the site deployment feature (It's the identical >setup to the one of the Maven project). It would automatically deploy a >sub-directory of "https://flex.apache.org"; ... I would suggest >"https://flex.apache.org/flexjs";. We could have a look at what it >produces and find a way to add a form-mailer. > > >Would this be acceptable? Seems worth doing so we can see how it will look. I read a bit about GitHub pages and it sounded interesting to me. I wonder if GH Pages would get us more visibility than flex.a.o. GH Pages seems to leverage "orphan" branches so the doc can be in the same repo, but in a different "view" or branch so activity there won't clutter changes to code. Whether we use GH Pages or not, we might want to consider organizing the doc that way. I'm not sure if ASF projects are required to release written doc that is effectively a web site. We don't have "releases" of our web site sources. Gh Pages seems to support AsciiDoc. I read a bit about AsciiDoc and didn't easily get why it would be better than markdown. It just seemed like another flavor of markdown. -Alex
