You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by andreaturli <gi...@git.apache.org> on 2014/09/09 16:27:22 UTC
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
GitHub user andreaturli opened a pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6
BROOKLYN-55
* simplify the deployment of the site to apache.org
* restructure a bit installation and getting started guide
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andreaturli/incubator-brooklyn-site brooklyn-55
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn-site/pull/6.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6
----
commit 611cb4581f3bece9058088e3247f8d64f3f19b3d
Author: Andrea Turli <an...@gmail.com>
Date: 2014-09-09T14:25:30Z
simplify the deployment of the site to apache.org
restructure a bit installation and getting started guide
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#issuecomment-54978225
Can you split the content changes and the deployment script changes into two different PRs please - they should not be related and need to be reviewed separately.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#issuecomment-54993246
Thanks @richardcloudsoft for the great review and comments
I'll close this PR and try to re-visit my changes on a different PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#issuecomment-54989293
Thanks for the PR Andrea - sorry that I have had to make quite a few comments on it. It seems to be performing several different changes - changing the nav categories, renaming pages, adding content - that should have been split into different commits. It also seems to be going beyond the scope of BROOKLYN-55 which was to add details of server installation, so I think that the changes unrelated to BROOKLYN-55 should have been in a different PR.
Specifically regarding BROOKLYN-55, I don't think that the content changes have fully addressed the bug report. A server installation is different to a desktop installation (and the desktop installation should be satisfactorily described [on the current site](https://brooklyn.incubator.apache.org/quickstart/index.html)) and that page needs to cover things like making sure that the install is remotely and securely accessible, and how to start Brooklyn in such a way that it doesn't terminate when you log out of the server.
I would suggest that you re-visit the server install page content, and add it as a child of the "documentation" navigation group.
The other changes you made to the navigation and them home page can certainly be considered - they are *not* sacred! - but they need to be justified and I would not merge them until they have been reviewed by at least two people. Adding content, however, is a much simpler review process, and it can be reviewed and published to the website in little time, which is why I strongly recommend that the changes are separated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17306767
--- Diff: quickstart/index.md ---
@@ -1,179 +1,34 @@
---
-title: Getting Started
layout: normal
-children:
-- { path: quickstart/policies-and-catalogs.md }
+title: Getting Started with Apache Brooklyn®
---
-This guide will walk you through deploying an application to a public cloud.
-
-We will be deploying an example 3-tier web application, described using this blueprint:
-
-{% highlight yaml %}
-{% readj _my-web-cluster.yaml %}
-{% endhighlight %}
-
-(This is written in YAML, following the [camp specification](https://www.oasis-open.org/committees/camp/). )
-
-
-## Install Brooklyn
-
-Download the [Brooklyn distribution]({{ site.data.brooklyn.url.dist.tgz }}) and expand it to your home directory ( `~/` ), or in a location of your choice. (Other [download options]({{site.url}}/download.html) are available.)
-
-{% if brooklyn_version contains 'SNAPSHOT' %}
-Expand the `tar.gz` archive (note: as this is a -SNAPSHOT version, your filename will be slightly different):
-{% else %}
-Expand the `tar.gz` archive:
-{% endif %}
-
-{% if brooklyn_version contains 'SNAPSHOT' %}
-{% highlight bash %}
-$ tar -zxf brooklyn-dist-{{ site.data.brooklyn.version }}-timestamp-dist.tar.gz
-{% endhighlight %}
-{% else %}
-{% highlight bash %}
-$ tar -zxf brooklyn-dist-{{ site.data.brooklyn.version }}-dist.tar.gz
-{% endhighlight %}
-{% endif %}
-
-This will create a `brooklyn-{{ site.data.brooklyn.version }}` folder.
-
-Note: You'll need a Java JRE or SDK installed (version 6 or later), as Brooklyn is Java under the covers.
-
-## Launch Brooklyn
-
-Let's setup some paths for easy commands.
-
-(Click the clipboard on these code snippets for easier c&p.)
-
-{% highlight bash %}
-$ cd brooklyn-{{ site.data.brooklyn.version }}
-$ BROOKLYN_DIR="$(pwd)"
-$ export PATH=$PATH:$BROOKLYN_DIR/bin/
-{% endhighlight %}
-
-We can do a quick test drive by launching Brooklyn:
-
-{% highlight bash %}
-$ brooklyn launch
-{% endhighlight %}
-
-Brooklyn will output the address of the management interface:
-
-
-`INFO Starting brooklyn web-console on loopback interface because no security config is set`
-
-`INFO Started Brooklyn console at http://127.0.0.1:8081/, running classpath://brooklyn.war and []`
-
-But before we really use Brooklyn, we need to setup some Locations.
-
-Stop Brooklyn with ctrl-c.
-
-## Configuring a Location
-
-Brooklyn deploys applications to Locations.
-
-Locations can be clouds, machines with fixed IPs or localhost (for testing).
-
-Brooklyn loads Location configuration from `~/.brooklyn/brooklyn.properties`.
-
-Create a `.brooklyn` folder in your home directory and download the template [brooklyn.properties](brooklyn.properties) to that folder.
-
-{% highlight bash %}
-$ mkdir ~/.brooklyn
-$ cd ~/.brooklyn
-$ wget {{site.url}}/quickstart/brooklyn.properties
-{% endhighlight %}
-
-Open brooklyn.properties in a text editor and add your cloud credentials.
-
-If you would rather test Brooklyn on localhost, follow [these instructions]({{ site.data.brooklyn.url.userguide }}/use/guide/locations/) to ensure that your Brooklyn can access your machine.
-
-Restart Brooklyn:
-
-{% highlight bash %}
-$ brooklyn launch
-{% endhighlight %}
-
-## Launching an Application
-
-There are several ways to deploy a YAML blueprint (including specifying the blueprint on the command line or submitting it via the REST API).
-
-For now, we will simply copy-and-paste the raw YAML blueprint into the web console.
-
-Open the web console ([127.0.0.1:8081](http://127.0.0.1:8081)). As Brooklyn is not currently managing any applications the 'Create Application' dialog opens automatically. Select the YAML tab.
-
-
-
-
-### Chose your Cloud / Location
-
-Edit the 'location' parameter in the YAML template (repeated below) to use the location you configured.
-
-For example, replace:
-{% highlight yaml %}
-location: location
-{% endhighlight %}
-
-with (one of):
-{% highlight yaml %}
-location: aws-ec2:us-east-1
-location: rackspace-cloudservers-us:ORD
-location: google-compute-engine:europe-west1-a
-location: localhost
-{% endhighlight %}
-
-**My Web Cluster Blueprint**
-
-{% highlight yaml %}
-{% readj _my-web-cluster.yaml %}
-{% endhighlight %}
-
-Paste the modified YAML into the dialog and click 'Finish'.
-The dialog will close and Brooklyn will begin deploying your application.
-
-Your application will be shown as 'Starting' on the web console's front page.
-
-
-
-
-## Monitoring and Managing Applications
-
-Click on the application name, or open the Applications tab.
-
-We can explore the management hierarchy of the application, which will show us the entities it is composed of.
-
- * My Web Cluster (A `BasicApplication`)
- * My DB (A `MySqlNode`)
- * My Web (A `ControlledDynamicWebAppCluster`)
- * Cluster of JBoss7 Servers (A `DynamicWebAppCluster`)
- * NginxController (An `NginxController`)
-
-
-
-Clicking on the 'My Web' entity will show the Summary tab. Here we can see if the cluster is ready to serve and, when ready, grab the web address for the front of the loadbalancer.
-
-
-
-
-The Activity tab allows us to drill down into what activities each entity is currently doing or has recently done. It is possible to drill down to all child tasks, and view the commands issued, and any errors or warnings that occured.
-
-Drill into the 'My DB' start operation. Working down through 'Start (processes)', then 'launch', we can discover the ssh command used including the stdin, stdout and stderr.
-
-[](images/my-db-activities-large.png)
-
-
-## Stopping the Application
-
-To stop an application, select the application in the tree view (the top/root entity), click on the Effectors tab, and invoke the 'Stop' effector. This will cleanly shutdown all components in the application and return any cloud machines that were being used.
-
-[](images/my-web-cluster-stop-confirm-large.png)
-
-
-### Next
-
-So far we have touched on Brooklyn's ability to *deploy* an application blueprint to a cloud provider, but this a very small part of Brooklyn's capabilities!
-
-Brooklyn's real power is in using Policies to automatically *manage* applications. There is also the (very useful) ability to store a catalog of application blueprints, ready to go.
-
-[Getting Started - Policies and Catalogs](policies-and-catalogs.html)
+<table class="table table-striped table-hover">
+<tbody>
+<tr>
+ <td><span class="glyphicon glyphicon-cloud text-primary"></span>
+ <a href="/what-is-brooklyn/">What is Brooklyn?</a></td>
--- End diff --
Avoid the use of links starting "/" - either use strictly relative links (`../what-is-brooklyn/`) - or reference site.url (`{{site.url}}/what-is-brooklyn/`). Using a leading slash causes links to break when the website is rendered to a non-root location, such as when testing using file:/// URLs or deploying to a temporary web server. (This would explain why you said that the `build-preview` output was not working for you.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17306290
--- Diff: index.md ---
@@ -3,13 +3,13 @@ layout: homepage
title: Home
navgroup: home
children:
-- { path: learnmore.md }
+- { path: what-is-brooklyn.md }
- { path: download.md }
- { path: quickstart/index.md }
- { path: documentation.md }
- { path: community/index.md }
navgroups:
-- { id: learnmore, page: learnmore.md, title: learn more }
+- { id: what-is-brooklyn, page: what-is-brooklyn.md, title: What is Brooklyn }
--- End diff --
Stylistic convention for the navbar and call-to-action buttons is to use lower case, in line with the "brooklyn" logo
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17306018
--- Diff: index.md ---
@@ -3,13 +3,13 @@ layout: homepage
title: Home
navgroup: home
children:
-- { path: learnmore.md }
+- { path: what-is-brooklyn.md }
--- End diff --
Could you explain why you chose to rename this section? The top-level nav names were chosen after careful consideration and review of other open source project websites. I'm not ruling out a change, of course, but I would like to get wider agreement first.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307779
--- Diff: quickstart/index.md ---
@@ -1,179 +1,34 @@
---
-title: Getting Started
layout: normal
-children:
-- { path: quickstart/policies-and-catalogs.md }
+title: Getting Started with Apache Brooklyn®
---
-This guide will walk you through deploying an application to a public cloud.
-
-We will be deploying an example 3-tier web application, described using this blueprint:
-
-{% highlight yaml %}
-{% readj _my-web-cluster.yaml %}
-{% endhighlight %}
-
-(This is written in YAML, following the [camp specification](https://www.oasis-open.org/committees/camp/). )
-
-
-## Install Brooklyn
-
-Download the [Brooklyn distribution]({{ site.data.brooklyn.url.dist.tgz }}) and expand it to your home directory ( `~/` ), or in a location of your choice. (Other [download options]({{site.url}}/download.html) are available.)
-
-{% if brooklyn_version contains 'SNAPSHOT' %}
-Expand the `tar.gz` archive (note: as this is a -SNAPSHOT version, your filename will be slightly different):
-{% else %}
-Expand the `tar.gz` archive:
-{% endif %}
-
-{% if brooklyn_version contains 'SNAPSHOT' %}
-{% highlight bash %}
-$ tar -zxf brooklyn-dist-{{ site.data.brooklyn.version }}-timestamp-dist.tar.gz
-{% endhighlight %}
-{% else %}
-{% highlight bash %}
-$ tar -zxf brooklyn-dist-{{ site.data.brooklyn.version }}-dist.tar.gz
-{% endhighlight %}
-{% endif %}
-
-This will create a `brooklyn-{{ site.data.brooklyn.version }}` folder.
-
-Note: You'll need a Java JRE or SDK installed (version 6 or later), as Brooklyn is Java under the covers.
-
-## Launch Brooklyn
-
-Let's setup some paths for easy commands.
-
-(Click the clipboard on these code snippets for easier c&p.)
-
-{% highlight bash %}
-$ cd brooklyn-{{ site.data.brooklyn.version }}
-$ BROOKLYN_DIR="$(pwd)"
-$ export PATH=$PATH:$BROOKLYN_DIR/bin/
-{% endhighlight %}
-
-We can do a quick test drive by launching Brooklyn:
-
-{% highlight bash %}
-$ brooklyn launch
-{% endhighlight %}
-
-Brooklyn will output the address of the management interface:
-
-
-`INFO Starting brooklyn web-console on loopback interface because no security config is set`
-
-`INFO Started Brooklyn console at http://127.0.0.1:8081/, running classpath://brooklyn.war and []`
-
-But before we really use Brooklyn, we need to setup some Locations.
-
-Stop Brooklyn with ctrl-c.
-
-## Configuring a Location
-
-Brooklyn deploys applications to Locations.
-
-Locations can be clouds, machines with fixed IPs or localhost (for testing).
-
-Brooklyn loads Location configuration from `~/.brooklyn/brooklyn.properties`.
-
-Create a `.brooklyn` folder in your home directory and download the template [brooklyn.properties](brooklyn.properties) to that folder.
-
-{% highlight bash %}
-$ mkdir ~/.brooklyn
-$ cd ~/.brooklyn
-$ wget {{site.url}}/quickstart/brooklyn.properties
-{% endhighlight %}
-
-Open brooklyn.properties in a text editor and add your cloud credentials.
-
-If you would rather test Brooklyn on localhost, follow [these instructions]({{ site.data.brooklyn.url.userguide }}/use/guide/locations/) to ensure that your Brooklyn can access your machine.
-
-Restart Brooklyn:
-
-{% highlight bash %}
-$ brooklyn launch
-{% endhighlight %}
-
-## Launching an Application
-
-There are several ways to deploy a YAML blueprint (including specifying the blueprint on the command line or submitting it via the REST API).
-
-For now, we will simply copy-and-paste the raw YAML blueprint into the web console.
-
-Open the web console ([127.0.0.1:8081](http://127.0.0.1:8081)). As Brooklyn is not currently managing any applications the 'Create Application' dialog opens automatically. Select the YAML tab.
-
-
-
-
-### Chose your Cloud / Location
-
-Edit the 'location' parameter in the YAML template (repeated below) to use the location you configured.
-
-For example, replace:
-{% highlight yaml %}
-location: location
-{% endhighlight %}
-
-with (one of):
-{% highlight yaml %}
-location: aws-ec2:us-east-1
-location: rackspace-cloudservers-us:ORD
-location: google-compute-engine:europe-west1-a
-location: localhost
-{% endhighlight %}
-
-**My Web Cluster Blueprint**
-
-{% highlight yaml %}
-{% readj _my-web-cluster.yaml %}
-{% endhighlight %}
-
-Paste the modified YAML into the dialog and click 'Finish'.
-The dialog will close and Brooklyn will begin deploying your application.
-
-Your application will be shown as 'Starting' on the web console's front page.
-
-
-
-
-## Monitoring and Managing Applications
-
-Click on the application name, or open the Applications tab.
-
-We can explore the management hierarchy of the application, which will show us the entities it is composed of.
-
- * My Web Cluster (A `BasicApplication`)
- * My DB (A `MySqlNode`)
- * My Web (A `ControlledDynamicWebAppCluster`)
- * Cluster of JBoss7 Servers (A `DynamicWebAppCluster`)
- * NginxController (An `NginxController`)
-
-
-
-Clicking on the 'My Web' entity will show the Summary tab. Here we can see if the cluster is ready to serve and, when ready, grab the web address for the front of the loadbalancer.
-
-
-
-
-The Activity tab allows us to drill down into what activities each entity is currently doing or has recently done. It is possible to drill down to all child tasks, and view the commands issued, and any errors or warnings that occured.
-
-Drill into the 'My DB' start operation. Working down through 'Start (processes)', then 'launch', we can discover the ssh command used including the stdin, stdout and stderr.
-
-[](images/my-db-activities-large.png)
-
-
-## Stopping the Application
-
-To stop an application, select the application in the tree view (the top/root entity), click on the Effectors tab, and invoke the 'Stop' effector. This will cleanly shutdown all components in the application and return any cloud machines that were being used.
-
-[](images/my-web-cluster-stop-confirm-large.png)
-
-
-### Next
-
-So far we have touched on Brooklyn's ability to *deploy* an application blueprint to a cloud provider, but this a very small part of Brooklyn's capabilities!
-
-Brooklyn's real power is in using Policies to automatically *manage* applications. There is also the (very useful) ability to store a catalog of application blueprints, ready to go.
-
-[Getting Started - Policies and Catalogs](policies-and-catalogs.html)
+<table class="table table-striped table-hover">
+<tbody>
+<tr>
+ <td><span class="glyphicon glyphicon-cloud text-primary"></span>
+ <a href="/what-is-brooklyn/">What is Brooklyn?</a></td>
+ <td>A basic introduction about what Brooklyn is and why you should use it.</td>
+</tr>
+<tr>
+ <td><span class="glyphicon glyphicon-download text-primary"></span>
+ <a href="/quickstart/install/">Install Brooklyn</a></td>
+ <td>The installation guide for Brooklyn.</td>
+</tr>
+<tr>
+ <td><span class="glyphicon glyphicon-list text-primary"></span>
+ <a href="/quickstart/tutorial/">Brooklyn tutorial</a></td>
+ <td>Tutorial for Brooklyn.</td>
+</tr>
+<tr>
+ <td><span class="glyphicon glyphicon-book text-primary"></span>
+ <a href="/learnmore/catalog/">Learning about Brooklyn catalog</a></td>
+ <td>Description of the available Brooklyn catalog.</td>
+</tr>
+<tr>
+ <td><span class="glyphicon glyphicon-briefcase text-primary"></span>
+ <a href="https://github.com/apache/incubator-brooklyn/tree/master/examples">Brooklyn Examples</a></td>
+ <td>See examples of Brooklyn in action.</td>
+</tr>
+</tbody>
+</table>
--- End diff --
This page nominally belongs to the "get started" nav category, but this table is sending links to both the "what is brooklyn" and "get started" categories, and external links - this is an inconsistent navigation hierarchy. Please be consistent about which category pages belong to, and define the hierarchy in the YAML front matter section - see [community/index.md](https://raw.githubusercontent.com/apache/incubator-brooklyn-site/master/community/index.md) and [community/index.html](https://brooklyn.incubator.apache.org/community/) for an example of how to define the submenus.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli closed the pull request at:
https://github.com/apache/incubator-brooklyn-site/pull/6
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#issuecomment-54976959
@richardcloudsoft could you please have a look, and try to test the deploy-site.sh in particular? Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307108
--- Diff: what-is-brooklyn.md ---
@@ -1,6 +1,7 @@
---
layout: normal
-title: Learn More
+title: What is Brooklyn
+permalink: /what-is-brooklyn/
--- End diff --
`permalink` is not used in our configuration
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307272
--- Diff: quickstart/index.md ---
@@ -1,179 +1,34 @@
---
-title: Getting Started
layout: normal
-children:
-- { path: quickstart/policies-and-catalogs.md }
--- End diff --
Why was this child page removed from the menu?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307149
--- Diff: quickstart/install.md ---
@@ -0,0 +1,86 @@
+---
+layout: normal
+title: Install Apache Brooklyn®
+permalink: /quickstart/install/
--- End diff --
`permalink` is not used in our configuration
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307177
--- Diff: quickstart/tutorial.md ---
@@ -0,0 +1,133 @@
+---
+title: Tutorial
+layout: normal
+children:
+- { path: install.md }
+- { path: /quickstart/policies-and-catalogs.md }
+permalink: /quickstart/tutorial/
--- End diff --
`permalink` is not used in our configuration
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17306533
--- Diff: index.md ---
@@ -63,8 +63,8 @@ View and modify using the *web console* or automate using the *REST API*
<div style="text-align: center" markdown="1">
-<a class="btn btn-primary btn-lg" role="button" href="learnmore.html">learn more</a>
-<a class="btn btn-primary btn-lg" role="button" href="quickstart/">get started</a>
+<a class="btn btn-default btn-lg" role="button" href="quickstart/">Learn more</a>
+<a class="btn btn-primary btn-lg" role="button" href="quickstart/install">Install</a>
--- End diff --
Again, these front-page call-to-action buttons were chosen after careful consideration. Could you explain why you chose to change them?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#issuecomment-54980539
ok @richardcloudsoft good suggestion. they have been splitted now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-brooklyn-site pull request: BROOKLYN-55
Posted by richardcloudsoft <gi...@git.apache.org>.
Github user richardcloudsoft commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn-site/pull/6#discussion_r17307455
--- Diff: quickstart/index.md ---
@@ -1,179 +1,34 @@
---
-title: Getting Started
layout: normal
-children:
-- { path: quickstart/policies-and-catalogs.md }
--- End diff --
If you are adding child pages (`install.md`, `tutorial.md`) you need to reference them here to make them appear in the menus. At the moment these two new pages are "orphaned".
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---