new Learn section for general monitoring guides

[serverless-mom]

Not currently ready to merge, @tnolet I'm struggling to get documents added to a new subfolder/section, I'm clearly missing a config step that changed since your re-work. I'd love your guidance. The idea is to have a top-level 'Monitoring' section.

Affected Components

• Content & Marketing
• Pricing
• Test
• Docs
• Learn
• Other

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
checklyhq-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 19, 2024 6:06pm

[tnolet]

@serverless-mom I'll check it tomorrow. Probably something simple

[tnolet]

@serverless-mom looks all good to me! I just changed the navTitle for one of the new articles. But the structure works fine AFAICS. 👇

What's happening under the hood is that you are defining a new "menu" (this is a Hugo thing) by just mentioning it in the front matter of the new articles, learn_monitoring. This is an ad hoc way of creating menu structures. It is an alternative to defining them in the config.toml, see the Hugo docs on that topic.

I think that is fine. If there is only one content level, as we have for Kubernetes, K8S and now Monitoring this is a simple and effective way. For PWT we have multiple layers, so then it makes sense to define it upfront in the config.toml.

CleanShot.2024-12-16.at.10.50.13.mp4