diff --git a/vuepress/docs/.vuepress/next.js b/vuepress/docs/.vuepress/next.js
index 88d2f6f545..2809aa34e0 100644
--- a/vuepress/docs/.vuepress/next.js
+++ b/vuepress/docs/.vuepress/next.js
@@ -78,7 +78,7 @@ module.exports = {
                 title: 'Curate and Share Components',
                 children: [    
                     {
-                        title: 'Bundle and Component Descriptors',
+                        title: 'Bundle Details',
                         path: path  + 'curate/ecr-bundle-details.md'
                     },
                     {
diff --git a/vuepress/docs/next/docs/curate/bundle-comparison.md b/vuepress/docs/next/docs/curate/bundle-comparison.md
new file mode 100644
index 0000000000..11fb957a35
--- /dev/null
+++ b/vuepress/docs/next/docs/curate/bundle-comparison.md
@@ -0,0 +1,35 @@
+---
+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.
+
+Some of the major improvements with docker-based bundles are:
+* Simplified bundle directory structure
+* Just one Git source repository required with Docker image repositories created automatically as needed
+* Optimized file storage and transfer using a layered file system, beneficial for large projects
+* Standardized bundle address format
+* A decoupled build and deployment process which is easier to understand, modify, and troubleshoot 
+
+For specifications on docker-based bundles, see the [Bundle Details](ecr-bundle-details.md) page. 
+### Bundle Comparison Table
+|Attribute | [git-based bundles](../../../v7.0/docs/curate/ecr-bundle-details.md)| [docker-based bundles](ecr-bundle-details.md)|
+| :- | :-------------------- | :---------------------  |
+|`descriptorVersion`| v1| v5
+| Bundle Specifications |Defined with descriptor files | Built with [ent bundle CLI](../getting-started/ent-bundle.md) tool
+| Versioning |Bundle version set by Git tags |Bundle version set by Docker tags. For MFEs, the version defaults to 1.0.0 unless set in the [entando.json](ecr-bundle-details.md). 
+|Plugin Ingress| Generated by Entando or set in the plugin descriptor.yaml | Generated by Entando or customized in the [bundle descriptor](ecr-bundle-details.md#bundle-conventions), entando.json 
+|Identifiers| Designated Bundle ID and Plugin ID | Bundles, MFEs, & Plugins have unique global IDs|
+|Initialize from Entando Hub| As git clone  |[Direct initialization from Hub](../../tutorials/create/mfe/react.md)(TODO-switch to appropriate tutorial)  with `ent init BUNDLE-NAME –from-hub`|
+|Bundle Creation | [`ent prj` commands](../getting-started/ent-bundle.md#git-based-bundle-commands)| New modular [`ent bundle` commands](../getting-started/ent-bundle.md)
+|Deploy & Install| `ent ecr deploy` and `ent ecr install` | No change 
+|Export Bundle|`ent bundler`| Not Available 
+|JHipster Integrated Blueprint Project| `ent jhipster blueprint` creates [MFE & MS template project](../../tutorials/create/ms/generate-microservices-and-micro-frontends.md)| [Convert Blueprint project to v5 bundle](../../tutorials/create/ms/generate-microservices-and-micro-frontends.md) (TODO-change link to new tutorial)
+|APIs| Not Available | [Manage APIs with `ent bundle` commands](../getting-started/ent-api.md). MFEs can make API claims to MSs within the namespace
+||| MFEs support service discovery by using the property `apiClaim`
+|Local Services |Not Available | Default services now include PostgreSQL, MySQL, and Keycloak. Additional services can be added with the [`ent bundle svc` commands](../getting-started/ent-svc.md).
+|MFE Custom UI| Add with manual scripts| Custom UI is auto-generated in FTL format
+|Data Transfer | Manual | New ways to pass values or information to widgets and bundles, or expose them in the APIs, by [utilizing context parameters, system parameters and the ext variable](ecr-bundle-details.md).
+|Bundle Thumbnail| Detailed inside the YAML bundle descriptor|Automatically set with a JPG or PNG file named `thumbnail` in the bundle root folder.  e.g. thumbnail.png