site: add learning paths

[dvdksn]

@netlify /learning-paths/

Description

This PR adds another top-level section to the site: Learning paths

Learning paths are articles that guide users through a series of articles, videos, and other resources to help them learn a Docker product, feature, or concept.

The learning paths are linked in the site's top navigation bar, and have a dedicated page that lists all available learning paths.

Learning path pages are similar to the guide overviews, listing a number of modules that make up the learning path.
Paths have the following metadata:

title: "Learning path title"
description: "A brief description of the learning path" # meta description for SEO
summary: "A brief summary of the learning path" # excerpt and summary for the page
params:
  image: "/images/path-image.jpg" # path timage
  skill: "Beginner" # skill level
  time: "1 hour" # estimated time to complete
  prereq: "Docker installed" # prerequisites

The layout of each learning path is as follows:

• Title
• Summary
• Guide stats (skill level, time, prerequisites)
• Subject overview
• What you'll learn
• Tools integration
• Who's this for?
• Modules (list of modules in the learning path)

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	7083355
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/66c6f5a638baba00080cf682
😎 Deploy Preview	https://deploy-preview-20563--docsdocker.netlify.app/learning-paths/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sbenhoff007]

On the Docker Compose page, the URL for Control Startup and Shutdown Order with Compose is wrong. It should be: https://docs.docker.com/compose/startup-order/

It was like that in the Google doc and I've updated it.

[sbenhoff007]

On the Docker Scout page, remove the "Modules" heading.

[dvdksn]

On the Docker Scout page, remove the "Modules" heading.

I am thinking about keeping the heading, just for the sake of a reasonable HTML document structure. The previous heading otherwise becomes "Tools integration" which doesn't make sense semantically. So I will add it in to the build cloud page instead (where it was missing)

[aevesdocker]

Few nits that can be done in a follow up. Otherwise, looks great

[usha-mandya]