ENDOC-566 7.1 Edits for loose threads #579
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lyd1aCla1r3
reviewed
Sep 26, 2022
|
|
||
| ::: tip | ||
| See the [Plugin Environment Variables](../../tutorials/devops/plugin-environment-variables.md) tutorial to setup environment variables, either inline or based on Kubernetes Secrets. |
| @@ -12,7 +12,7 @@ The docker-based approach is an improvement of the previous Entando Bundle struc | |||
|
|
|||
| * There is a single bundle descriptor, `entando.json`, initialized and managed by the [ent bundle CLI](../getting-started/ent-bundle.md). | |||
| * Microservices and micro frontends can be built independently, each with their own folders. | |||
| * The `platform` directory is dedicated to platform specific components such as fragments, pages, and static resources. | |||
| * The `platform` directory is dedicated to platform specific components such as fragments, pages, and static resources. For more information on component types and descriptors, see the [Bundle Component Details ](bundle-component-details.md) page. | |||
There was a problem hiding this comment.
extra space between "Details" and "]"
| @@ -10,7 +10,7 @@ In addition, this document describes the series of `ent ecr` commands that manag | |||
|
|
|||
| ## Entando 7.1 Bundle Development | |||
|
|
|||
| Beginning with Entando 7.1, the `ent bundle` command and its convenience methods introduce a streamlined process to govern the structure, files and management of Entando bundles. The bundle development lifecycle consists of 6 stages, each corresponding to a subcommand: | |||
| Beginning with Entando 7.1, the `ent bundle` module introduces a streamlined process to govern the files, structure, and management of Entando bundles. The bundle development lifecycle consists of 6 stages, each corresponding to a subcommand: | |||
There was a problem hiding this comment.
ent bundle cli tool (per discussion)
structure is the broadest term in that list and encompasses files, so the list should lead with it
There was a problem hiding this comment.
My understanding is that ascending or descending is fine. In this case, because I wanted to end with the management, I picked ascending. The thinking was that management is bigger than structure since it controls it.
Lyd1aCla1r3
approved these changes
Sep 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.