[feat] update angular sample guide to use dhi example (#23820)

## Description

This PR adds a DHI-based Dockerfile example demonstrating how to build
an Angular application using the dhi-node image and serve it through the
dhi-nginx image.

## Reviews


- [x] Technical review

Author: kristiyan-velkov

content/guides/angular/containerize.md

@@ -28,7 +28,7 @@ By the end of this guide, you will:
 - Containerize an Angular application using Docker.
 - Create and optimize a Dockerfile for production builds. 
 - Use multi-stage builds to minimize image size.
-- Serve the application efficiently with a custom NGINX configuration.
+- Serve the application efficiently with a custom Nginx configuration.
 - Build secure and maintainable Docker images by following best practices.
 
 ---
@@ -77,7 +77,7 @@ For consistency, please use the same responses shown in the example below when p
 | Question                                                   | Answer          |
 |------------------------------------------------------------|-----------------|
 | What application platform does your project use?           | Node            |
-| What version of Node do you want to use?                   | 23.11.0-alpine  |
+| What version of Node do you want to use?                   | 24.12.0-alpine  |
 | Which package manager do you want to use?                  | npm             |
 | Do you want to run "npm run build" before starting server? | yes             |
 | What directory is your build output to?                    | dist            |
@@ -105,7 +105,7 @@ The default Dockerfile generated by `docker init` serves as a solid starting poi
 In this step, you’ll improve the Dockerfile and configuration files by following best practices:
 
 - Use multi-stage builds to keep the final image clean and small  
-- Serve the app using NGINX, a fast and secure web server  
+- Serve the app using Nginx, a fast and secure web server  
 - Improve performance and security by only including what’s needed  
 
 These updates help ensure your app is easy to deploy, fast to load, and production-ready.
@@ -114,19 +114,90 @@ These updates help ensure your app is easy to deploy, fast to load, and producti
 > A `Dockerfile` is a plain text file that contains step-by-step instructions to build a Docker image. It automates packaging your application along with its dependencies and runtime environment.  
 > For full details, see the [Dockerfile reference](/reference/dockerfile/).
 
-
 ### Step 2: Configure the Dockerfile
 
-Copy and replace the contents of your existing `Dockerfile` with the configuration below:
+Before creating a Dockerfile, you need to choose a base image. You can either use the [Node.js Official Image](https://hub.docker.com/_/node) or a Docker Hardened Image (DHI) from the [Hardened Image catalog](https://hub.docker.com/hardened-images/catalog).
+
+Choosing DHI offers the advantage of a production-ready image that is lightweight and secure. For more information, see [Docker Hardened Images](https://docs.docker.com/dhi/).
+
+> [!IMPORTANT]
+> This guide uses a stable Node.js LTS image tag that is considered secure when the guide is written. Because new releases and security patches are published regularly, the tag shown here may no longer be the safest option when you follow the guide. Always review the latest available image tags and select a secure, up-to-date version before building or deploying your application.
+>
+> Official Node.js Docker Images: https://hub.docker.com/_/node
+
+{{< tabs >}}
+{{< tab name="Using Docker Hardened Images" >}}
+Docker Hardened Images (DHIs) are available for Node.js in the [Docker Hardened Images catalog](https://hub.docker.com/hardened-images/catalog/dhi/node). Docker Hardened Images are freely available to everyone with no subscription required. You can pull and use them like any other Docker image after signing in to the DHI registry. For more information, see the [DHI quickstart](/dhi/get-started/) guide.
+
+1. Sign in to the DHI registry:
+   ```console
+   $ docker login dhi.io
+   ```
+
+2. Pull the Node.js DHI (check the catalog for available versions):
+   ```console
+   $ docker pull dhi.io/node:24-alpine3.22-dev
+   ```
+
+In the following Dockerfile, the `FROM` instruction uses `dhi.io/node:24-alpine3.22-dev` as the base image.
 
 ```dockerfile
 # =========================================
 # Stage 1: Build the Angular Application
 # =========================================
+
+# Use a lightweight DHI Node.js image for building
+FROM dhi.io/node:24-alpine3.22-dev AS builder
+
+# Set the working directory inside the container
+WORKDIR /app
+
+# Copy package-related files first to leverage Docker's caching mechanism
+COPY package.json package-lock.json* ./
+
+# Install project dependencies using npm ci (ensures a clean, reproducible install)
+RUN --mount=type=cache,target=/root/.npm npm ci
+
+# Copy the rest of the application source code into the container
+COPY . .
+
+# Build the Angular application
+RUN npm run build 
+
+# =========================================
+# Stage 2: Prepare Nginx to Serve Static Files
+# =========================================
+
+FROM dhi.io/nginx:1.28.0-alpine3.21-dev AS runner
+
+# Copy custom Nginx config
+COPY nginx.conf /etc/nginx/nginx.conf
+
+# Copy the static build output from the build stage to Nginx's default HTML serving directory
+COPY --chown=nginx:nginx --from=builder /app/dist/*/browser /usr/share/nginx/html
+
+# Use a non-root user for security best practices
+USER nginx
+
+# Expose port 8080 to allow HTTP traffic
+# Note: The default Nginx container now listens on port 8080 instead of 80 
+EXPOSE 8080
+
+# Start Nginx directly with custom config
+ENTRYPOINT ["nginx", "-c", "/etc/nginx/nginx.conf"]
+CMD ["-g", "daemon off;"]
+```
+
+{{< /tab >}}
+{{< tab name="Using the Docker Official Image" >}}
+
+Now you need to create a production-ready multi-stage Dockerfile. Replace the generated Dockerfile with the following optimized configuration:
+
+```dockerfile
 # =========================================
 # Stage 1: Build the Angular Application
 # =========================================
-ARG NODE_VERSION=24.7.0-alpine
+ARG NODE_VERSION=24.12.0-alpine
 ARG NGINX_VERSION=alpine3.22
 
 # Use a lightweight Node.js image for building (customizable via ARG)
@@ -136,7 +207,7 @@ FROM node:${NODE_VERSION} AS builder
 WORKDIR /app
 
 # Copy package-related files first to leverage Docker's caching mechanism
-COPY package.json package-lock.json ./
+COPY package.json *package-lock.json* ./
 
 # Install project dependencies using npm ci (ensures a clean, reproducible install)
 RUN --mount=type=cache,target=/root/.npm npm ci
@@ -153,32 +224,34 @@ RUN npm run build
 
 FROM nginxinc/nginx-unprivileged:${NGINX_VERSION} AS runner
 
-# Use a built-in non-root user for security best practices
-USER nginx
-
 # Copy custom Nginx config
 COPY nginx.conf /etc/nginx/nginx.conf
 
 # Copy the static build output from the build stage to Nginx's default HTML serving directory
 COPY --chown=nginx:nginx --from=builder /app/dist/*/browser /usr/share/nginx/html
 
+# Use a built-in non-root user for security best practices
+USER nginx
+
 # Expose port 8080 to allow HTTP traffic
-# Note: The default NGINX container now listens on port 8080 instead of 80 
+# Note: The default Nginx container now listens on port 8080 instead of 80 
 EXPOSE 8080
 
 # Start Nginx directly with custom config
 ENTRYPOINT ["nginx", "-c", "/etc/nginx/nginx.conf"]
 CMD ["-g", "daemon off;"]
-
 ```
 
 > [!NOTE]
-> We are using nginx-unprivileged instead of the standard NGINX image to follow security best practices.
+> We are using nginx-unprivileged instead of the standard Nginx image to follow security best practices.
 > Running as a non-root user in the final image:
 >- Reduces the attack surface
 >- Aligns with Docker’s recommendations for container hardening
 >- Helps comply with stricter security policies in production environments
 
+{{< /tab >}}
+{{< /tabs >}}
+
 ### Step 3: Configure the .dockerignore file
 
 The `.dockerignore` file tells Docker which files and folders to exclude when building the image.
@@ -259,12 +332,12 @@ docker-compose*.yml
 
 ### Step 4: Create the `nginx.conf` file
 
-To serve your Angular application efficiently inside the container, you’ll configure NGINX with a custom setup. This configuration is optimized for performance, browser caching, gzip compression, and support for client-side routing.
+To serve your Angular application efficiently inside the container, you’ll configure Nginx with a custom setup. This configuration is optimized for performance, browser caching, gzip compression, and support for client-side routing.
 
 Create a file named `nginx.conf` in the root of your project directory, and add the following content:
 
 > [!NOTE]
-> To learn more about configuring NGINX, see the [official NGINX documentation](https://nginx.org/en/docs/).
+> To learn more about configuring Nginx, see the [official Nginx documentation](https://nginx.org/en/docs/).
 
 
 ```nginx
@@ -351,7 +424,7 @@ With your custom configuration in place, you're now ready to build the Docker im
 
 The updated setup includes:
 
-- The updated setup includes a clean, production-ready NGINX configuration tailored specifically for Angular.
+- The updated setup includes a clean, production-ready Nginx configuration tailored specifically for Angular.
 - Efficient multi-stage Docker build, ensuring a small and secure final image.
 
 After completing the previous steps, your project directory should now contain the following files:

content/guides/angular/develop.md

@@ -38,7 +38,7 @@ Create a file named `Dockerfile.dev` in your project root with the following con
 # =========================================
 
 # Define the Node.js version to use (Alpine for a small footprint)
-ARG NODE_VERSION=24.7.0-alpine
+ARG NODE_VERSION=24.12.0-alpine
 
 # Set the base image for development
 FROM node:${NODE_VERSION} AS dev
@@ -50,7 +50,7 @@ ENV NODE_ENV=development
 WORKDIR /app
 
 # Copy only the dependency files first to optimize Docker caching
-COPY package.json package-lock.json ./
+COPY package.json package-lock.json* ./
 
 # Install dependencies using npm with caching to speed up subsequent builds
 RUN --mount=type=cache,target=/root/.npm npm install