jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Everett Toews (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-169) Make links/styles/images relative
Date Wed, 03 Jul 2013 22:44:19 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Everett Toews updated JCLOUDS-169:
----------------------------------

    Description: 
This should allow the site to be deployed at any level in a directory hierarchy and it will
still render/work correctly because the links/style/image refs are relative. In particular
it should appear correctly and all links should work in the Jenkins workspace when the site
gets built. I.E.

https://buildhive.cloudbees.com/job/jclouds/job/jclouds.github.com/ws/_site/index.html

The ultimate goal of this is to make doc contribution easier. If the site renders/works correctly
in the Jenkins workspace, contributors can simply edit a Markdown file in GitHub, submit a
PR, and check the result in the workspace. Anyone will be able to improve the jclouds documentation
entirely from within their web browser.

  was:
This should allow the site to be deployed at any level in a directory hierarchy and it will
still render/work correctly because the links/style/image refs are relative. In particular
it should appear correctly and all links should work in the Jenkins workspace when the site
gets built. I.E.

https://buildhive.cloudbees.com/job/jclouds/job/jclouds.github.com/ws/_site/index.html

The ultimate goal of this is to make doc contribution easier. If the site renders/works correctly
in the Jenkins workspace, contributors can simply edit a Markdown file in GitHub, submit a
PR, and check the result in the workspace.

    
> Make links/styles/images relative
> ---------------------------------
>
>                 Key: JCLOUDS-169
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-169
>             Project: jclouds
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Everett Toews
>
> This should allow the site to be deployed at any level in a directory hierarchy and it
will still render/work correctly because the links/style/image refs are relative. In particular
it should appear correctly and all links should work in the Jenkins workspace when the site
gets built. I.E.
> https://buildhive.cloudbees.com/job/jclouds/job/jclouds.github.com/ws/_site/index.html
> The ultimate goal of this is to make doc contribution easier. If the site renders/works
correctly in the Jenkins workspace, contributors can simply edit a Markdown file in GitHub,
submit a PR, and check the result in the workspace. Anyone will be able to improve the jclouds
documentation entirely from within their web browser.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message