-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENDOC-314 new links on Getting Started draft #346
Conversation
2. [Manually install Entando step by step](#manual-install). This permits configuration of either a shared cluster or a local developer environment. A manual install is appropriate when CLI defaults don't meet specific needs, or to customize the deployment. | ||
## Try Entando | ||
|
||
Set up Entando using two simple steps or install manually for your specific needs. Then try the platform with a simple widget or walk through the **Welcome Wizard** in our AppBuilder. For a more in-depth experience, check out our **Banking demo**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably update the language to Standard Banking Demo rather than Banking demo or Standard Demo. That's what the tutorial is called now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glossary - App Builder, instead of AppBuilder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think it's important to keep 1. and 2. above. they provide pertinent information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never mind! i just got to where you moved that info to. it flows nicely to introduce things vaguely then hit the details time-of. on the other hand 1. and 2. clue the user into which install they'd like to follow and quickly compare the two... me not knowing anything i'd like the info up front, but someone with experience would probably know which path to take and then get a refresh on the particulars :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
* [Quick Local Install](https://dev.entando.org/v6.3.2/docs/getting-started/#automatic-install) | ||
The fastest way to start up Entando in Kubernetes. | ||
|
||
* [Manual Install](https://dev.entando.org/v6.3.2/docs/getting-started/#manual-insta) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Link looks broken to me - should be #manual-install
Once you're setup, check out: | ||
* [Build a simple Bundle and create an App](https://dev.entando.org/v6.3.2/tutorials/ecr/publish-simple-bundle.html) | ||
* [Welcome Wizard](https://dev.entando.org/v6.3.2/docs/getting-started/welcome-wizard.html) | ||
* [Install our Banking Demo](https://dev.entando.org/v6.3.2/tutorials/samples/install-standard-demo.html) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same, Standard Banking Demo
|
||
## Learn about Entando | ||
|
||
Learn about what Entando can do top down or explore the elements that make automating containers with Kubernetes easier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"make automating containers with Kubernetes" is too specific, "quickly developing applications on Kubernetes" would be preferable
|
||
Learn about what Entando can do top down or explore the elements that make automating containers with Kubernetes easier. | ||
|
||
* [Introduction to Entando ](https://dev.entando.org/v6.3.2/docs/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style guide-wise, all links should be relative links, meaning do not include the full URL. I think there are notes on that in the README. If you include the full URL, these links will not point to the correct location in different environments, e.g. local, staging, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nshaw please give an example of how to turn a full url link into a relative one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Relative means the path to the new page is relative to the location of the current page. So ./abc/def.md would check in the current location for an abc folder and then display the def.md in that folder. You can also use .. to go up a level (or more levels with ../.. or ../../.., etc.) , e.g. ../docs/getting-started/ to go up one level then into docs and getting started. You can also skip the path altogether and just use #section-name if you're referencing a different section in the current page. Unless you're pointing to an external web site we want to avoid anything with dev.entando.org in it and even v6.3.2, for maintenance reasons.
|
||
|
||
|
||
<!-- 1. [Automatically install Entando via the Entando command-line interface (CLI)](#automatic-install). This is the fastest way to initialize an Entando application in Kubernetes. A CLI install defaults certain settings and prepares a local developer environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General principle, we don't leave commented code in docs or actual code since it can always be found in the git history. Comment sections clutter the code and make it harder to maintain.
|
||
Set up Entando using two simple steps or install manually for your specific needs. Then try the platform with a simple widget or walk through the **Welcome Wizard** in our AppBuilder. For a more in-depth experience, check out our **Banking demo**. | ||
|
||
* [Quick Local Install](https://dev.entando.org/v6.3.2/docs/getting-started/#automatic-install) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep the same language - maybe Automatic Install here but expand the note to indicate it's local, "The fastest way to locally install and start up Entando in Kubernetes".
2. [Manually install Entando step by step](#manual-install). This permits configuration of either a shared cluster or a local developer environment. A manual install is appropriate when CLI defaults don't meet specific needs, or to customize the deployment. | ||
## Try Entando | ||
|
||
Set up Entando using two simple steps or install manually for your specific needs. Then try the platform with a simple widget or walk through the **Welcome Wizard** in our AppBuilder. For a more in-depth experience, check out our **Banking demo**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think it's important to keep 1. and 2. above. they provide pertinent information.
2. [Manually install Entando step by step](#manual-install). This permits configuration of either a shared cluster or a local developer environment. A manual install is appropriate when CLI defaults don't meet specific needs, or to customize the deployment. | ||
## Try Entando | ||
|
||
Set up Entando using two simple steps or install manually for your specific needs. Then try the platform with a simple widget or walk through the **Welcome Wizard** in our AppBuilder. For a more in-depth experience, check out our **Banking demo**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never mind! i just got to where you moved that info to. it flows nicely to introduce things vaguely then hit the details time-of. on the other hand 1. and 2. clue the user into which install they'd like to follow and quickly compare the two... me not knowing anything i'd like the info up front, but someone with experience would probably know which path to take and then get a refresh on the particulars :)
|
||
Learn about what Entando can do top down or explore the elements that make automating containers with Kubernetes easier. | ||
|
||
* [Introduction to Entando ](https://dev.entando.org/v6.3.2/docs/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nshaw please give an example of how to turn a full url link into a relative one?
2. [Manually install Entando step by step](#manual-install). This permits configuration of either a shared cluster or a local developer environment. A manual install is appropriate when CLI defaults don't meet specific needs, or to customize the deployment. | ||
## Try Entando | ||
|
||
Set up Entando using two simple steps or install manually for your specific needs. Then try the platform with a simple widget or walk through the **Welcome Wizard** in our App Builder. For a more in-depth experience, check out our **Standard Banking demo**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Demo instead of demo.
The fastest way to locally install and start up Entando in Kubernetes. | ||
|
||
* [Manual Install](#manual-install): | ||
Useful if you want a shared cluster or customize. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "or custom local instance"
Useful if you want a shared cluster or customize. | ||
|
||
Once you're setup, check out: | ||
* [Build a simple Bundle and create an App](../../tutorials/ecr/publish-simple-bundle.html) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whitespace matters so I think you're getting extra indentation because of the spaces on this list.
|
||
|
||
## Automatic Install | ||
The following steps will launch an Ubuntu VM via Multipass, install Kubernetes, and then deploy Entando to it. | ||
Automatically install Entando via the Entando command-line interface (CLI) and prepare a local developer environment with defaults settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"defaults settings" feels wrong. Maybe just "default settings".
|
||
::: tip What's Needed to Run Kubernetes? | ||
**What's Needed to Run Kubernetes?** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments and then we need the /next change as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
This is a draft and need to assess links, layout and new text.
Also, when approved, will be added to next version.