ENDOC-511 Update tutorials to reflect changes to bundle/resource codes #578
Conversation
| @@ -4,7 +4,7 @@ sidebarDepth: 2 | |||
|
|
|||
| # Bundle Evolution on Entando 7.1 | |||
|
|
|||
| Entando 7.1 implements a more modular approach to building apps with the **ent bundle** CLI orchestrating the management of project bundles. The Entando Bundle was restructured, its processes decoupled by component type, and the publishing transport method, streamlined. With these changes, Entando Bundles went from git-based to docker-based OCI bundles. Both methods are supported on Entando 7.1, and this page clarifies the differences between the two, along with the improvements in the new release. | |||
| Entando 7.1 implements a more modular approach to building apps with the **ent bundle CLI** orchestrating the management of project bundles. The Entando Bundle was restructured, its processes decoupled by component type, and the publishing transport method was streamlined. With these changes, Entando Bundles went from git-based to docker-based OCI bundles. Both types are supported on Entando 7.1, and this page clarifies the differences between the two, along with the improvements in the new release. | |||
There was a problem hiding this comment.
just a note: both methods and types are work in this sentence. But it's not just types that are supported in the specific sense, because the way the bundles are processed in the building, packing, etc. is different. So methods is technically applicable too.
There was a problem hiding this comment.
the subject is bundles, of which there are types. a bundle is not a method. we would need to rephrase / change the subject to make "methods" work
There was a problem hiding this comment.
the paragraph talks about bundles and how they are processed
There was a problem hiding this comment.
methods doesn't work here. if anything, it would refer back to the transport method mentioned 2 sentences prior. more directly, the previous sentence concerns bundles. to use a synonym for the subject that refers to something other than a bundle in the next breath doesn't work.
There was a problem hiding this comment.
You have a point, with the previous sentence, it flows nicer. But the topic sentence of the paragraph is not bundles but how bundles are managed by the ent bundle cli. So both words work, 'type' flows better, while 'method' emphasizes the process.
I think this shows that we are not timeservers.
| |MFE Configuration| Manually defined in the FTL | Utilize context parameters, system parameters and the `ext` variable to pass information to widgets and bundles, or expose it in the APIs | ||
| || | Auto-generated FTLs with parameters defined in `entando.json` | | ||
| |Bundle Thumbnail| Detailed inside the YAML bundle descriptor| Set with a JPG or PNG file named `thumbnail` in the bundle root folder, e.g. thumbnail.png | ||
| |Bundle creation | [`ent prj` commands](../getting-started/ent-bundle.md#git-based-bundle-commands)| New modular [`ent bundle` commands](../getting-started/ent-bundle.md) |
There was a problem hiding this comment.
Everything in the first column was capitalized because they are row titles/headers to give it some emphasis.
There was a problem hiding this comment.
the column is labeled "Attribute" and capitalizing the row entries implies that each of those terms is an attribute, which is incorrect
No description provided.