You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Ignasi Barrera <no...@github.com> on 2014/01/04 17:14:05 UTC
[jclouds-site] Rebranding proposal (#51)
This is a first proposal for the site rebranding based on Twitter's Bootstrap.
**This PR is just a WIP!**
Note the branch only exists in GitHub (not in the ASF repos). This way we can add changes to the branch and use the pull request to discuss the new layout, design, theme, etc, and have it online so we can see how it evolves. Consider this branch yours, and feel free to commit directly any change you want. Let's build together the new site!
I've made the first steps to rebrand the site using the [Flatly](http://bootswatch.com/flatly/) theme:
* Configured a more friendly landing page. It's still missing an initial set of icons of the popular supported providers.
* Configured the main navigation bar with the pages I think are the most important ones. Any main guide should have a direct link there.
* Added the links to the "Getting started" guides. The pages need to be reworked, though.
* Migrated the Blog.
I've changed a bit the structure of the site. I've moved the `gettingstarted`, `blog` and `documentation` folders to the top level, to have a directory structure that matches the navigation bar. That would help contributor find the documents easily.
And that's it! We should start by discussing about the new layout (navigation, the structure of the landing page, and the pages), and once we are happy with the structure we can move to the theme/style, as it should be as easy as replacing a CSS file with the one we prefer.
@everett-toews @demobox Wanna have a look and spend some time with this?
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site rebranding
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/51
-- Commit Summary --
* First rebranding proposal
-- File Changes --
A _includes/footer.html (6)
A _includes/footer.html~ (5)
A _includes/head.html (32)
A _includes/navbar.html (73)
A _layouts/home.html (110)
A _layouts/home.html~ (71)
A _layouts/home.htmx~ (110)
A _layouts/home.htmy~ (110)
A _layouts/home.htmz~ (71)
A _layouts/page.html (18)
M _layouts/post.html (76)
R _posts/2009-05-11-jclouds-s3-beta-released.md (0)
A _posts/2009-05-11-jclouds-s3-beta-released.md~ (14)
R _posts/2009-05-13-catching-exceptions-with-less-keystrokes.md (0)
R _posts/2011-10-18-jclouds-1-2-released.md (0)
R _posts/2012-01-17-jclouds-training-and-jfokus-stockholm.md (0)
R _posts/2012-01-21-jclouds-1-3-released.md (0)
R _posts/2012-03-09-ec2-gets-rid-of-that-if-instancetype-is32bit.md (0)
R _posts/2012-03-23-take-a-peek-at-vcloud-director-1-5-openstack-and.md (0)
R _posts/2012-05-02-new-toys-in-1-5-0-alpha-6.md (0)
R _posts/2012-07-16-fluency-for-paginated-api-lists.md (0)
R _posts/2012-09-28-jclouds-1-5-is-out.md (0)
R _posts/2012-11-09-500-jclouds-builds-on-buildhive-and-counting.md (0)
R _posts/2012-11-17-jclouds-1-5-3-out-the-door.md (0)
R _posts/2012-12-12-jclouds-1-5-4-mistletoe-released.md (0)
R _posts/2013-04-28-jclouds-1-6-0-released.md (0)
R _posts/2013-05-13-jclouds-at-gluecon-2013.md (0)
M blog/index.md (6)
A blog/index.md~ (10)
A css/bootstrap-theme.css (459)
A css/bootstrap-theme.min.css (9)
A css/bootstrap.css (7733)
A css/bootstrap.min.css (1)
A css/style.css (12)
R css/syntax.css (0)
A fonts/glyphicons-halflings-regular.eot (0)
A fonts/glyphicons-halflings-regular.svg (229)
A fonts/glyphicons-halflings-regular.ttf (0)
A fonts/glyphicons-halflings-regular.woff (0)
A gettingstarted/blobstore.md (432)
R gettingstarted/blobstore.md~ (0)
A gettingstarted/compute.md (627)
R gettingstarted/index.md~ (0)
A gettingstarted/installation-guide.md (190)
A gettingstarted/what-is-jclouds.md (50)
A img/apple-touch-icon-114-precomposed.png (0)
A img/apple-touch-icon-144-precomposed.png (0)
A img/apple-touch-icon-57-precomposed.png (0)
A img/apple-touch-icon-72-precomposed.png (0)
A img/favicon.png (0)
R img/feather-small.gif (0)
R img/fullsizelogo.jpg (0)
A img/glyphicons-halflings-white.png (0)
A img/glyphicons-halflings.png (0)
M index.md (2)
A js/bootstrap.min.js (9)
A js/html5shiv.js (8)
A js/jquery.min.js (6)
A js/less-1.3.3.min.js (9)
R js/scripts.js (0)
A less/alerts.less (67)
A less/badges.less (51)
A less/bootstrap.less (49)
A less/bootswatch.less (185)
A less/breadcrumbs.less (23)
A less/button-groups.less (253)
A less/buttons.less (158)
A less/carousel.less (231)
A less/close.less (33)
A less/code.less (53)
A less/component-animations.less (29)
A less/dropdowns.less (192)
A less/forms.less (366)
A less/glyphicons.less (237)
A less/grid.less (93)
A less/input-groups.less (136)
A less/jumbotron.less (40)
A less/labels.less (58)
A less/list-group.less (88)
A less/media.less (56)
A less/mixins.less (858)
A less/modals.less (132)
A less/navbar.less (624)
A less/navs.less (262)
A less/normalize.less (406)
A less/pager.less (55)
A less/pagination.less (85)
A less/panels.less (172)
A less/popovers.less (133)
A less/print.less (105)
A less/progress-bars.less (92)
A less/responsive-utilities.less (209)
A less/scaffolding.less (119)
A less/tables.less (236)
A less/theme.less (247)
A less/thumbnails.less (31)
A less/tooltip.less (95)
A less/type.less (279)
A less/utilities.less (56)
A less/variables.less (642)
A less/wells.less (29)
D news.md (20)
A old-site/_config.yml (3)
A old-site/_includes/disqus.html (12)
R old-site/_includes/footer.md (0)
R old-site/_includes/menu.md (0)
R old-site/_layouts/index.html (0)
R old-site/_layouts/jclouds.html (0)
A old-site/_layouts/post.html (60)
A old-site/_posts/tumblr/2009-05-11-jclouds-s3-beta-released.md (14)
A old-site/_posts/tumblr/2009-05-13-catching-exceptions-with-less-keystrokes.md (38)
A old-site/_posts/tumblr/2011-10-18-jclouds-1-2-released.md (26)
A old-site/_posts/tumblr/2012-01-17-jclouds-training-and-jfokus-stockholm.md (17)
A old-site/_posts/tumblr/2012-01-21-jclouds-1-3-released.md (44)
A old-site/_posts/tumblr/2012-03-09-ec2-gets-rid-of-that-if-instancetype-is32bit.md (27)
A old-site/_posts/tumblr/2012-03-23-take-a-peek-at-vcloud-director-1-5-openstack-and.md (49)
A old-site/_posts/tumblr/2012-05-02-new-toys-in-1-5-0-alpha-6.md (55)
A old-site/_posts/tumblr/2012-07-16-fluency-for-paginated-api-lists.md (55)
A old-site/_posts/tumblr/2012-09-28-jclouds-1-5-is-out.md (15)
A old-site/_posts/tumblr/2012-11-09-500-jclouds-builds-on-buildhive-and-counting.md (17)
A old-site/_posts/tumblr/2012-11-17-jclouds-1-5-3-out-the-door.md (24)
A old-site/_posts/tumblr/2012-12-12-jclouds-1-5-4-mistletoe-released.md (51)
A old-site/_posts/tumblr/2013-04-28-jclouds-1-6-0-released.md (15)
A old-site/_posts/tumblr/2013-05-13-jclouds-at-gluecon-2013.md (23)
R old-site/documentation/community/index.md (0)
R old-site/documentation/devguides/continuous-integration.markdown (0)
R old-site/documentation/devguides/creating-providers-with-maven.markdown (0)
R old-site/documentation/devguides/guice-guava-primer.md (0)
R old-site/documentation/devguides/index.md (0)
R old-site/documentation/devguides/provider-metadata.markdown (0)
R old-site/documentation/devguides/provider-testing.markdown (0)
R old-site/documentation/devguides/using-eclipse.markdown (0)
R old-site/documentation/examples/google-app-engine.md (0)
R old-site/documentation/examples/index.md (0)
R old-site/documentation/faqs/ec2-faq.md (0)
A old-site/documentation/gettingstarted/index.md (31)
R old-site/documentation/gettingstarted/what-is-jclouds.md (0)
R old-site/documentation/index.md (0)
R old-site/documentation/jcloudsguides/index.md (0)
R old-site/documentation/quickstart/abiquo.md (0)
R old-site/documentation/quickstart/aws.markdown (0)
R old-site/documentation/quickstart/azure-storage.markdown (0)
R old-site/documentation/quickstart/bluelock.markdown (0)
R old-site/documentation/quickstart/chef.md (0)
R old-site/documentation/quickstart/cloudsigma.markdown (0)
R old-site/documentation/quickstart/ebs.md (0)
R old-site/documentation/quickstart/filesystem.md (0)
R old-site/documentation/quickstart/go-grid.markdown (0)
R old-site/documentation/quickstart/hpcloud.markdown (0)
R old-site/documentation/quickstart/index.md (0)
R old-site/documentation/quickstart/openstack.markdown (0)
R old-site/documentation/quickstart/rackspace.markdown (0)
R old-site/documentation/quickstart/sqs.md (0)
R old-site/documentation/quickstart/terremark-ecloud.markdown (0)
R old-site/documentation/quickstart/terremark-vcloud-express.markdown (0)
R old-site/documentation/quickstart/virtualbox.md (0)
R old-site/documentation/reference/apps-that-use-jclouds.markdown (0)
R old-site/documentation/reference/async.md (0)
R old-site/documentation/reference/columnar-datadesign.markdown (0)
R old-site/documentation/reference/compute-design.markdown (0)
R old-site/documentation/reference/error-handling.md (0)
R old-site/documentation/reference/index.md (0)
R old-site/documentation/reference/jclouds-api.markdown (0)
R old-site/documentation/reference/jclouds-logging.markdown (0)
R old-site/documentation/reference/load-balancer-design.markdown (0)
R old-site/documentation/reference/location-metadata-design.markdown (0)
R old-site/documentation/reference/oauth.markdown (0)
R old-site/documentation/reference/osgi.markdown (0)
R old-site/documentation/reference/pool-design.markdown (0)
R old-site/documentation/reference/rationale-design.markdown (0)
R old-site/documentation/reference/runscript-design.markdown (0)
R old-site/documentation/reference/supported-providers.markdown (0)
R old-site/documentation/reference/using-provider-metadata.markdown (0)
R old-site/documentation/reference/vmware-vsphere-design.markdown (0)
R old-site/documentation/releasenotes/1.1.0.md (0)
R old-site/documentation/releasenotes/1.1.1.md (0)
R old-site/documentation/releasenotes/1.2.0-output/aws-cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/aws-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/aws-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/azureblob.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/bluelock-vcloud-zone01.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudfiles-uk.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudfiles-us.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudloadbalancers-us.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudonestorage-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudonestorage.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/elastichosts-lon-b.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/elastichosts-lon-p-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/elastichosts-lon-p.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/elastichosts-sat-p-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/elastichosts-sat-p.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/eucalyptus-partnercloud-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/eucalyptus-partnercloud-ec2.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/eucalyptus-partnercloud-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/eucalyptus-partnercloud-s3.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/go2cloud-jhb1.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/gogrid.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/greenhousedata-element-vcloud.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/ninefold-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/ninefold-storage.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/openhosting-east1.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/rimuhosting-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/rimuhosting.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/savvis-symphonyvpdc-failed.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/savvis-symphonyvpdc.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/serverlove-z1-man.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/skalicloud-sdg-my.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/slicehost-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/slicehost.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/softlayer.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/stratogen-vcloud-mycloud-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/stratogen-vcloud-mycloud.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/synaptic-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/synaptic-storage.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/trmk-ecloud-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/trmk-ecloud.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/trmk-vcloudexpress-failures.txt (0)
R old-site/documentation/releasenotes/1.2.0-output/trmk-vcloudexpress.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/swift-failures.txt (0)
R old-site/documentation/releasenotes/1.2.1-output/swift.txt (0)
R old-site/documentation/releasenotes/1.2.2-output/aws-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.2.2-output/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.2.2-output/gogrid.txt (0)
R old-site/documentation/releasenotes/1.2.2.md (0)
R old-site/documentation/releasenotes/1.2.md (0)
R old-site/documentation/releasenotes/1.3.0-output/aws-cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/azureblob.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/bluelock-vcloud-zone01.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudfiles-uk.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudfiles-us-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudfiles-us.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudloadbalancers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudloadbalancers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudonestorage-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudonestorage.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudstack-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/cloudstack.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/elastichosts-lax-p.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/elastichosts-lon-b.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/elastichosts-lon-p.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/elastichosts-sat-p.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/elastichosts-tor-p.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/eucalyptus-partnercloud-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/eucalyptus-partnercloud-ec2.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/eucalyptus-partnercloud-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/go2cloud-jhb1-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/go2cloud-jhb1.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/gogrid-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/gogrid.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/greenhousedata-element-vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/greenhousedata-element-vcloud.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/hpcloud-objectstorage-lvs.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/ninefold-compute.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/ninefold-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/ninefold-storage.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/openhosting-east1-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/openhosting-east1.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/rimuhosting-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/rimuhosting.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/savvis-symphonyvpdc-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/savvis-symphonyvpdc.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/serverlove-z1-man.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/skalicloud-sdg-my-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/skalicloud-sdg-my.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/slicehost-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/slicehost.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/softlayer.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/stratogen-vcloud-mycloud-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/stratogen-vcloud-mycloud.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/swift.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/synaptic-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/synaptic-storage.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/trmk-ecloud-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/trmk-ecloud.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/trmk-vcloudexpress-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/trmk-vcloudexpress.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.3.0-output/vcloud.txt (0)
R old-site/documentation/releasenotes/1.3.md (0)
R old-site/documentation/releasenotes/1.4.0/aws-cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.4.0/aws-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.4.0/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.4.0/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/azureblob.txt (0)
R old-site/documentation/releasenotes/1.4.0/bluelock-vcloud-zone01-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/bluelock-vcloud-zone01.txt (0)
R old-site/documentation/releasenotes/1.4.0/byon-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/byon.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudfiles-uk.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudfiles-us-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudfiles-us.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudloadbalancers-uk.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudloadbalancers-us.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudonestorage-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudonestorage.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudstack-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/cloudstack.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-lax-p-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-lax-p.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-lon-b.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-lon-p.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-sat-p-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-sat-p.txt (0)
R old-site/documentation/releasenotes/1.4.0/elastichosts-tor-p.txt (0)
R old-site/documentation/releasenotes/1.4.0/eucalyptus-partnercloud-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/eucalyptus-partnercloud-ec2.txt (0)
R old-site/documentation/releasenotes/1.4.0/eucalyptus-partnercloud-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/eucalyptus-partnercloud-s3.txt (0)
R old-site/documentation/releasenotes/1.4.0/go2cloud-jhb1-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/go2cloud-jhb1.txt (0)
R old-site/documentation/releasenotes/1.4.0/gogrid-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/gogrid.txt (0)
R old-site/documentation/releasenotes/1.4.0/greenhousedata-element-vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/greenhousedata-element-vcloud.txt (0)
R old-site/documentation/releasenotes/1.4.0/hpcloud-objectstorage-lvs.txt (0)
R old-site/documentation/releasenotes/1.4.0/ninefold-compute-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/ninefold-compute.txt (0)
R old-site/documentation/releasenotes/1.4.0/ninefold-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/ninefold-storage.txt (0)
R old-site/documentation/releasenotes/1.4.0/nova-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/nova.txt (0)
R old-site/documentation/releasenotes/1.4.0/openhosting-east1-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/openhosting-east1.txt (0)
R old-site/documentation/releasenotes/1.4.0/rimuhosting-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/rimuhosting.txt (0)
R old-site/documentation/releasenotes/1.4.0/serverlove-z1-man.txt (0)
R old-site/documentation/releasenotes/1.4.0/skalicloud-sdg-my-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/skalicloud-sdg-my.txt (0)
R old-site/documentation/releasenotes/1.4.0/slicehost-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/slicehost.txt (0)
R old-site/documentation/releasenotes/1.4.0/softlayer-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/softlayer.txt (0)
R old-site/documentation/releasenotes/1.4.0/stratogen-vcloud-mycloud-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/stratogen-vcloud-mycloud.txt (0)
R old-site/documentation/releasenotes/1.4.0/swift-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/swift.txt (0)
R old-site/documentation/releasenotes/1.4.0/synaptic-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/synaptic-storage.txt (0)
R old-site/documentation/releasenotes/1.4.0/trmk-ecloud-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/trmk-ecloud.txt (0)
R old-site/documentation/releasenotes/1.4.0/trmk-vcloudexpress-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/trmk-vcloudexpress.txt (0)
R old-site/documentation/releasenotes/1.4.0/vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.4.0/vcloud.txt (0)
R old-site/documentation/releasenotes/1.4.md (0)
R old-site/documentation/releasenotes/1.5-tests.md (0)
R old-site/documentation/releasenotes/1.5.0/abiquo-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/abiquo.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-cloudwatch-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-elb-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-elb.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-iam-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-iam.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-rds-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-rds.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-sqs-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/aws-sqs.txt (0)
R old-site/documentation/releasenotes/1.5.0/azure-management-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/azure-management.txt (0)
R old-site/documentation/releasenotes/1.5.0/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/azureblob.txt (0)
R old-site/documentation/releasenotes/1.5.0/bluelock-vcloud-zone01-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/bluelock-vcloud-zone01.txt (0)
R old-site/documentation/releasenotes/1.5.0/chef-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/chef.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles-uk.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles-us-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles-us.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudfiles.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers-uk.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers-us.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudloadbalancers.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudonestorage-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudonestorage.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudservers.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudstack-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudstack.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudwatch-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.5.0/ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/ec2.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lax-p-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lax-p.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lon-b-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lon-b.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lon-p-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-lon-p.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-sat-p-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-sat-p.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-tor-p-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elastichosts-tor-p.txt (0)
R old-site/documentation/releasenotes/1.5.0/elasticstack-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elasticstack.txt (0)
R old-site/documentation/releasenotes/1.5.0/elb-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/elb.txt (0)
R old-site/documentation/releasenotes/1.5.0/glesys-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/glesys.txt (0)
R old-site/documentation/releasenotes/1.5.0/go2cloud-jhb1-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/go2cloud-jhb1.txt (0)
R old-site/documentation/releasenotes/1.5.0/gogrid-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/gogrid.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenhousedata-element-vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenhousedata-element-vcloud.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenqloud-compute-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenqloud-compute.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenqloud-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/greenqloud-storage.txt (0)
R old-site/documentation/releasenotes/1.5.0/hostedchef-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/hostedchef.txt (0)
R old-site/documentation/releasenotes/1.5.0/hpcloud-compute-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/hpcloud-compute.txt (0)
R old-site/documentation/releasenotes/1.5.0/hpcloud-objectstorage-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/hpcloud-objectstorage.txt (0)
R old-site/documentation/releasenotes/1.5.0/iam-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/iam.txt (0)
R old-site/documentation/releasenotes/1.5.0/joyentcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/joyentcloud.txt (0)
R old-site/documentation/releasenotes/1.5.0/ninefold-compute-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/ninefold-compute.txt (0)
R old-site/documentation/releasenotes/1.5.0/ninefold-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/ninefold-storage.txt (0)
R old-site/documentation/releasenotes/1.5.0/openhosting-east1-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/openhosting-east1.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-keystone-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-keystone.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-nova-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-nova.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-swift-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/openstack-swift.txt (0)
R old-site/documentation/releasenotes/1.5.0/privatechef-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/privatechef.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudidentity-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudidentity.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudservers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/rackspace-cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.5.0/rds-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/rds.txt (0)
R old-site/documentation/releasenotes/1.5.0/rimuhosting-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/rimuhosting.txt (0)
R old-site/documentation/releasenotes/1.5.0/serverlove-z1-man-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/serverlove-z1-man.txt (0)
R old-site/documentation/releasenotes/1.5.0/skalicloud-sdg-my-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/skalicloud-sdg-my.txt (0)
R old-site/documentation/releasenotes/1.5.0/slicehost-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/slicehost.txt (0)
R old-site/documentation/releasenotes/1.5.0/softlayer-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/softlayer.txt (0)
R old-site/documentation/releasenotes/1.5.0/sqs-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/sqs.txt (0)
R old-site/documentation/releasenotes/1.5.0/stratogen-vcloud-mycloud-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/stratogen-vcloud-mycloud.txt (0)
R old-site/documentation/releasenotes/1.5.0/synaptic-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/synaptic-storage.txt (0)
R old-site/documentation/releasenotes/1.5.0/trmk-ecloud.txt (0)
A old-site/documentation/releasenotes/1.5.0/trmk-vcloudexpress-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/trmk-vcloudexpress.txt (0)
R old-site/documentation/releasenotes/1.5.0/trystack-nova-failures.txt (0)
R old-site/documentation/releasenotes/1.5.0/trystack-nova.txt (0)
R old-site/documentation/releasenotes/1.5.md (0)
R old-site/documentation/releasenotes/1.6-tests.md (0)
R old-site/documentation/releasenotes/1.6.0/atmos-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/atmos.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-ec2.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-route53-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-route53.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-s3.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-sqs-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-sqs.txt (0)
R old-site/documentation/releasenotes/1.6.0/aws-sts.txt (0)
R old-site/documentation/releasenotes/1.6.0/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/azureblob.txt (0)
R old-site/documentation/releasenotes/1.6.0/bluelock-vcloud-zone01-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/bluelock-vcloud-zone01.txt (0)
R old-site/documentation/releasenotes/1.6.0/byon-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/byon.txt (0)
R old-site/documentation/releasenotes/1.6.0/chef-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/chef.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudfiles.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudservers.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma-lvs-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma-lvs.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma-zrh-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma-zrh.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudsigma.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudstack-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudstack.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudwatch-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/cloudwatch.txt (0)
R old-site/documentation/releasenotes/1.6.0/dynect-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/dynect.txt (0)
R old-site/documentation/releasenotes/1.6.0/ec2-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/ec2.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lax-p-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lax-p.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lon-b-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lon-b.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lon-p-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-lon-p.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-sat-p-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-sat-p.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-tor-p-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elastichosts-tor-p.txt (0)
R old-site/documentation/releasenotes/1.6.0/elasticstack-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/elasticstack.txt (0)
R old-site/documentation/releasenotes/1.6.0/filesystem-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/filesystem.txt (0)
R old-site/documentation/releasenotes/1.6.0/glesys-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/glesys.txt (0)
R old-site/documentation/releasenotes/1.6.0/go2cloud-jhb1-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/go2cloud-jhb1.txt (0)
R old-site/documentation/releasenotes/1.6.0/gogrid-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/gogrid.txt (0)
R old-site/documentation/releasenotes/1.6.0/greenhousedata-element-vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/greenhousedata-element-vcloud.txt (0)
R old-site/documentation/releasenotes/1.6.0/hostedchef-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/hostedchef.txt (0)
R old-site/documentation/releasenotes/1.6.0/hpcloud-compute-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/hpcloud-compute.txt (0)
R old-site/documentation/releasenotes/1.6.0/hpcloud-objectstorage-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/hpcloud-objectstorage.txt (0)
R old-site/documentation/releasenotes/1.6.0/ninefold-compute.txt (0)
R old-site/documentation/releasenotes/1.6.0/ninefold-storage-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/ninefold-storage.txt (0)
R old-site/documentation/releasenotes/1.6.0/openhosting-east1-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/openhosting-east1.txt (0)
R old-site/documentation/releasenotes/1.6.0/openstack-keystone-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/openstack-keystone.txt (0)
R old-site/documentation/releasenotes/1.6.0/openstack-nova-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/openstack-nova.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudblockstorage-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudblockstorage-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudblockstorage-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudblockstorage-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-clouddns.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudidentity-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudidentity.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudloadbalancers.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudservers-uk-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudservers-uk.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudservers-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/rackspace-cloudservers-us.txt (0)
R old-site/documentation/releasenotes/1.6.0/route53-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/route53.txt (0)
R old-site/documentation/releasenotes/1.6.0/s3-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/s3.txt (0)
R old-site/documentation/releasenotes/1.6.0/serverlove-z1-man-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/serverlove-z1-man.txt (0)
R old-site/documentation/releasenotes/1.6.0/skalicloud-sdg-my-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/skalicloud-sdg-my.txt (0)
R old-site/documentation/releasenotes/1.6.0/softlayer-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/softlayer.txt (0)
R old-site/documentation/releasenotes/1.6.0/sqs-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/sqs.txt (0)
R old-site/documentation/releasenotes/1.6.0/sts-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/sts.txt (0)
R old-site/documentation/releasenotes/1.6.0/swift-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/swift.txt (0)
R old-site/documentation/releasenotes/1.6.0/trmk-ecloud-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/trmk-ecloud.txt (0)
R old-site/documentation/releasenotes/1.6.0/trmk-vcloudexpress-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/trmk-vcloudexpress.txt (0)
R old-site/documentation/releasenotes/1.6.0/ultradns-ws-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/ultradns-ws.txt (0)
R old-site/documentation/releasenotes/1.6.0/vcloud-failures.txt (0)
R old-site/documentation/releasenotes/1.6.0/vcloud.txt (0)
R old-site/documentation/releasenotes/1.6.1.md (0)
R old-site/documentation/releasenotes/1.6.2-tests.md (0)
R old-site/documentation/releasenotes/1.6.2.md (0)
R old-site/documentation/releasenotes/1.6.2/atmos-failures.txt (0)
R old-site/documentation/releasenotes/1.6.2/aws-s3-failures.txt (0)
R old-site/documentation/releasenotes/1.6.2/azureblob-failures.txt (0)
R old-site/documentation/releasenotes/1.6.2/cloudfiles-us-failures.txt (0)
R old-site/documentation/releasenotes/1.6.2/hostedchef-failures.txt (0)
R old-site/documentation/releasenotes/1.6.2/hpcloud-objectstorage-failures.txt (0)
R old-site/documentation/releasenotes/1.6.3.md (0)
R old-site/documentation/releasenotes/1.6.md (0)
R old-site/documentation/releasenotes/1.7.md (0)
R old-site/documentation/releasenotes/beta7.markdown (0)
R old-site/documentation/releasenotes/beta8.markdown (0)
R old-site/documentation/releasenotes/index.md (0)
R old-site/documentation/userguide/ant-compute.md (0)
A old-site/documentation/userguide/blobstore-guide.md (433)
R old-site/documentation/userguide/bug-report.md (0)
R old-site/documentation/userguide/compute.markdown (0)
R old-site/documentation/userguide/filesystem-provider.md (0)
R old-site/documentation/userguide/google-app-engine.md (0)
R old-site/documentation/userguide/index.md (0)
R old-site/documentation/userguide/init-builder.md (0)
R old-site/documentation/userguide/installation-guide.md (0)
R old-site/documentation/userguide/karaf.md (0)
R old-site/documentation/userguide/terremark.md (0)
R old-site/documentation/userguide/using-abiquo.md (0)
R old-site/documentation/userguide/using-ec2.md (0)
R old-site/documentation/userguide/using-maven.md (0)
R old-site/documentation/userguide/using-s3.md (0)
R old-site/documentation/userguide/vmware-vcloud-director.md (0)
R old-site/documentation/userguide/vmware-vcloud.md (0)
A old-site/index.md (4)
R old-site/licenses/cla-corporate.txt (0)
R old-site/licenses/icla.txt (0)
R old-site/style/favicon.ico (0)
A old-site/style/feather-small.gif (0)
A old-site/style/fullsizejcloudslogo.jpg (0)
R old-site/style/jcloudslogo.jpg (0)
R old-site/style/style.css (0)
A old-site/style/syntax.css (61)
-- Patch Links --
https://github.com/jclouds/jclouds-site/pull/51.patch
https://github.com/jclouds/jclouds-site/pull/51.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <no...@github.com>.
I don't understand why it's difficult to keep the existing slogan. It should just be a matter of not changing the slogan...
Then just have the one download link, the others later on are fine without having the download link.
What about tablets that are requesting the full site? The 4 column format is typically *not* used on sites for that purpose, it makes it difficult to read on a 7" screen.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31812147
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #186](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/186/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35236133
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
>I tried to fix it with permalink in _config.yml but it broke other stuff. Didn't have time to look into it any deeper.
Yeah, I also tried that but I couldn't configure it without breaking the links in all other pages :( Don't know if that can be done in an elegant way...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33771665
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
I'd rather open them in the same page. I find particularly annoying when links are opened in a new tab/window (you have no choice), when it is quite an easy thing to do with a middle/right click.
It is just a matter of taste, so I'll change it if there is a preference to open external links in a new tab/window.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33345772
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
Agreed that footer doesn't look so great. More columns would be better and moving the Apache stuff more to the right or even below might look better. What else should we put in the footer?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32317015
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> Migrated release notes
Looks great! Thanks, @nacx!
Just a thought: would it make sense to have the Javadocs opening in a new tab/window?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33331747
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@demobox I use the [RSS Subscription Extension (by Google)](https://chrome.google.com/webstore/detail/rss-subscription-extensio/nlbjncdgjeocebhnmkbbbdekmmmcbfjd) for that in Chrome. Once it's installed you'll see it in the Location Bar (for sites that have feeds).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33822367
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Inbar Stolberg <in...@gmail.com>.
I know i am a noob in the forom but how about "cloud control/er"?
On Jan 10, 2014 10:35 AM, "Ignasi Barrera" <no...@github.com> wrote:
> Personally, I don't like putting an entire pom there, even if it's not too
> long. If some is using Maven and doesn't have the basic knowledge of the
> tool (and adding a dependency requires a very basic understanding of
> Maven), that's not something we should fix. Projects like [OkHttp](
> http://square.github.io/okhttp/) or [Spring Framework](
> http://projects.spring.io/spring-framework/) only show the dependency
> snippet (see the links). The setup guide remains clean and concise, and
> just focus in what matters to add the library to your project.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32010843
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Personally, I don't like putting an entire pom there, even if it's not too long. If some is using Maven and doesn't have the basic knowledge of the tool (and adding a dependency requires a very basic understanding of Maven), that's not something we should fix. Projects like [OkHttp](http://square.github.io/okhttp/) or [Spring Framework](http://projects.spring.io/spring-framework/) only show the dependency snippet (see the links). The setup guide remains clean and concise, and just focus in what matters to add the library to your project.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32010843
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #156](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/156/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31602396
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
CUSTOMERS -> USERS?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32221835
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
>"Rule the cloud" is a bit lame sounding to me, why not "Cloud interfaces, simplified" - this slogan does a great deal to invite people into something that appears complex to begin with.
I've been trying to put that slogan, but didn't succeed at using it and keeping a good-looking "introduction box". I'm not good at CSS, etc. If you really think that should be changed, I'd really appreciate your commit to change that by keeping a consistent and good-looking aspect! :)
>I think there are too many links, especially the download link being duplicated
Yes, it is duplicated, but I think having all main buttons in the main box is a good idea. I agree with @demobox that having a link/button just in the first place the eyes will go is a good idea. users shouldn't have to "find" the buttons. IMO the landing page should provide a clear access to every important page that helps users get started.
>The content at the bottom could be dynamically loaded on a mouse over to make it simpler
I like the idea of having all the content displayed and not relying on the user to "roll the mouse over somewhere" to display more content. A quick look should give a good overview of the project, and I think the current landing page doesn't have too much content to "scare" newcomers.
Also, what about tablets and mobile devices? Now the site can be displayed there too, and the look and feel is not too ugly (only the main logo being too big is what seems a bit ugly).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31811695
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@demobox I quite like the use of space at the top. It's nice and clean. We only want to convey one message in that spot because it's our most important message.
I also like having only the ComputeService and BlobStore examples. LoadBalancer isn't necessary here. Also when there are more abstractions we won't be able to fit them all anyway. Perhaps a single line underneath that says, "There are also views/abstractions/whatever for Loadbalancers (link) and the next one and the next one."
I'm not sure about success quotes either but I think we could do with cherry picking some great customer examples from [Apps that use jclouds](http://jclouds.apache.org/documentation/reference/apps-that-use-jclouds/). Showing apps that use jclouds can be an important deciding factor for devs.
I've got more to say and contribute but that's all I have time for now. I'll start tracking this branch tomorrow and making some commits/suggestions.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31692998
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
That's bizarre. My commit disappeared. It definitely happened as we can see from @demobox's screen shots.
@nacx Did you pull and rebase before your commit? Did you force push?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31799259
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> What's the width of your screen?
It's 1366px, but the browser window was indeed not full screen. If I fullscreen it, it's no longer balanced? And the provider logos still look a bit cramped (Chrome 31.0.1650.63 on Windows 7):
Fine with fixing text and links later, of course - just wondering if there was supposed to be a link there or not. That definitely should not hold us up from merging this, agreed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31786423
Re: [jclouds-site] Rebranding proposal (#51)
Posted by jclouds-commentator <no...@github.com>.
Go to http://12274602dbeae3380bb5-be7278d037edb25bb0775222ee3bf6f8.r80.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31790867
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> If your browser can detect feeds, they should show up however your browser detects them on any
> page.
Where would you see that in Chrome, if at all? The Atom files themselves look fine...thanks, @everett-toews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33818660
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #169](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/169/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32077857
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
I also like the horizontal footer. Great @everett-toews!
I've uploaded a small change/test to it: just changed the color of the links to a dark blue, as I think they look better with it, and removed the line separator between the links and the Apache disclaimer, as everything is part of the footer. Do you think it looks better like this or we'd better revert this last commit (it is just a test)?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32695643
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #182](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/182/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35177624
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Addressed your comments @demobox. Only left out the one about adding space between the main text and the buttons, as I've not been able to properly configure the paddings for the enclosing box properly. All yours if you wanna try! :)
I've separated a bit the logos, and added the "30 providers" to the main text, to show how much jclouds rocks :) Also changed the "title" of the last bottom box, to "Specific APIs", to avoid repeating the "many more" that comes after the logos.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750107
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Hmmm not sure. I've changed that locally, and it seems like too much. In the end it is only one short sentence describing the purpose of the project. We could end up emphasizing practically all words there. I think having only the "30 cloud providers" in bold is enough to make people be interested in reading more.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31751516
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
I like the balanced look. Wonder if we can add some more padding, though...and some more cloud next to the 's' of jclouds? It's currently this:
Perhaps something closer to this?
Also, the "...and many more!" changes colour on mouseover but isn't actually a link, which is a bit confusing. Is that intentional?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31782599
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #171](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/171/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32312666
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
I've also been thinking about what to put in the bottom-right side space that is now left blank. I thought about some "success case" quotes, but I don't have any.
Any proposal for what to put there?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31601875
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Thanks, Ignasi! I like it - also the section on abstractions at the bottom. Here I've just added some more cloud to the right of the 's' of 'jclouds', and added some spacing between logos and the 'Rule the clouds' sentence and the buttons:
Just wondering whether we could replace the "a variety of supported cloud providers" in
```
Apache jclouds® is a cloud agnostic library for the JVM that enables developers to access a variety of supported cloud providers using one API.
```
with something a little less modest? "Over 30 cloud providers" or so?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31728762
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrea Turli <no...@github.com>.
Thanks guys for your great job!
fwiw I think you can try http://getbootstrap.com/css/#overview-responsive-images for jclouds logo
as for example on my s3 this is what I can see:
http://goo.gl/xRTFK6
and also the buttons look confused
http://goo.gl/CE0CQU
HTH
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31911557
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
Simply balanced the provider images by putting 4 in each row. Mostly doing this to check that my tracking branch was working and I could commit changes.
@nacx Was there a design reason you had it with 5 in the first row and 3 in the second?
If so, I can revert this change.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31781945
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Thanks for the tip @andreaturli!
I've tried configuring the responsive image class locally, and it renders OK in my phone, but in the browser the logo gets smaller than the right box (t is slightly smaller right now). I haven't been able to properly configure the logo so it has the same size as the right box... Do you have any tip for that? :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31912598
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <no...@github.com>.
I would steer away from customers, it does imply some kind of payment.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32294975
Re: [jclouds-site] Rebranding proposal (#51)
Posted by jclouds-commentator <no...@github.com>.
Go to http://da90b45cfe2d67e57c09-d7a5dfd73341d723527b762b5e50da03.r15.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31891180
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
First of all, thanks for your feedback Matt!
Let's see then if @silkysun reads the GitHub mention notifications and can give some help here. Meanwhile, I think we should move forward and continue, and address this once we have someone with more web skill than I have involved in the rebranding.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31813439
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #165](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/165/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31981975
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
+1 on the full POM, too (thanks, @everett-toews!). One small comment: add `<?xml version="1.0" encoding="UTF-8"?>` as the first line? Or maybe that's in there, but just got cut from the screenshot?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32069823
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #153](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/153/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31591963
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #149](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/149/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31581927
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@nacx For the maven installation guide.
What do you think about making the top example a complete pom.xml file?
Then users could just copy/paste that in the download the binaries section.
Think about it from the perspective of a user who has no or limited experience with maven.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31993936
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
I've just pushed a change to replace the Abiquo logo (which looked blurred) by a better one. @everett-toews, I've pulled the changes, but in the last version the logos are not balanced. Did you revert that change?
Moving forward, I think once we are happy with the landing page, we should start rebranding the exisisting documents. Here is a list of my proposed steps to follow, in order to get everything done. Feel free to edit this comment and add everything you want:
**Getting started**
- [ ] Decide if we are happy with the current menu items.
- [ ] Create the *Getting started* index page, and link there from the main page appropriate buttons. (Ignasi)
- [ ] Rebrand the *What is jclouds* guide. (Ignasi)
- [ ] Rebrand the *Installation* guide. (Ignasi)
- [ ] Rebrand the *Compute* guide. (Ignasi)
- [ ] Rebrand the *BlobStore* guide.
- [ ] Create a *Download* page. Link there from the installation guide and all the *Download* buttons. (Ignasi)
**Documentation**
- [ ] Decide the items in the menu. Should link to more detailed guides.
- [ ] Decide which elements from the old site are kept and which ones are dropped.
- [ ] Migrate and rebrand the content to the new *documentation* folder.
**Community**
- [ ] Create the *community folder*, the index page and link there from the main page.
- [ ] Migrate and rebrand the content from the old site.
**Blog**
- [ ] Rebrand all the posts. (Ignasi)
**Release Notes**
- [ ] Create the *releasenotes* folder, the *Release Notes* index page and link there from the *Release archive* link.
- [ ] Migrate and rebrand all release notes.
When rebranding, we should take care of fixing all local links, as the directory structure for the documents has changed to be aligned with the main menu.
As part of the rebranding of each page, I plan to try to make documents more clear and understandable. Perhaps restructuring them, changing a few examples, etc. I don't think this should be out of the scope here (we want to get the new site live keeping the content; we can improve it later), but I'll try :)
So this is what comes to my mind when thinking about what I'd want to have before publishing the new site. WDYT?
If we are happy with the landing page, and the layout for the content pages (it has just the menu and the footer), we could start with this tasks and all that may be added (again, feel free to edit the comment). I've assigned some of the tasks to me, but just to avoid collisions (not sure if it's worth creating JIRA technical tasks; we can coordinate just here) feel free to change that too.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31791111
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Closed #51.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@nacx While I was doing this I noticed that the individual posts aren't under the blog dir like .../blog/2013/12/... They're actually under the root .../2013/12/...
I tried to fix it with permalink in _config.yml but it broke other stuff. Didn't have time to look into it any deeper.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33759811
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #166](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/166/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31984500
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
The footer should always give the user some options to do something. Give them somewhere to go or something to do when they get to the bottom of the page.
I know the menu follows them down the page but having that at the top of the page (and it could just be pancakes if they're on a mobile device) doesn't have the same impact as when they see the options laid out before them in the footer.
Obviously we could expand beyond just "Improve jclouds" but I wanted to get something out there to look at.
What do you think?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32221821
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
If your browser can detect feeds, they should show up however your browser detects them on any page.
Or they can be found at .../blog/atom.xml and .../releasenotes/atom.xml
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33759693
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Ooo...looking forward to the pull request builder!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750337
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #183](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/183/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35206154
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> Trying out a horizontal footer
I like it!
Perhaps bold or a little bigger? Or make the line between the "Users" section and the footer a little darker?
Thanks, @everett-toews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32669024
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Also like it, as the main focus is still in the dependency, which is practicaly the only content in the pom. +1 to this full pom! :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32068821
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@demobox
The reason I chose "customers" was because then the sections are "clouds", "code", and "customers" with a nice alliterative ring to it. I'm not married to it. "users" might be more appropriate in this case.
I think "Improve jclouds" is just fine. It's actionable without being too wordy.
Most footer links at the bottom of pages are vertical in a column-like layout. I think we can continue with that convention.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32293102
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
>Ah. That's it.
And that's why the jclouds-mirror closed the PR the first time, after deleting my commits to GitHUb :)
Agree on the Abiquo thing too, we should focus there in the apps or people that uses jclouds, and not how the supported providers use clouds internally.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31840026
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Nice!! Perhaps make "one" in `Apache jclouds® is a cloud agnostic library...` italic, bold or underlined?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750810
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
>Any reason to wait before all this is done before merging the landing page?
I think we should publish the new site "at once". Making an announce or letting newcomers see the new landing page but the old style in the other pages would cause confusion and give an impression of something "broken". I'd rather merge it once all pages have been re-styled.
I don't care about improving the docs in this phase. Just having the old docs rebranded should be enough. But thinking about the elements in the top menu should give us the pages we could drop (IMO all those about design decisions that are partially complete and all referring to specific jclouds 1.0 features that no longer make sense to explain). I think that cut can happen before merging.
My idea would be to ideally have everything rebranded in a week or two at most. It is not that difficult. Rebranding is easy as everything left is markdown.It will be just about replacing some h1 to h2, etc, to make the pages good looking, but in general I don't expect that to take much.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31792617
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <no...@github.com>.
consumers
Matt
On Tue, Jan 14, 2014 at 2:16 PM, Everett Toews <no...@github.com>wrote:
> I went with "USERS" as it's the most commonly used and well understood
> term.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32313630>
> .
>
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32314604
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #168](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/168/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31993486
Re: [jclouds-site] Rebranding proposal (#51)
Posted by jclouds-commentator <no...@github.com>.
Go to http://1a73a86bacb68f57e1f4-1d2274ed4bb3ccb0dc6e069c199dacba.r42.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750574
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@demobox I think the lack of padding might be a screen resolution issue. What's the width of your screen? My laptop is 1280x800 and everything fits in fine. The jclouds logo is a nice look square with equal padding on the left and right.
I think we're setup to have a pretty standard 970px layout, see [Grid Options](http://getbootstrap.com/css/#grid-options). That should give us enough space even on older systems with 1024x768.
@nacx Can you confirm that?
Also, don't worry about broken links and such for the moment. I would even say don't worry about the exact wording of stuff just yet either. We're just trying to get the design right at the moment. Then we can fix the wording and make sure all of the links and such work.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31785650
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #163](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/163/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31890249
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <ma...@mattstep.net>.
I think that the original slogan can be preserved with a minor amount of
effort. I'm still trying to find time to dig through the changes.
It looks like some work can also be done to clean up unused css. This
still feels like a wip and not quite clean enough to be in master.
On Jan 20, 2014 5:41 PM, "Andrew Phillips" <no...@github.com> wrote:
> > rule the cloud
>
> Any thoughts on that vs. "cloud, simplified"? Or is the latter still too
> long?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32814050
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> rule the cloud
Any thoughts on that vs. "cloud, simplified"? Or is the latter still too long?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32814050
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #158](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/158/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31727764
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #167](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/167/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31989976
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <no...@github.com>.
"Rule the cloud" is a bit lame sounding to me, why not "Cloud interfaces, simplified" - this slogan does a great deal to invite people into something that appears complex to begin with.
I think there are too many links, especially the download link being duplicated
The content at the bottom could be dynamically loaded on a mouse over to make it simpler
jclouds is daunting and complex, the website should try to attack this problem, visually
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31811411
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrea Turli <no...@github.com>.
+1
I think it would be interesting to evaluate something like this gist-it.appspot.com to embed a snippet of live (working!) code taken i.e. from jclouds-examples' pom.xml refactored as @everett-toews suggested.
Not sure about the graphical result of something like:
<script src="http://gist-it.appspot.com/http://github.com/jclouds/jclouds-examples/blob/master/compute-basics/pom.xml?slice=21:54;footer=0">
</script>
my 2 cents
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32069927
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
@demobox I've just pushed a change to show some of the supported providers in the landing page, to have an idea of what can be managed with jclouds. I think it looks nice.
Regarding the "Download/Browse/Join", the box is quite "big" to be merged in the one with the description. Do you think adding buttons near the "Learn more" one could be good? I really like having a big sentence that describes the project.
The second one, "Cloud interfaces, simplified", is there to show that with a common interface you can support the list of providers. Now that the images are there I think it makes sense, but anyway would you rather remove it?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31601837
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #176](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/176/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32663004
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #177](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/177/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32695654
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #154](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/154/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31601826
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
I'd really like to see a list of some of our users on the home page. A section right after the abstraction descriptions.
"Many projects and customers already depend on jclouds"
What are some of the ones we should use from [apps](http://jclouds.apache.org/documentation/reference/apps-that-use-jclouds/)?
How about?
1. Maginatics (/cc @andrewgaul)
1. Jenkins
1. GigaSpaces Cloudify
I'd like to get Twitter and RedHat in there but I'm not really familiar with how they're using it. Is anyone else?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31799494
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #160](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/160/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31781296
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Would it be possible to move the "Download/Browse/Join" box that now comes at the bottom of the page into the first box, next to the logo? Right now, the "Rule the cloud" and "Cloud interfaces, simplified" content feels like it's pretty much the same thing (a high-level description of the purpose of jclouds) - can we try to merge them?
And then we perhaps also don't have to go looking for an image of supported providers ;-) Or we could use the other half of the "supported providers" block for "who uses jclouds"..?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31601460
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
>@nacx Was there a design reason you had it with 5 in the first row and 3 in the second?
Nope :) Just liked it, but also like the balanced version
Regarding the resolution, I've tested full screen, in my laptop resolution (1440x900), and with 1024x728 and it renders properly without padding issues in all them.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31789080
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> I'm not married to it. "users" might be more appropriate in this case.
My motivation was mainly to avoid users thinking that jclouds is somehow paid-for software.
>
If you're thinking about something like Meetup then yes, agreed.
Although GitHub itself makes for a nice counterexample:
In the case of the jclouds site, it's just that the rest of the footer is quite distinctly horizontal (different from the Meetup example), which to me feels like it clashes visually:
I would prefer a GitHub-style layout, but also fine to start with this for now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32294585
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Closed #51.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> What do you think about making the top example a complete pom.xml file?
Or stay with a snippet in the guide, and add a "download a full example POM" link to a complete POM, as @everett-toews is suggesting?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31994743
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
I went with "USERS" as it's the most commonly used and well understood term.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32313630
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Also addressed @everett-toews's comment and removed the `null` from the blobstore code snippet.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750171
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #157](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/157/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31726853
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> Perhaps a single line underneath that says, "There are also views/abstractions/whatever for Loadbalancers (link)
> and the next one and the next one."
Agree. BlobStore and Compute are certainly the most important ones so far, and the symmetry is nice visually, too.
> I quite like the use of space at the top. It's nice and clean. We only want to convey one message in that spot
> because it's our most important message.
More space is certainly cleaner and nice. Agree also that we want to make sure our main message gets across. But at present I think we are displaying _two_ messages that are pretty similar, and are a bit short on links that actually indicate what a user can _do_.
I think these need to be visible in the first view - you shouldn't have to scroll down to get there. Perhaps just have "Download" and "Contribute" as extra buttons next to "Learn more", and move the "Action Menu" back down the page?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31697032
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #161](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/161/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31782049
Re: [jclouds-site] Rebranding proposal (#51)
Posted by jclouds-commentator <no...@github.com>.
Go to http://4a0e3d8b69ac040500e7-c1ea266519378f3e6713454c267a254e.r38.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35177668
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> What do you think?
I certainly like the idea of encouraging the reader to do something. Just wondering if we can make it a horizontal menu in some way, in keeping with most of the other menus and the general layout theme on the page?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32222090
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
@nacx It's more about a good developer experience with the recommended installation method. And because Maven is the first thing on the page, it's clearly the recommended installation method (as it should be). But a developer might not be familiar with Maven so we should consider going the extra mile to make sure they have a good first experience with jclouds.
I fiddled around with it a bit to see what it looks like and here's the result.
Snippet pom
Full pom
What I like about the Full pom is that it's a complete working pom.xml. Extremely easy to get started. Copy, paste, and go. A quick and easy start with jclouds is essential. It also encourages the use of a jclouds.version property. There have been a number of cases where users' deps get out of version sync. The jclouds.version property helps that problem.
What I dislike about the Full pom is that it's verbose. That first line is brutal. Other than that there's only a handful of lines before getting to the deps.
WDYT now that you can see them side by side?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32068241
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrea Turli <no...@github.com>.
Great job @nacx! It is really a good start!
I really like the template: clean and elegant! And links are more evident now!!
The main navigation bar is much better in my opinion and Getting started is a must-have!
I think we could still work on the landing page: I'd suggest to have a links to the current version, doc, github project and examples (similarly to bootstrap.com or playframework.com/) close to `Learn more` button.
We could also add a "carousel" of the company/projects that are using jclouds.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31588922
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #155](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/155/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31602234
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #162](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/162/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31790685
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #148](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/148/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31581773
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
I've never been too happy with snippets when it comes to Java and XML. Snippets have a way of frustrating new users because too much context/syntax/whatever is missing. It's just winds up being a really crappy first experience and there's a good chance they won't come back because of it. An because installation is such a crucial step in attracting new users we need to make it as painless as possible.
And a complete pom.xml won't burden intermediate/advanced users either in this case because there really isn't that much more XML needed. They'll know exactly what they need to copy out and move on quickly.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32000984
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> So this is what comes to my mind when thinking about what I'd want to have before publishing the new site. WDYT?
Any reason to wait before all this is done before merging the landing page? Obviously, if you think this can be finished relatively quickly, sure...but I think it would be great to have at least the new landing page up as soon as possible?
I know you already addressed this in your comment, but I think for the first rebranding phase it might be easier, as @everett-toews also suggested in previous comments about _this_ page, to do the style first, then work on the content. I suspect the latter may take a little longer to get right.
Which, of course, doesn't mean that we should neglect it! But that I think the project can benefit a lot from simply having the existing data presented in the new style.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31792081
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #184](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/184/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35219399
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Thanks for all the effort here, first of all! About the top block: I still think we're using a lot of space here
to convey essentially one message: that you have an abstraction to manage multiple cloud providers and APIs. How about something like a cleaned-up version of this?
We're also not mentioning the loadbalancer abstraction, I note? Agree that it's not as relevant as BlobStore and Compute, but for completeness I guess we should mention it?
Not sure about "success quotes" - they're good for managers but I think less convincing for developers. Well-known projects that use jclouds are better for that, I would assume?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31602358
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #151](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/151/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31590967
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Thanks for the feedback!
I've just pushed a commit that tries to address all the comments: I've moved the links at the bottom near to the "Learn More" button. Now those are buttons too. I've tried different color configurations and this one is the one that (to me :)) looked more clean.
I've also removed the "Cloud interfaces simplified" sentence, to eliminate the duplicate message, and changed the bottom part to briefly describe the existing abstractions and mention that there are more cool things too.
Let's see how it looks once the commentator publishes the changes!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31726508
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
I did pull&rebase and your commit wasn't there. Did you push to GitHub or
to ASF? You have to push to ASF or the mirror job will remove your commit
from GitHub!
I like that TOC too.
Regarding the apps, Abiquo based clouds use jclouds to enable hybrid cloud
models and Chef to provide configuration management to the deployed nodes.
Perhaps it's worth a mention too.
El 08/01/2014 02:58, "Everett Toews" <no...@github.com> escribió:
> I'd really like to see a list of some of our users on the home page. A
> section right after the abstraction descriptions.
>
> "Many projects and customers already depend on jclouds"
>
> What are some of the ones we should use from apps<http://jclouds.apache.org/documentation/reference/apps-that-use-jclouds/>
> ?
>
> How about?
>
> 1. Maginatics (/cc @andrewgaul <https://github.com/andrewgaul>)
> 2. Jenkins
> 3. GigaSpaces Cloudify
>
> I'd like to get Twitter and RedHat in there but I'm not really familiar
> with how they're using it. Is anyone else?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31799494>
> .
>
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31810757
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
On Jan 8, 2014, at 1:28 AM, Ignasi Barrera wrote:
> I did pull&rebase and your commit wasn't there. Did you push to GitHub or
> to ASF? You have to push to ASF or the mirror job will remove your commit
> from GitHub!
Ah. That's it.
> Regarding the apps, Abiquo based clouds use jclouds to enable hybrid cloud
> models and Chef to provide configuration management to the deployed nodes.
> Perhaps it's worth a mention too.
It is. But then we would have repetition between the providers and customers, which would look kind of weird IMO.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31836334
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #170](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/170/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32220826
Re: [jclouds-site] Rebranding proposal (#51)
Posted by jclouds-commentator <no...@github.com>.
Go to http://92ca4a45ce4bc2fd3a2c-7346364addb59037702b9e407e081506.r2.cf1.rackcdn.com/ to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35206218
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #152](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/152/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31591538
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
The difficulty resides in keeping the consistent style. The "cloud interfaces, simplified" slogan does not fit in one single line, and if you put it in two lines, the "gray box" with the introduction message gets bigger than the logo. I've been struggling to make it keep the same size, but hasn't succeeded, and also tried to align the logo (even if smaller than the right box) to the box, but haven't succeeded and keeping all aligned and all sizes balanced.
I really encourage you to try make the change and commit it. I also like the original slogan, so if you manage to bring it back, keeping the nice aspect of the page, that would be really appreciated! Wanna help?
Regarding the tablets, I was not talking about the size. we still have no focus on making the site render properly there. Just have the new layout and migrate the docs. Just wanted to show that the "rollover" thing has implications. Also, I prefer having all the information visible, without having to move the mouse over a page. Just scroll down the page and you'll find everything, using the mouse wheel, without having to "put the mouse over that small title there" to show its description. This is also a tendency. Many sites now that go for a "single page" based on scrolling, put all the content visible and accessible, and they really look nice. I like that. Anyway, would like to see the opinion of other members of the community on this.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31812479
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Matt Stephenson <no...@github.com>.
Consider reaching out to @silkysun for both of those, she did the CSS on the current site and has some opinions on layout typically. I will have time to play with it in February, but this is bad timing for me right now.
> On Jan 8, 2014, at 12:13 AM, Ignasi Barrera <no...@github.com> wrote:
>
> The difficulty resides in keeping the consistent style. The "cloud interfaces, simplified" slogan does not fit in one single line, and if you put it in two lines, the "gray box" with the introduction message gets bigger than the logo. I've been struggling to make it keep the same size, but hasn't succeeded, and also tried to align the logo (even if smaller than the right box) to the box, but haven't succeeded and keeping all aligned and all sizes balanced.
>
> I really encourage you to try make the change and commit it. I also like the original slogan, so if you manage to bring it back, keeping the nice aspect of the page, that would be really appreciated! Wanna help?
>
> Regarding the tablets, I was not talking about the size. we still have no focus on making the site render properly there. Just have the new layout and migrate the docs. Just wanted to show that the "rollover" thing has implications. Also, I prefer having all the information visible, without having to move the mouse over a page. Just scroll down the page and you'll find everything, using the mouse wheel, without having to "put the mouse over that small title there" to show its description. This is also a tendency. Many sites now that go for a "single page" based on scrolling, put all the content visible and accessible, and they really look nice. I like that. Anyway, would like to see the opinion of other members of the community on this.
>
> —
> Reply to this email directly or view it on GitHub.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31813033
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #187](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/187/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-35236387
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
+1 to everything (well almost everything) @nacx said here.
This kind of rebranding needs to be a big bang type change. It should be done all at once.
The only thing we should do differently is improve the Installation page. Hopefully we'll get some traffic as a result of just announcing the new site. We should have a streamlined installation page ready for that.
Here's a TOC for what I would like to see on the installation page.
1. Maven
1. Getting the Binaries Using Maven
1. Adding jclouds to Your Maven Project
1. Adding jclouds Snapshot (Daily) Builds to Your Maven Project
1. Ant
1. Getting the Binaries Using Ant
1. Adding jclouds to Your Ant Project
1. Adding jclouds Snapshot (Daily) Builds to Your Ant Project
1. Clojure
1. Getting the Binaries Using lein
1. Adding jclouds to Your Clojure Project Using leiningen
1. Adding jclouds Snapshot (Daily) Builds to Your Clojure Project Using leiningen
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31799239
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #179](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/179/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33758934
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrea Turli <no...@github.com>.
Unfortunately I'm not an expert but I guess it is related to http://net.tutsplus.com/tutorials/html-css-techniques/mobile-first-with-bootstrap-3/
I don't think it is critical, but let's keep it in mind.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31913178
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Reopened #51.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Ignasi Barrera <no...@github.com>.
Personally I think *users* is the more appropriate here. They're not customers (as they don't pay) nor clients (which sounds quite impersonal), and we don't know if they are champions :) I think "users" is the best term here.
Regarding the footer I like the idea, but I'm not sure about the implementation. At a first look it seems that the main footer (the one with the disclaimer) is not centered and seems to be "moved" by the "links box" due to some bad arrangement of the footer. Perhaps adding some more link columns could make it look a bit better?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32316238
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> Once it's installed you'll see it in the Location Bar (for sites that have feeds).
OK, thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-33822628
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Gaul <no...@github.com>.
+1, a vast improvement over our existing web site. Can we reflow the page better for smaller-width browsers? My 1045 pixel width reflows the jclouds logo and "rule the cloud" awkwardly. Also please change the copyright year to 2014.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32813724
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Becca Wood <no...@github.com>.
Patrons, sponsors, clients, champions?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32300867
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> And a complete pom.xml won't burden intermediate/advanced users either in this case because there really isn't
> that much more XML needed.
Any particular minimal sample you have in mind? I guess it'll be easier to discuss "full vs. snippet" if it's clear how big (or not!) the difference actually is. Not that that's the only criterion, obviously.
I personally don't find simply the list of required dependencies that bad, but I guess that also springs from a different expectation in terms of Maven experience of a user who comes to the "Using jclouds with Maven" page. Do we have any data on how much/little experience most people there have?
Certainly, a recent user group question about the jclouds and Ant guide indicates that visitors can be pretty new to the build tool, too.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32001237
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> "Rule the cloud" is a bit lame sounding to me, why not "Cloud interfaces, simplified"
How about "Cloud, simplified". Would that fit?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31992975
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Everett Toews <no...@github.com>.
One more quick note, the null in the BlobStore example looks nasty. Is there something more appropriate we can put in there?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31693102
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
> I think having only the "30 cloud providers" in bold is enough to make people be interested in reading more.
Also works for me. Good to know we've tried it to see what it looks like ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31752377
Re: [jclouds-site] Rebranding proposal (#51)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-site-pull-requests #159](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/159/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31750350
Re: [jclouds-site] Rebranding proposal (#51)
Posted by Andrew Phillips <no...@github.com>.
Just to show these two side by side:
and
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/51#issuecomment-32710665