docs: reorganize CLI commands into categorical folders

[thebiglabasky]

Summary

• Reorganizes the 17 CLI command reference pages into 5 semantic subfolders under cli/
• checkly skills stays at the CLI root as the cross-cutting AI entry point
• All internal links and docs.json navigation updated

Proposed structure

cli/
├── checkly-skills.mdx              ← root level
├── account/      → login, logout, switch, whoami, runtimes
├── configure/    → env, import, sync-playwright
├── testing/      → test, pw-test
├── monitoring/   → deploy, destroy, trigger, checks
└── communicate/  → incidents, status-pages

Alternative: condensed (3 folders)

If 5 subgroups feels like too much, here's a more condensed option:

cli/
├── checkly-skills.mdx              ← root level
├── account/      → login, logout, switch, whoami, runtimes, env, import, sync-playwright
├── workflow/     → test, pw-test, deploy, destroy, trigger, checks
└── communicate/  → incidents, status-pages

This merges configure/ into account/ and testing/ + monitoring/ into a single workflow/ group.

Test plan

• Verify sidebar navigation renders correctly with nested groups
• Spot-check internal links resolve to the correct pages
• Review folder groupings with team

🤖 Generated with Claude Code

[stefanjudis]

Uff... This is very hard and I can't really say I have a strong opinion here, but my first thought was leaning towards actions and resources. actions might not be the right word, but yeah... I thought of this.

cli/
├── checkly-skills.mdx     ← root level
├── actions/       → login, logout, switch, whoami, runtimes, import, sync-playwright, deploy, destroy, trigger, pw-test
├── platform/      → env, runtimes, checks, incidents, status-pages

This is very hard. But I'm generally on board with your proposal. This won't perfect but we need to start grouping things.

[stefanjudis]

heads up: you'll have to set "a thousand" redirects in the marketing repo then. :)

[thebiglabasky]

Urf. True. Are there ways to keep folders without changing the URL? 🤓

[thebiglabasky]

Uff... This is very hard and I can't really say I have a strong opinion here, but my first thought was leaning towards actions and resources. actions might not be the right word, but yeah... I thought of this.

cli/
├── checkly-skills.mdx     ← root level
├── actions/       → login, logout, switch, whoami, runtimes, import, sync-playwright, deploy, destroy, trigger, pw-test
├── platform/      → env, runtimes, checks, incidents, status-pages

This is very hard. But I'm generally on board with your proposal. This won't perfect but we need to start grouping things.

Yes, I'm very open to alternatives. I think it depends on what we want to convey in terms of "areas" the CLI covers. The current way made me feel overall OK about the match between the commands and their respective folders, so I'd be fine with this for a start.

At least as long as we don't need to do redirects 😬