Skip to content
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-330 reorganization of intro pages content #507

Merged
merged 10 commits into from
May 18, 2022
Merged

ENDOC-330 reorganization of intro pages content #507

merged 10 commits into from
May 18, 2022

Conversation

jyunmitch
Copy link
Collaborator

@jyunmitch jyunmitch commented May 4, 2022

will fix the links in the next round. it's from moving the development concepts content to a different location.

@jyunmitch jyunmitch requested review from nshaw and Lyd1aCla1r3 May 4, 2022 13:52

1. [Install Kubernetes](#install-kubernetes)
2. [Prepare the Kubernetes Environment](#prepare-kubernetes)
3. [Deploy Entando](#deploy-entando)


We've tested a variety of Kubernetes implementations, including Minikube, Minishift, CodeReady Containers, K3s, and Microk8s, to find the optimal combination of low CPU/memory usage, fast startup times, and minimal configuration. After downloading the necessary files, we'll have our own instance of Kubernetes up and running in <60 seconds.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nshaw, Not sure if removing this was a good idea, just thinking that a tutorial should keep peripheral information to a minimum.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jyunmitch i had the same thoughts here; i thought i'd changed it to read "we selected k3s to use the optimal combination..."
i don't think we need to dive into process and trial and error, just discuss what's topical and pertinent

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jyunmitch looks good to me.

vuepress/docs/v7.0/docs/README.md Show resolved Hide resolved
vuepress/docs/v7.0/docs/README.md Outdated Show resolved Hide resolved
vuepress/docs/v7.0/docs/README.md Outdated Show resolved Hide resolved
vuepress/docs/v7.0/docs/README.md Outdated Show resolved Hide resolved
vuepress/docs/v7.0/docs/README.md Outdated Show resolved Hide resolved
@@ -41,21 +29,20 @@ https://multipass.run/#install
curl -sfL https://get.entando.org | bash
```

3. The progress of the install will be displayed on the console. Installation can take 10+ minutes depending on how long the Docker images take to download. The sequence of steps performed by the CLI is identical to the manual steps below. To understand what the CLI does, review the manual steps.
3. The progress of the install will be displayed on the console. Installation can take up to 10 minutes, depending on how long the Docker images take to download. The sequence of steps performed by the CLI is identical to the manual steps below. To understand what the CLI does, review the manual steps.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will be displayed -> is displayed

10+ means more than ten

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time has been reduced

4. The URL to access the Entando App Builder will print to the console once the install completes.
5. Login with username:`admin` and password: `adminadmin`. Refer to [Login to Entando](#login-to-entando) for more information and next steps.

## Manual Install

Manual installation allows you to configure a shared cluster or customize a local developer environment. The following learn-as-you-go approach gives you a working knowledge of Kubernetes as you get Entando up and running in a local environment. This is a three stage process:
Manual installation allows you to configure a shared cluster or customize a local developer environment. The following learn-as-you-go approach gives you a working knowledge of Kubernetes as you get Entando up and running in a local environment. After downloading the necessary files, your instance of Kubernetes will be up and running in <60 seconds.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gives you a -> provides

too many "up and running"s here

<60 seconds is the guaranteed time frame based on empirical data?


Entando supports full stack micro frontend and microservice architectures for codebases that are easier to understand, maintain, and debug across large, distributed teams, and comes with a private component repository that makes it easy for teams to share and reuse components.
* Build end-to-end modularity into your application for codebases that are easier to maintain & debug.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

& -> and

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was missed. I still see the &.


Use the navigation on the left to find step-by-step tutorials for common tasks or check out our learning paths below for a more structured approach.
Check out the learning paths below to start, with varying levels of experience and needs for the developer.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"to start" is awkward, like to start what?

Copy link
Member

@nshaw nshaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few requests and then apply to next as well.


1. [Install Kubernetes](#install-kubernetes)
2. [Prepare the Kubernetes Environment](#prepare-kubernetes)
3. [Deploy Entando](#deploy-entando)


We've tested a variety of Kubernetes implementations, including Minikube, Minishift, CodeReady Containers, K3s, and Microk8s, to find the optimal combination of low CPU/memory usage, fast startup times, and minimal configuration. After downloading the necessary files, we'll have our own instance of Kubernetes up and running in <60 seconds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jyunmitch looks good to me.


This document explores the architecture of the platform and some notable runtime characteristics.

![entando-architecture](../entando-architecture.png)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a screenshot of the full slide from the presentation with left and right background images. I think we had that before but can we clean that up and just include the diagram itself? We can probably drop the header as well but then when you click on the image you just get the interesting parts.


#### Entando Kubernetes Service

The Entando Kubernetes Service is part of the Entando cluster
The Entando K8s service is part of the cluster
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor, but maybe Kubernetes integration service per the glossary. I wouldn't shorten it here in the full name like this.


#### Using the Openshift Dashboard

On the Openshift dashboard, ingresses are not exposed directly as pods and deployments. The dashboard provides direct access to the Ingress Routes (or simply routes) under the `Applications` → `Routes` menu.
On the Openshift dashboard, ingresses are not exposed directly as pods and deployments. The dashboard provides direct access to the ingress routes under the `Applications` → `Routes` menu.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Openshift -> OpenShift


Entando supports full stack micro frontend and microservice architectures for codebases that are easier to understand, maintain, and debug across large, distributed teams, and comes with a private component repository that makes it easy for teams to share and reuse components.
* Build end-to-end modularity into your application for codebases that are easier to maintain & debug.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was missed. I still see the &.

# Learning Paths

::: tip Entando simplifies the development of modern apps:
::: tip Entando simplifies and automates the DevOps lifecycle of applications orchestrated by Kubernetes.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit too narrow since the 4Cs cover more than just DevOps. Maybe "Entando simplifies the development of composable applications deployed on Kubernetes." I actually don't love these bullets but let's keep those for now.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took out the blue highlighted box because it always bothered me and we don't use it anywhere else. What about the bullets needs improvement? It feels wrong to publish when something is off on a page that will get the more traffic than most pages.


Use the navigation on the left to find step-by-step tutorials for common tasks or check out our learning paths below for a more structured approach.
Check out the learning paths below, for varying levels of experience and needs for the developer.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we discussed improving this - "varying levels of experience and needs" is awkward to me. Maybe "Check out the learning paths below to find step-by-step tutorials for the most common tasks you may encounter."

@@ -12,28 +12,56 @@ only be available by building from source.

Entando is the leading open source **Application Composition Platform** for Kubernetes. It enables parallel teams to accelerate development and innovation of business capabilities on a modern, cloud-native, and Kubernetes-native stack.

With native support for Javascript app development, a micro frontend and microservices architecture, deployment of apps in containers that can be individually scaled up and down, and automated management of containers with Kubernetes, we simplify the move for enterprises looking to modernize across on-prem and cloud infrastructures.
It is a distributed and composable environment in which components can be built, scaled and iterated independently, helping teams build agile applications that can adapt to change.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would change one instance of "build/built" to "create" to eliminate redundancy


![entando-architecture](./entando-architecture.png)
On the Entando Platform, development of an application is organized into four stages: Create, Curate, Compose, and Consume. In the simplest terms, you create functional building blocks, curate them into a catalog, compose the blocks onto an app or website, which is then consumed by a user.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the second sentence doesn't make sense as-is. simplest option is to add "and" before "compose the blocks." without "and" it's grammatically incorrect.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not a grammar rule to use 'and' in a list, it is convention. It is not wrong to leave out 'and' in a list.

Adding 'and' where you suggest breaks up the flow.

I would suggest we follow the 80% rule because most of the suggestions made here may make the content incrementally better, but there's just a lot bigger improvements we can make elsewhere. So unless there is a significant improvement, something is unclear, or just wrong, I would move on and not belabor the point. Some of these issues are just too small to argue about and it's taking up a lot of time. It's ok if we disagree.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

belabor is an interesting word choice. the point of this process is to offer both corrections and perspective. ignoring comments that identify valid issues prolongs this cycle and is the biggest contributor to inefficiency.


The Entando platform includes the following major elements:
## Create Components
The first step in building a modern application on Entando is to design and create each independent component or functional block. Developers can use the [Entando Component Generator](./create/component-gen-overview.md) and [Blueprint](./create/blueprint-features.md) to automate the building and packaging of project files, with the flexibility to customize while using software they are accustomed to. The modular design of apps built on Entando means new business capabilities can be integrated into your application without reworking existing systems.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be consistent with either "they" or "you," not mix these


## Why Kubernetes?
## Curate and Share Components
On the Entando Platform, Curate and Share means development teams can bundle and share components within a central catalog. Multiple teams can collaborate on a single component or packaged business capabilities (PBCs) and share them across organizations and applications. They can test and assess components for readiness, manage and publish versions, and share metadata for continuous upgrades.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"share" is not one of the 4Cs and should not be capitalized in support of Curate

"single component" is redundant and "single" carries over to PCBs on first read, making the plurality seem wrong. should either use "component of PCB" or "components or PCBs," not mix singular and plural.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Share is part of the menu title and need to be consistent with that. Also, the items under that menu header don't really make sense without the Share.

Single is there for emphasis. Can we not belabor this point and sometimes disagree.

| | [Digital Assets](../tutorials/compose/digital-assets-tutorial.md) |

## Consume Applications
In the development lifecycle of an application, Consume is the execution stage where users interact with the app. On Entando, the modular design of components and services means they can be scaled individually, or as a whole, according to those interactions. Likewise, content can be updated, engine rules adapted, and upgrades made seamlessly. As a result, the development cycle is a continuous process with minimal disruptions and faster time to market.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"upgrades made seamlessly" is very awkward phrasing

Entando supports full stack micro frontend and microservice architectures for codebases that are easier to understand, maintain, and debug across large, distributed teams, and comes with a private component repository that makes it easy for teams to share and reuse components.

Use the navigation on the left to find step-by-step tutorials for common tasks or check out our learning paths below for a more structured approach.
Check out the learning paths below to find step-by-step tutorials for the most common tasks, organized by architecture and levels.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what kind of levels? needs a qualifier. level of complexity? level of stack?

@nshaw nshaw merged commit 0ce7fe6 into main May 18, 2022
@nshaw nshaw deleted the ENDOC-330 branch May 18, 2022 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants