update: Database service management reuse - PART 2

[wojcik-dorota]

https://aiven.atlassian.net/browse/DOC-1948

Created per-service articles from the 7 component groups — only where the service supports the feature (verified against aiven-core), with service-specific info, placed in the correct IA sections.

Feature → article | Section | Services:

• Change service plan | Scaling and performance | all 6
• Prepare for high load | Scaling and performance | all 6
• Scale disk storage | Scaling and performance | PG, MySQL, OpenSearch, Valkey
• Maintenance and updates (updates + window) | Maintenance and lifecycle | all 6
• Change cloud or region | Service management | all 6 (PG reuses its existing page)
• Track restore progress | Backups and migration (Metrics: Maintenance) | all 6
• Backup to another region (BTAR) | Backups and migration | all except Metrics
• Memory + out-of-memory | Scaling and performance | new pages for OpenSearch/Grafana/Metrics; merged into existing memory pages for PG/MySQL/Valkey

Also:

• 6 new section overview pages (OpenSearch Scaling; Grafana Scaling/Maintenance/Backups; Metrics Scaling/Maintenance), wired as category landing pages — new sections were created for OpenSearch/Grafana/Metrics that didn't have them.
• Moved PG's existing migrate-cloud-region into Service management (its content already uses the change-cloud-console include).

Three includes needed fixes to build (they were provided incomplete/latent-buggy):

• maintenance-updates.md and maintenance-window-instructions.md — added the missing ConsoleLabel/Tabs/TabItem imports (they used the components without importing them).
• service-memory-limits.md — the ${ RAM - overhead }$ line was parsed by MDX as a JS expression (RAM is not defined, broke the build). Rewrote it as inline code (usable memory = RAM - overhead).

Finally, for Metrics (no backups/fork), I put Track restore progress under Maintenance and lifecycle rather than creating a "Backups and migration" section that would be misleading.

[cloudflare-workers-and-pages]

Deploying aiven-docs with    Cloudflare Pages

Latest commit:	d1199d6
Status:	✅  Deploy successful!
Preview URL:	https://fbc5d41d.aiven-docs.pages.dev
Branch Preview URL:	https://doc-1948-db-part-2-service-m.aiven-docs.pages.dev

View logs

[UX-Irene]

Great work Dorota, your all done!
Last part we need to discuss with the team is if the EOL should be on the Service level or not. Perhaps this is more a generic section somewhere.

[UX-Irene]

Perfect, it all looks consistent and works well. thanks for all this effort to make the Docs navigation more consistent.