diff --git a/README.md b/README.md
index e23989e..defb337 100644
--- a/README.md
+++ b/README.md
@@ -21,9 +21,8 @@ When documenting your APIs, it's possible to perform changes and eval how they l
 
 For that, all you need to do is follow the instructions below:
 
-1. Point your API spec on the file `docusaurus.config.js` to your localhost: `http://localhost:3001/openapi.json`
-2. `npm dev` to run the docs portal locally
-3. `npm run swagger-ui:watch` to serve your api docs locally on your API project
-4. Finally to bypass CORS you will want to get this Chrome [extension](https://chrome.google.com/webstore/detail/moesif-origin-cors-change/digfbfaphojjndkpccljibejjbppifbc)
+1. `DOCS_URL=http://localhost:3001/ npm run dev` to run the docs portal locally
+2. `npm run swagger-ui:watch` to serve your api docs locally on your API project
+3. Finally to bypass CORS you will want to get this Chrome [extension](https://chrome.google.com/webstore/detail/moesif-origin-cors-change/digfbfaphojjndkpccljibejjbppifbc)
 
 When you are done, just deploy your `openapi.yml` as you normally would. And don't forget to update your client sdk [here](https://github.com/epilot-dev/sdk-js).
diff --git a/docs/blueprints/editing-and-synchronizing.md b/docs/blueprints/editing-and-synchronizing.md
new file mode 100644
index 0000000..543bb73
--- /dev/null
+++ b/docs/blueprints/editing-and-synchronizing.md
@@ -0,0 +1,188 @@
+---
+sidebar_position: 3
+title: Editing and synchronizing
+hide_title: true
+---
+
+## Editing Blueprints 
+
+After installation or creation, Blueprints can be adjusted. All changes are applied directly within the Blueprint overview.
+
+---
+
+### Changing Blueprint name
+
+To change a Blueprint’s name, hover over it, click the pen icon, enter the new name, and confirm by clicking the checkmark icon.
+
+![Edit Blueprint name](/img/blueprints/3-edit-blueprint-name.png)
+
+---
+
+### Adding Resources
+
+- Click the **“Ressource hinzufügen”** button on the left.
+
+- Follow the procedure for adding a resource, the same as when creating a Blueprint.
+
+- For detailed instructions, see [Creating a Blueprint](/docs/blueprints/installing-a-blueprint#creation-of-custom-blueprint).
+
+
+![Resources toc](/img/blueprints/3-resources-toc.png)
+
+### Removing Resources
+
+- In the Blueprint overview, select the resources you want to remove.
+
+- Click **“Delete from this Blueprint”** to remove them.
+
+:::info
+
+Note: Resources removed from the Blueprint still exist in your organization. They are simply no longer a part of this Blueprint.
+
+:::
+
+![Remove resource](/img/blueprints/3-remove-resource.png)
+
+---
+
+### Actions
+
+Blueprints offer a set of actions that allow you to manage and share them efficiently. The available actions can be accessed from the **top-right navbar** of the Blueprint overview.
+
+![Actions](/img/blueprints/3-actions.png)
+
+---
+
+### Synchronize with another organization
+
+- Transfer the Blueprint and its resources to other organizations you are associated with.
+
+- For detailed instructions, see [Synchronizing Blueprints](#synchronizing-your-blueprint-with-another-org).
+
+---
+
+### Download
+
+- Download the Blueprint by selecting **Actions → Download** in the top-right navbar and confirming the operation.
+
+:::info
+
+Note: This function is only available for custom Blueprints, not for those installed from the Marketplace.
+
+:::
+
+![Download](/img/blueprints/3-blueprint-download.png)
+
+---
+
+### Delete
+
+- Remove the Blueprint by selecting Actions → Delete in the top-right navbar and confirming.
+
+:::info
+
+Note: Deleting a Blueprint does **not** delete the underlying resources in your organization. It only removes the grouping of those resources as part of the Blueprint.
+
+:::
+
+![Delete](/img/blueprints/3-blueprint-delete.png)
+
+---
+
+## Synchronizing your blueprint with another org
+
+When a Blueprint has been created or installed in your sandbox, you can synchronize it with other organizations you are associated with. Synchronization means transfering configuration elements (resources) —such as journeys, automations, products, workflows, and entity schemas—from one tenant to another.
+
+On the **Blueprints tab** all the Blueprints available in your organisation: both created and installed from a Marketplace, are listed in the “Blueprints” tab. The label in “Source” column will help you understand where each Blueprint is coming from.
+
+![Installed blueprints tab](/img/blueprints/3-installed-blueprints-tab.png)
+
+Clicking a table item opens a detailed view of the resources included in the Blueprint.
+
+This page also allows you to easily manage all the resources involved with your blueprint.
+
+![Installed blueprint page](/img/blueprints/3-installed-blueprint-page.png)
+
+As of now, those resources only exist on the current **sandbox organization**, but after you are happy with the configuration, you can easily “[sync](#synchronizing-your-blueprint-with-another-org)” this blueprint with another org (typically, the associated **production organization**).
+
+This will create a copy of this blueprint, together with the current state of each resource, and apply them on the selected destination org.
+
+---
+
+### The Synchronization Process
+
+The process will look similar to the [blueprint installation process](/docs/blueprints/installing-a-blueprint):
+
+Click on **“Actions → Synchronize”** on the top right corner.
+
+![Actions](/img/blueprints/3-actions.png)
+
+You will be directed to a screen that allows to select the destination org you wish to synchronize to, meaning - where do you wish to transfer your Blueprint to.
+
+![Switch org screen](/img/blueprints/3-switch-org-screen.png)
+
+Select your production org and click on “**Continue**”.
+
+![Switch org screen selector](/img/blueprints/3-switch-org-screen-selector.png)
+
+Now we will prepare the resources of your blueprint for synchronization.
+
+Depending on the amount of resources, this may take from 1~5 min, after which you can click on “**Continue to destination organization**”.
+
+![Continue to destination](/img/blueprints/3-continue-to-destination.png)
+
+---
+
+### Switching to the destination org
+
+You will be prompted to switch the **destination org** to finish the syncing process, just click continue and you will be redirected there.
+
+![Destination modal](/img/blueprints/3-destination-modal.png)
+
+---
+
+### Reviewing the resources impact
+
+
+Now on the destination org, you will be able to review the impact that this blueprint will have on the resources of this org, just like in the [blueprint installation process](/docs/blueprints/installing-a-blueprint).
+
+Just click on “See resources with their impact” to review it.
+
+
+You will see what will be created denoted by **New**, and if some of those resources are already present on the destination org (that will happen if it’s not the first time syncing the blueprint), you will see either **No changes**,  “**Update**" or “**Delete**".
+
+![Resources impact](/img/blueprints/3-resources-impact.png)
+
+If everything is as expect you can now click on “Synchronize Blueprint” to finish the process.
+
+
+---
+
+And that’s it! 
+You will be presented with the success page of the synchronization process, which will give you a link to see the instance of your blueprint in this destination org!
+
+![Sync complete screen](/img/blueprints/3-sync-complete-screen.png)
+
+You successfully synchronized your sandbox blueprint to your production org!
+
+---
+
+### Further editing the blueprint
+
+Now you are able to edit and manage your Blueprint, for more details [click here](#editing-blueprints).
+
+After that, if you need, you can sync those changes back to the sandbox.
+
+For that, just repeat this process, but this time, starting from the blueprint overview page of the destination org.
+
+:::info
+
+We recommend experimenting with changes in the Sandbox and syncing to Production only when you are satisfied with the setup.
+
+:::
+
+
+![Installed blueprint page](/img/blueprints/3-installed-blueprint-page.png)
+
+
+That also counts for the blueprint back in the sandbox: you can go back and continue to make changes and experiment by adding, removing or editing resources. Those changes will only be present on your sandbox until you click on “**Actions → Synchronize**” again.
diff --git a/docs/blueprints/installing-a-blueprint.md b/docs/blueprints/installing-a-blueprint.md
index 5207d88..9248c1f 100644
--- a/docs/blueprints/installing-a-blueprint.md
+++ b/docs/blueprints/installing-a-blueprint.md
@@ -4,7 +4,9 @@ title: Installing a Blueprint
 hide_title: true
 ---
 
-## Installing a Blueprint
+
+
+## Installation from Marketplace
 
 :::info
 
@@ -12,28 +14,127 @@ Blueprints are currently in closed **BETA** only available to selected customers
 
 :::
 
-To manage and install Blueprints, navigate to the [Configuration > Blueprints](https://portal.epilot.cloud/app/blueprints) in the epilot portal.
+To install a blueprint from the Marketplace navigate to [Configuration → Blueprints → Marketplace tab](https://portal.epilot.cloud/app/blueprints).
+
+Here you can search and discover blueprints tailored for common use cases, based on our experience in the energy market.
+
+After finding the one that fits your business, click on “Install now”.
+
+:::info
+
+Installation of a Marketplace Blueprint is possible only in a Sandbox testing environment. If you don’t have a sandbox yet, check the [Sandbox documentation](/docs/blueprints/intro#sandbox).
+
+:::
+
+
+![Portal Marketplace Page](/img/blueprints/2-portal-marketplace.png)
+
+
+You have two options of installation:
+
+- [One-click Install](/docs/blueprints/installing-a-blueprint#one-click-install)
+- [Advanced Install](/docs/blueprints/installing-a-blueprint#advanced-install)
+
+![Step 2](/img/blueprints/2-one-click-installation.png)
+
+---
+
+### One-click install
+
+After choosing “One-click install” the installation process will start automatically.
+
+Depending on the number of resources included in the chosen blueprint the installation may take up to 5 min.
+
+![Step 3](/img/blueprints/2-one-click-step-3.png)
+
+And that’s it! You successufuly installed a blueprint from the marketplace. Check out [Post-Installation Configuration](#post-installation-configuration) on how to configure the installed resources.
 
-![Blueprints](/img/blueprints/installed-blueprints.png)
 
-To install a new Blueprint, click on "Install Blueprint" and choose the source for your Blueprint.
+Next, you can [edit it](/docs/blueprints/editing-and-synchronizing#editing-blueprints), or [synchronize with another organization](/docs/blueprints/editing-and-synchronizing#synchronize-with-another-organization)  — click on the relevant sections links for more details.
+
+![Installation Complete](/img/blueprints/2-one-click-complete.png)
+
+---
+
+### Advanced install
 
-1. If you already have a Blueprint zip file, you can choose *Upload File*
-1. Choose "Marketplace" to pick a Blueprint from the [epilot Marketplace](https://marketplace.epilot.cloud).
-1. Or if you wish to copy resources from another epilot organization, you can choose *"Sandbox"*.
+If “Advanced Install” is chosen, you will have a fine control on which resources from a blueprint should be installed.
 
-![Install Blueprint](/img/blueprints/install-blueprint.png)
+To remove a resource, uncheck an item and click on “Update installation”.
+
+
+![Pick resources](/img/blueprints/2-advanced-pick-resources.png)
+
+When done selecting resources, click on “Install resources” to continue, the installation will proceed automatically from here.
+
+And that’s it! You successufuly installed a blueprint from the marketplace. Check out [Post-Installation Configuration](#post-installation-configuration) on how to configure the installed resources.
+
+Next, you can [edit it](/docs/blueprints/editing-and-synchronizing#editing-blueprints), or [synchronize with another organization](/docs/blueprints/editing-and-synchronizing#synchronize-with-another-organization)  — click on the relevant sections links for more details.
+
+![Installation Complete](/img/blueprints/2-advanced-complete.png)
+
+---
 
-After picking a blueprint from your source, epilot will show a preview (plan) of what will get added or changed in your organization as part of the Blueprint. 
+## Post-Installation Configuration
 
-**Note that at this point, no changes will be made to your organization and you can still review the Blueprint before installing it!**
+After a Blueprint is installed, some resources may still require additional setup before they can be fully used. In the list view, these resources appear with the **“Ready to use” toggle switched off**. You can also filter the list to quickly see which items are not yet marked as ready.
 
-After you have reviewed the changes, click on *Import Resources* to start the Blueprint installation.
+- In the list view, click the link next to the toggle to open a resource in a new tab.
 
-![View Plan Step](/img/blueprints/view-plan.png)
+- Define and save any changes needed for the resource.
 
-The installation will take up to a few minutes to complete. 
+- Return to the Blueprint overview and toggle the resource as ready to use.
 
-After the installation is complete, you will see a list of all the resources that were installed, and can click on each one to view the details and edit the configuration.
+- Marking a resource as ready is optional and is meant to help you keep track of configuration progress.
 
-We recommend that you test the Blueprint in a sandbox environment before installing it in your production organization.
+
+![Resource toggle](/img/blueprints/2-resource-toggle.png)
+
+
+---
+
+## Creation of Custom Blueprint
+
+Besides installing a blueprint from marketplace, you are also able to create your own Blueprints.
+
+With **Custom Blueprints** you can combine available resources to create your own Blueprint. With that you are able to:
+
+- Organize use-cases
+
+- Test combination of resoures on a sandbox
+
+- Share your use-case with other orgs
+
+---
+
+To create a **Custom Blueprint**, go to Configuration → Blueprints and select the tab “Blueprints”.
+
+On the bottom you will see “Create Blueprint”, click on it to start the creation process.
+
+You will be presented with a screen that allows you to select Resources to include in your Custom Blueprint.
+
+Click on “Add resources” to continue.
+
+
+![Create blueprint](/img/blueprints/2-create-blueprint.png)
+
+
+You will be presented with a list of categories of resources, select one to continue.
+
+After, select the specific resources on that category you wish to include, here we are adding a single Product.
+
+:::info
+
+Note: A resource will be added together with any other resources linked to it.
+
+:::
+
+
+![Add resources](/img/blueprints/2-add-resource-side-panel.png)
+
+
+That’s it! You successfully created your own Blueprint! 
+
+You will be redirected to the resources view of this blueprint in there you are able to further edit it, [see more](/docs/blueprints/editing-and-synchronizing#editing-blueprints).
+
+---
diff --git a/docs/blueprints/intro.md b/docs/blueprints/intro.md
index a967b1e..4c3c87d 100644
--- a/docs/blueprints/intro.md
+++ b/docs/blueprints/intro.md
@@ -15,21 +15,108 @@ Blueprints are currently in closed **BETA** only available to selected customers
 :::
 
 
-**Blueprints** are an essential feature to package end-to-end epilot configuration into easily installable packages.
+Available through the **epilot Marketplace**, Blueprints allow companies to quickly launch and operate a wide variety of use cases with just a few clicks.
 
-![Blueprints](/img/blueprints/blueprint-details.png)
+![Marketplace blueprints carousel](/img/blueprints/1-marketplace-carousel.png)
 
-Blueprints are intended to simplify the setup of epilot and radically reduce the time and effort required to go to market with specific industry use cases using the latest epilot features and best practices.
+---
+
+
+
+### Example Use Cases
+
+A common example of a Blueprint is the sale of **heat pumps, PV systems, or electricity and gas tariffs.**
+
+Here’s how it works in practice:
+A customer applies through a predefined interactive form on your website. The request is captured in epilot, creating a lead for your agents team. Agents are notified immediately, and automated workflows (e.g., emails, task assignments) ensure the case is processed smoothly.
+
+---
+
+### Why Blueprints help you set up Use Cases faster
+
+Setting up epilot from scratch requires configuring multiple resources. For example:
+
+- **Customer entry points (Journeys)** on your website
+- **Automations**, such as emails or notifications
+- **Workflows** to define the process steps
+- **Products** with all relevant details
+- **Entity schemas and templates** to structure data; and many more
+
+Configuring all these resources individually can be time-consuming. Since epilot already knows what good configurations look like, we provide predefined best practice setups as Blueprints.
+
+A Blueprint is essentially a ready-to-use epilot configuration that combines these resources into one package. Each Blueprint is carefully orchestrated so that all components work seamlessly together.
+
+---
+
+### Benefits of Blueprints
+
+- **Faster time-to-market**: introduce new products and use cases quickly without complex setup.
+- **Reduced effort**: eliminate manual configuration by using pre-built best practices.
+
+---
+
+### Quality and expansion
+
+- All Blueprints are **built, verified, and tested by epilot**, ensuring they meet industry standards and best practices.
+
+- The epilot Marketplace is continuously updated with **new Blueprints and partner integrations.**
+
+---
+
+### Licensing & availability
+
+Blueprints use features that require a **Professional** or **Enterprise** license.
+
+If you are using a **Business** or **Starter** license, please contact your sales representative for further guidance.
+
+---
+
+### Installation and sandbox
+
+Epilot Marketplace Blueprints can be installed only in a [sandbox environment](/docs/blueprints/intro#sandbox).
+
+A sandbox is a safe testing space that allows you to validate configurations without affecting your production environment. Once the Blueprint has been installed and tested successfully, it can be synchronized into your production organization.
+
+For step-by-step instructions, see the [Installation documentation](/docs/blueprints/installing-a-blueprint).
+
+---
+
+## Sandbox
+
+A **Sandbox** provides the ability to safely test the epilot configuration in a separate tenant, away from the tenant used in daily business operations. Typical configurations include journeys along with their associated elements such as automations, products, workflows, or entity schemas. Once validated, these setups can be transferred to the desired tenant
+
+A sandbox environment is the only place where Marketplace Blueprints can be installed. This ensures that all configurations are tested safely before being transferred to production.
+
+---
+
+### Sandbox activation
+
+If you would like to use a sandbox but do not yet have one, please contact your Customer Success or Sales representative.
 
-These packages can include a wide variety of connected epilot resources such as *[Products](/docs/entities/schemas-list#product), [Journeys](/docs/journeys/journey-builder), [Automations](/docs/automation/intro), [Workflows](/docs/workflows/intro), [Entity Attributes](/docs/entities/attributes), [Purposes](#), [Labels](#), [Email templates](/docs/entities/schemas-list#email_template) and [Document templates](/docs/files/document-generation)*.
+Alternatively, you can also request a  sandbox directly during the installation of a Blueprint.
 
-Pre-made Blueprints incorporating latest industry best practices can be installed from the epilot Marketplace. Some examples:
+![Wallbox B2C blueprint description page](/img/blueprints/1-wallbox-description.png)
 
-- [Heat Pump Sales](https://marketplace.epilot.cloud/blueprints/edl-heat-pump)
-- [Commodity Sales](https://marketplace.epilot.cloud/blueprints/commodity-b2c)
-- [Solar System Installations](https://marketplace.epilot.cloud/blueprints/solar-b2c)
-- [Registration of PV Systems](https://marketplace.epilot.cloud/blueprints/registration-of-pv-systems)
-- [Registration of Grid Connections](https://marketplace.epilot.cloud/blueprints/hausanschluss-fernwarme)
+
+---
+
+### Sandbox set up for synchronizing between organizations
+
+To transfer configurations between organizations (for example, from a sandbox to a production environment), you must have a user account with the **same email address** in both organizations. With this in place, the connection between the organizations is created automatically for that user, and the transfer process can be executed without additional setup. To learn how synchronize resources between your Sandbox and other Org [click here].
+
+---
+
+### Switching Between Organizations
+
+:::tip
+
+To make switching between organizations possible, invite your users to both organizations using the same email address. Then you can conveniently switch between organizations by clicking your initials in the bottom left corner.
+
+:::
+
+![Org Switcher](/img/blueprints/1-org-switcher.png)
+
+---
 
 :::note
 
diff --git a/docs/blueprints/sandbox.md b/docs/blueprints/sandbox.md
deleted file mode 100644
index 33fc222..0000000
--- a/docs/blueprints/sandbox.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-sidebar_position: 3
-title: Sandbox
----
-
-# Sandbox
-
-:::info
-
-Sandboxes are currently in closed **BETA** only available to selected customers.
-
-:::
-
-Sandboxes are a way to safely test epilot configuration in a sandbox environment and promote configuration changes to production using a Blueprint Pipeline.
-
-## Connecting a Sandbox
-
-To easily promote configurations such as a journey with its connected resources to production, you should connect your sandbox to your production organization.
-
-To do this, you need to generate an [API Token](/docs/auth/access-tokens) for your sandbox organization and add it to your production organization.
-
-![Create Access Token](/img/create-access-token.png)
-
-Once you have an API token for your sandbox organization, you should log in to your production organization and navigate to [Blueprints > Pipelines to other Organizations](https://portal.epilot.cloud/app/blueprints/pipelines) and select [Connect Organization](https://portal.epilot.cloud/app/blueprints/pipelines/create).
-
-Here you can copy your Sandbox API token to connect your sandbox to your production organization.
-
-![Connect Organization](/img/blueprints/connect-organization.png)
-
-## Switching Between Organizations
-
-To make switching between organizations easier, make sure to invite your user to both organizations, and use the organization switcher in the bottom left corner of the portal.
-
-![Organization Switcher](/img/org-switcher.png)
-
-
-## Importing Between Organizations
-
-Log in to the organization you want to update. If you wish to start by copying existing configuration from production to your sandbox, you should log in to your Sandbox organization. If you want to promote changes from sandox to production, switch to your production organization.
-
-To import configurations via sandbox pipeline, navigate to [Configuration > Blueprints](https://portal.epilot.cloud/app/blueprints) and select [Install Blueprint > Sandbox](https://portal.epilot.cloud/app/blueprints/pipelines/import).
-
-![Sandbox Step 1](/img/blueprints/sandbox-step-1.png)
-
-If the sandbox is already connected to your production organization, you can pick the source organization from the list.
-
-Next, select the resources you want to import from your source organization. You can choose multiple resources here and preview the list of resources that will be imported.
-
-Click on *Select Resources* once you're happy with your selection.
-
-**Note that at this point, no changes will be made to your organization and you can still review the changes before applying!**
-
-You will now see a preview of changes that will be made after applying:
-
-![Sandbox Step 3](/img/blueprints/sandbox-step-3.png)
-
-If you're happy with the changes. Click Approve & Install, and the changes will be applied to the organization you're logged into.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 6218f09..8bf17f7 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -8,7 +8,7 @@ const lightCodeTheme = require('prism-react-renderer/themes/github');
 
 const graphqlMarkdownConfig = require('./graphql-markdown.config');
 const { specs } = require('./redoc.config');
-const DOCS_URL = 'https://docs.epilot.io';
+const DOCS_URL = process.env.DOCS_URL || 'https://docs.epilot.io'
 
 const changelogProcessingDir = path.join(__dirname, 'changelog-processing');
 
diff --git a/static/img/blueprints/1-marketplace-carousel.png b/static/img/blueprints/1-marketplace-carousel.png
new file mode 100644
index 0000000..92bd1b0
Binary files /dev/null and b/static/img/blueprints/1-marketplace-carousel.png differ
diff --git a/static/img/blueprints/1-org-switcher.png b/static/img/blueprints/1-org-switcher.png
new file mode 100644
index 0000000..b28e93c
Binary files /dev/null and b/static/img/blueprints/1-org-switcher.png differ
diff --git a/static/img/blueprints/1-wallbox-description.png b/static/img/blueprints/1-wallbox-description.png
new file mode 100644
index 0000000..0d6999f
Binary files /dev/null and b/static/img/blueprints/1-wallbox-description.png differ
diff --git a/static/img/blueprints/2-add-resource-checkboxes.png b/static/img/blueprints/2-add-resource-checkboxes.png
new file mode 100644
index 0000000..f51ac89
Binary files /dev/null and b/static/img/blueprints/2-add-resource-checkboxes.png differ
diff --git a/static/img/blueprints/2-add-resource-side-panel.png b/static/img/blueprints/2-add-resource-side-panel.png
new file mode 100644
index 0000000..3359d22
Binary files /dev/null and b/static/img/blueprints/2-add-resource-side-panel.png differ
diff --git a/static/img/blueprints/2-add-resource.png b/static/img/blueprints/2-add-resource.png
new file mode 100644
index 0000000..15db099
Binary files /dev/null and b/static/img/blueprints/2-add-resource.png differ
diff --git a/static/img/blueprints/2-advanced-complete.png b/static/img/blueprints/2-advanced-complete.png
new file mode 100644
index 0000000..9e8d369
Binary files /dev/null and b/static/img/blueprints/2-advanced-complete.png differ
diff --git a/static/img/blueprints/2-advanced-pick-resources.png b/static/img/blueprints/2-advanced-pick-resources.png
new file mode 100644
index 0000000..6013638
Binary files /dev/null and b/static/img/blueprints/2-advanced-pick-resources.png differ
diff --git a/static/img/blueprints/2-create-blueprint.png b/static/img/blueprints/2-create-blueprint.png
new file mode 100644
index 0000000..c713df9
Binary files /dev/null and b/static/img/blueprints/2-create-blueprint.png differ
diff --git a/static/img/blueprints/2-one-click-complete.png b/static/img/blueprints/2-one-click-complete.png
new file mode 100644
index 0000000..2ce8fb3
Binary files /dev/null and b/static/img/blueprints/2-one-click-complete.png differ
diff --git a/static/img/blueprints/2-one-click-installation.png b/static/img/blueprints/2-one-click-installation.png
new file mode 100644
index 0000000..7e3f2db
Binary files /dev/null and b/static/img/blueprints/2-one-click-installation.png differ
diff --git a/static/img/blueprints/2-one-click-step-3.png b/static/img/blueprints/2-one-click-step-3.png
new file mode 100644
index 0000000..6c582c1
Binary files /dev/null and b/static/img/blueprints/2-one-click-step-3.png differ
diff --git a/static/img/blueprints/2-portal-marketplace.png b/static/img/blueprints/2-portal-marketplace.png
new file mode 100644
index 0000000..acf8bcc
Binary files /dev/null and b/static/img/blueprints/2-portal-marketplace.png differ
diff --git a/static/img/blueprints/2-resource-toggle.png b/static/img/blueprints/2-resource-toggle.png
new file mode 100644
index 0000000..d1484c5
Binary files /dev/null and b/static/img/blueprints/2-resource-toggle.png differ
diff --git a/static/img/blueprints/3-actions.png b/static/img/blueprints/3-actions.png
new file mode 100644
index 0000000..f09883d
Binary files /dev/null and b/static/img/blueprints/3-actions.png differ
diff --git a/static/img/blueprints/3-blueprint-delete.png b/static/img/blueprints/3-blueprint-delete.png
new file mode 100644
index 0000000..1f89678
Binary files /dev/null and b/static/img/blueprints/3-blueprint-delete.png differ
diff --git a/static/img/blueprints/3-blueprint-download.png b/static/img/blueprints/3-blueprint-download.png
new file mode 100644
index 0000000..4d6550f
Binary files /dev/null and b/static/img/blueprints/3-blueprint-download.png differ
diff --git a/static/img/blueprints/3-continue-to-destination.png b/static/img/blueprints/3-continue-to-destination.png
new file mode 100644
index 0000000..c866e82
Binary files /dev/null and b/static/img/blueprints/3-continue-to-destination.png differ
diff --git a/static/img/blueprints/3-destination-modal.png b/static/img/blueprints/3-destination-modal.png
new file mode 100644
index 0000000..949b3ed
Binary files /dev/null and b/static/img/blueprints/3-destination-modal.png differ
diff --git a/static/img/blueprints/3-edit-blueprint-name.png b/static/img/blueprints/3-edit-blueprint-name.png
new file mode 100644
index 0000000..fe21b3c
Binary files /dev/null and b/static/img/blueprints/3-edit-blueprint-name.png differ
diff --git a/static/img/blueprints/3-installed-blueprint-page.png b/static/img/blueprints/3-installed-blueprint-page.png
new file mode 100644
index 0000000..353a765
Binary files /dev/null and b/static/img/blueprints/3-installed-blueprint-page.png differ
diff --git a/static/img/blueprints/3-installed-blueprints-tab.png b/static/img/blueprints/3-installed-blueprints-tab.png
new file mode 100644
index 0000000..559d294
Binary files /dev/null and b/static/img/blueprints/3-installed-blueprints-tab.png differ
diff --git a/static/img/blueprints/3-remove-resource.png b/static/img/blueprints/3-remove-resource.png
new file mode 100644
index 0000000..9fd2dea
Binary files /dev/null and b/static/img/blueprints/3-remove-resource.png differ
diff --git a/static/img/blueprints/3-resources-impact.png b/static/img/blueprints/3-resources-impact.png
new file mode 100644
index 0000000..47f62c7
Binary files /dev/null and b/static/img/blueprints/3-resources-impact.png differ
diff --git a/static/img/blueprints/3-resources-toc.png b/static/img/blueprints/3-resources-toc.png
new file mode 100644
index 0000000..ada5d92
Binary files /dev/null and b/static/img/blueprints/3-resources-toc.png differ
diff --git a/static/img/blueprints/3-switch-org-screen-selector.png b/static/img/blueprints/3-switch-org-screen-selector.png
new file mode 100644
index 0000000..9299444
Binary files /dev/null and b/static/img/blueprints/3-switch-org-screen-selector.png differ
diff --git a/static/img/blueprints/3-switch-org-screen.png b/static/img/blueprints/3-switch-org-screen.png
new file mode 100644
index 0000000..3c7fe80
Binary files /dev/null and b/static/img/blueprints/3-switch-org-screen.png differ
diff --git a/static/img/blueprints/3-sync-complete-screen.png b/static/img/blueprints/3-sync-complete-screen.png
new file mode 100644
index 0000000..bfa6af9
Binary files /dev/null and b/static/img/blueprints/3-sync-complete-screen.png differ
diff --git a/static/img/blueprints/blueprint-details.png b/static/img/blueprints/blueprint-details.png
deleted file mode 100644
index a56ea31..0000000
Binary files a/static/img/blueprints/blueprint-details.png and /dev/null differ
diff --git a/static/img/blueprints/connect-organization.png b/static/img/blueprints/connect-organization.png
deleted file mode 100644
index e6d63c5..0000000
Binary files a/static/img/blueprints/connect-organization.png and /dev/null differ
diff --git a/static/img/blueprints/connect-pipeline.png b/static/img/blueprints/connect-pipeline.png
deleted file mode 100644
index 0067834..0000000
Binary files a/static/img/blueprints/connect-pipeline.png and /dev/null differ
diff --git a/static/img/blueprints/import-resources-tree.png b/static/img/blueprints/import-resources-tree.png
deleted file mode 100644
index c6dbc5c..0000000
Binary files a/static/img/blueprints/import-resources-tree.png and /dev/null differ
diff --git a/static/img/blueprints/install-blueprint.png b/static/img/blueprints/install-blueprint.png
deleted file mode 100644
index f110756..0000000
Binary files a/static/img/blueprints/install-blueprint.png and /dev/null differ
diff --git a/static/img/blueprints/installed-blueprints.png b/static/img/blueprints/installed-blueprints.png
deleted file mode 100644
index 10a4d29..0000000
Binary files a/static/img/blueprints/installed-blueprints.png and /dev/null differ
diff --git a/static/img/blueprints/pipelines.png b/static/img/blueprints/pipelines.png
deleted file mode 100644
index fc7707e..0000000
Binary files a/static/img/blueprints/pipelines.png and /dev/null differ
diff --git a/static/img/blueprints/sandbox-step-1.png b/static/img/blueprints/sandbox-step-1.png
deleted file mode 100644
index 10ed641..0000000
Binary files a/static/img/blueprints/sandbox-step-1.png and /dev/null differ
diff --git a/static/img/blueprints/sandbox-step-3.png b/static/img/blueprints/sandbox-step-3.png
deleted file mode 100644
index 41ecbb1..0000000
Binary files a/static/img/blueprints/sandbox-step-3.png and /dev/null differ
diff --git a/static/img/blueprints/view-plan.png b/static/img/blueprints/view-plan.png
deleted file mode 100644
index eb63405..0000000
Binary files a/static/img/blueprints/view-plan.png and /dev/null differ