Merge pull request #131 from tebanieo/modernizr

Updating Modernizr references to Modernizer, to avoid confusion

Author: tebanieo

content/modernizr/00-preparation/index.en.md renamed to content/modernizer/00-preparation/index.en.md

@@ -13,29 +13,29 @@ Before beginning the modernization process, you need to configure your developme
 
 Navigate to the workshop studio page and access the "Outputs" tab to retrieve your environment credentials:
 
-![Workshop studio tab](/static/images/modernizr/0/setup-01.png)
+![Workshop studio tab](/static/images/modernizer/0/setup-01.png)
 
 Locate these two important values:
 - **VSCodeServerPassword** - Authentication credential for your VS Code instance
-- **VSCodeServerURLModernizr** - Direct endpoint to your cloud-based IDE
+- **VSCodeServerURLModernizer** - Direct endpoint to your cloud-based IDE
 
 Your values are unique to you and will differ from the above example.
 
-Click the `VSCodeServerURLModernizr` to launch your development environment. Enter the password when prompted and allow approximately 60 seconds for the environment to initialize. Any startup notifications can be safely dismissed.
+Click the `VSCodeServerURLModernizer` to launch your development environment. Enter the password when prompted and allow approximately 60 seconds for the environment to initialize. Any startup notifications can be safely dismissed.
 
 ## Step 2: Configuring the Cline AI Agent
 
 Your workspace includes **Cline**, an autonomous AI coding agent that will assist with the modernization process. Cline provides intelligent code analysis, generation, and refactoring capabilities throughout this workshop.
 
 Access the [Cline](https://cline.bot/) extension through the VS Code interface:
 
-![Cline plugin](/static/images/modernizr/0/setup-02.png)
+![Cline plugin](/static/images/modernizer/0/setup-02.png)
 
 ## Step 3: Establishing Bedrock Integration
 
 Configure Cline to use Amazon Bedrock as its foundation model provider. Select "Use your own API Key" and choose "Amazon Bedrock" from the dropdown:
 
-![Cline plugin API config](/static/images/modernizr/0/setup-03.png)
+![Cline plugin API config](/static/images/modernizer/0/setup-03.png)
 
 Apply the following configuration parameters:
 - **Authentication**: AWS Profile
@@ -45,7 +45,7 @@ Apply the following configuration parameters:
 
 Confirm the settings and initialize the connection:
 
-![Cline plugin config](/static/images/modernizr/0/setup-04.png)
+![Cline plugin config](/static/images/modernizer/0/setup-04.png)
 
 
 ::alert[You are working in a lab environment, the foundational models have configured rate limiting, it is highly likely during the workshop you will get throttled and you will have to retry the operations. You have 4 request per minute using Claude 4 and 6 request per minute using Claude 3.7.]{type="info"}
@@ -59,11 +59,11 @@ Verify the Bedrock connection is functioning correctly by sending the below test
 Hello and Welcome to this modernization project, can you confirm you can read and list all the files in the workspace?
 ```
 
-![Cline plugin testing](/static/images/modernizr/0/setup-05.png)
+![Cline plugin testing](/static/images/modernizer/0/setup-05.png)
 
 This workshop provides access to two foundation models: `claude-sonnet-4` (latest generation with enhanced reasoning capabilities) and `claude-sonnet-3.7` (previous generation with proven reliability).
 
-![Cline plugin response](/static/images/modernizr/0/setup-06.png) ![Cline plugin result](/static/images/modernizr/0/setup-07.png)
+![Cline plugin response](/static/images/modernizer/0/setup-06.png) ![Cline plugin result](/static/images/modernizer/0/setup-07.png)
 
 ## Step 5: Configuring Auto-Approval Settings
 
@@ -76,13 +76,13 @@ Enable the following capabilities:
 
 Increase the **Max requests** parameter from 20 to 40 to accommodate complex multi-step operations without interruption.
 
-![Cline plugin auto-approve settings](/static/images/modernizr/0/setup-08.png)
+![Cline plugin auto-approve settings](/static/images/modernizer/0/setup-08.png)
 
 ## Step 6: Verifying MCP Server Status
 
 Access the MCP server management interface (stacked server icon) to confirm all specialized AI tools are operational. You should observe 3 active servers with green status indicators, confirming proper connectivity.
 
-![Cline plugin auto-approve settings](/static/images/modernizr/0/setup-09.png)
+![Cline plugin auto-approve settings](/static/images/modernizer/0/setup-09.png)
 
 ## Step 7: MCP Integration Verification
 
@@ -92,7 +92,7 @@ Test the MCP server functionality by querying existing DynamoDB resources:
 Please show me the DynamoDB tables that I have in this region
 ```
 
-![Task MCP Server](/static/images/modernizr/0/setup-10.png)
+![Task MCP Server](/static/images/modernizer/0/setup-10.png)
 
 ## Environment Ready
 

content/modernizr/01-modernization/index.en.md renamed to content/modernizer/01-modernization/index.en.md

@@ -1,5 +1,5 @@
 ---
-title: "Database Modernizr Workflow"
+title: "Database Modernizer Workflow"
 date: 2025-09-01T10:41:04-05:00
 weight: 30
 chapter: true
@@ -13,7 +13,7 @@ Begin by reviewing the application documentation in the `README.md` file, which
 
 ::alert[You don't have to follow the `README.md` instructions as your environment is already pre-configured for you. ]{type="info"}
 
-![README](/static/images/modernizr/1/workflow-01.png)
+![README](/static/images/modernizer/1/workflow-01.png)
 
 ## Starting the Application Services
 
@@ -28,7 +28,7 @@ While your application environment is already preconfigured, you'll still need t
 
 The backend API server manages all client requests and database transactions. Navigate to the `/backend` directory and open an integrated terminal (right-click > "Open in Integrated Terminal"). Grant any requested permissions when prompted.
 
-![menu](/static/images/modernizr/1/workflow-02.png)
+![menu](/static/images/modernizer/1/workflow-02.png)
 
 Build and start the backend service using these commands:
 
@@ -87,15 +87,15 @@ Verify the API server is responding correctly by accessing the health endpoint:
 
 This endpoint should return status information confirming the backend is operational:
 
-![Backend](/static/images/modernizr/1/workflow-03.png)
+![Backend](/static/images/modernizer/1/workflow-03.png)
 
 Monitor your backend terminal for request logging, which demonstrates the API request flow.
 
 ### Frontend Application Access
 
 Access the e-commerce frontend by navigating to `[your-url]/store/`:
 
-![Store](/static/images/modernizr/1/workflow-04.png)
+![Store](/static/images/modernizer/1/workflow-04.png)
 
 ## System Interaction Analysis
 

content/modernizr/01-modernization/workflow-00.en.md renamed to content/modernizer/01-modernization/workflow-00.en.md

@@ -12,7 +12,7 @@ Think of database modernization like renovating a house while people are still l
 
 Our process consists of seven carefully designed stages, each one building on the previous step. It's like following a recipe — each ingredient needs to be added at the right time and in the right order to get the perfect result.
 
-![Modernization workflow](/static/images/modernizr/1/workflow-base-01.png)
+![Modernization workflow](/static/images/modernizer/1/workflow-base-01.png)
 
 ## Stage 1: Understanding What You Have — Database Detective Work
 

content/modernizr/01-modernization/workflow-01.en.md renamed to content/modernizer/01-modernization/workflow-01.en.md

@@ -10,7 +10,7 @@ chapter: false
 
 The `/prompts` directory implements a structured approach to AI-driven development through organized subfolders that correspond to each stage of the modernization workflow. Each subfolder contains three components: Requirements, Design, and Tasks documents. This architectural pattern creates a comprehensive framework that systematically guides the entire modernization process from initial analysis through final implementation.
 
-![Prompts](/static/images/modernizr/1/workflow-prompt-01.png)
+![Prompts](/static/images/modernizer/1/workflow-prompt-01.png)
 
 ### Requirements Documentation — Defining Objectives and Success Criteria
 
@@ -32,4 +32,4 @@ The structured approach provides several advantages. The LLM receives explicit g
 
 To conceptualize this framework using a navigation analogy: the Requirements document defines the destination and the reasons for traveling there, the Design document provides the comprehensive route map showing all available paths and optimal strategies, and the Tasks document functions as turn-by-turn GPS navigation that guides execution through each specific step of the journey. This structured approach transforms complex modernization challenges into systematic, manageable processes that can be executed reliably through AI-assisted development workflows.
 
-![Tasks](/static/images/modernizr/1/workflow-prompt-02.png)
+![Tasks](/static/images/modernizer/1/workflow-prompt-02.png)

content/modernizr/01-modernization/workflow-02.en.md renamed to content/modernizer/01-modernization/workflow-02.en.md

@@ -14,7 +14,7 @@ Each stage generates "Artifacts" — deliverables that will be used in the futur
 
 Let's start exploring the artifacts available for the first stage `stage-01`. This stage is focused on capturing the data that is available from the source database and application backend logic. We use the MySQL MCP server to understand table structure, constraints and data. Next we use the MySQL query logs to identify the data . Finally, we explore the application logic to capture all the access patterns that we will need to modernize. 
 
-![Artifacts](/static/images/modernizr/1/workflow-artifacts-01.png)
+![Artifacts](/static/images/modernizer/1/workflow-artifacts-01.png)
 
 DynamoDB is all about application the access patterns that we need to support. The secret to DynamoDB data modelling is to store data exactly in the format your application will consume it, structing your data in a way that can be read as efficiently as possible with the smallest number of queries.
 

content/modernizr/01-mysql-mcp/index.en.md renamed to content/modernizer/01-mysql-mcp/index.en.md

@@ -33,7 +33,7 @@ Rather than following prescriptive instructions, focus on understanding the core
 
 This picture is an Entity Relationship Mapping that will help you understand in detail what it needs to be modeled. 
 
-![Start conversation](/static/images/modernizr/2/stage02-10.png)
+![Start conversation](/static/images/modernizer/2/stage02-10.png)
 
 ## Entity Relationship Mapping
 

content/modernizr/02-data-modeling/data-modeling-01.en.md renamed to content/modernizer/02-data-modeling/data-modeling-01.en.md

@@ -151,23 +151,23 @@ We will add two indexes, that are possible future hot partitions, but with the n
 - **Warning:** Monitor for hot partitions with high-volume sellers
 ```
 
-![User entitiy modifcation](/static/images/modernizr/2/stage02-11.png)
+![User entitiy modifcation](/static/images/modernizer/2/stage02-11.png)
 
 Make sure all the modifications are stored in the `working_log.md` file! sometimes `Cline` ignores what you say!!
 
-![Working Log](/static/images/modernizr/2/stage02-12.png)
+![Working Log](/static/images/modernizer/2/stage02-12.png)
 
 In my specific scenario, `Cline` was having a hard time understanding it needed to create the GSIs and it wasn't including them in the data model. It is your responsibility to make sure every access patterns is properly identified and recorded, remember this is the base of data modeling and all the future steps depend on the decisions you make at this point. 
 
-![Working Log](/static/images/modernizr/2/stage02-13.png)
+![Working Log](/static/images/modernizer/2/stage02-13.png)
 
 Even at some points it actually suggested me to have a different table for my shopping cart entity. 
 
-![Working Log](/static/images/modernizr/2/stage02-14.png)
+![Working Log](/static/images/modernizer/2/stage02-14.png)
 
 But with a little patience, and making sure all the data is there I was able to guide `Cline` to obtain the outcome and table structure that we originally intended. 
 
-![Working Log](/static/images/modernizr/2/stage02-15.png)
+![Working Log](/static/images/modernizer/2/stage02-15.png)
 
 Before completing this workshop section, make sure the content you approve is valid, we are trying to use one table with 3 different entities, one for User metadata, another for User cart items and finally one for User orders! If in your case you are still getting suggestions to have another table for orders or shopping cart items, make sure you tell `Cline` we don't need it anymore. 
 

content/modernizr/02-data-modeling/data-modeling-02.en.md renamed to content/modernizer/02-data-modeling/data-modeling-02.en.md

@@ -135,6 +135,6 @@ We will add two indexes, that are possible future hot partitions, but with the n
 - **Warning:** Monitor for hot partitions with high-volume sellers
 ```
 
-![Working Log](/static/images/modernizr/2/stage02-16.png)
+![Working Log](/static/images/modernizer/2/stage02-16.png)
 
 In my execution, I was getting throttled, please remember to be patient and just retry! but also review the changes made by `Cline`.

content/modernizr/02-data-modeling/data-modeling-03.en.md renamed to content/modernizer/02-data-modeling/data-modeling-03.en.md

@@ -170,12 +170,12 @@ GSI1: Category Hierarchy Lookup (Migration Support)
 
 Always remember to check if the input was added in the working log and the instructions were followed.
 
-![Working Log](/static/images/modernizr/2/stage02-17.png)
+![Working Log](/static/images/modernizer/2/stage02-17.png)
 
 Make sure that everything that is not needed, such other tables that might have been suggested before are not longer there, we don't need to send noise when we will re-generate the data model. 
 
-![Working Log](/static/images/modernizr/2/stage02-18.png)
+![Working Log](/static/images/modernizer/2/stage02-18.png)
 
 At this point `Cline` should tell you the summary of the work, and that it has effectively created a 3 table architecture. 
 
-![Working Log](/static/images/modernizr/2/stage02-19.png)
+![Working Log](/static/images/modernizer/2/stage02-19.png)