Documentation for Rackspace Cloud DNS#134
Conversation
|
Adrian Cole » jclouds.github.com #15 SUCCESS |
There was a problem hiding this comment.
Why do the examples use a combination of ant and maven? This could be simpler.
|
This quickstart guide has some general rot in it, you should clean this document up. Terms are off, examples seem overly complex, and there are pre sections that appear untenable. |
|
@silkysun Do you have some suggestions on how to fix the code samples? I've tried the triple backtick thing (e.g. ```xml) but as you can see from http://www.jclouds.org/documentation/quickstart/rackspace/ it doesn't want to work with GitHub pages. The pre sections with the highlight do a proper job of formatting and highlighting the code so it looks good but there's too much space around the sample. Perhaps embedding a gist is the way to go? Thoughts? Also does BuildHive publish the pages somewhere? I run my docs through jekyll but it doesn't always seem to be one-to-one with what winds up on jclouds.org. |
|
@everett-toews jekyll works great for me and shows these problems. |
|
Tracking issue for Ant/Maven stuff in jclouds/jclouds-examples#35 |
|
@everett-toews I'm working on this. I should have more for you later this afternoon or tomorrow. Thanks for your patience! |
|
@everett-toews I apologize for this delayed response. This weekend got very busy for me, and I lost track of time. Have you tried removing the pre tags around your xml snippets? Please look at the Maven doc for examples of xml snippets that render correctly. https://raw.github.com/jclouds/jclouds.github.com/master/documentation/userguide/using-maven.md |
|
Will address these comments in separate PRs. |
|
@mattstep Not sure if you noticed but I addressed your comments from this pull request in PR #141 a few days ago. Switching to Maven was really useful. It also eliminated the need for the XML samples. Thanks for your review. And sorry about the timing of it all. I got pretty sick after I submitted this PR and I should have communicated the fact that I was down and out. |
|
No worries dude. Thanks for addressing!
|
No description provided.