adjust guides naming

[christinaausley]

Description

Closes https://github.com/camunda/developer-experience/issues/253.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

Will backport upon approval.

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

@mesellings @conceptualshark I'm just playing around with ideas in this PR for effective Guides naming. Do you have any thoughts, suggestions, opinions?

[mesellings]

I like these changes a lot - they make perfect sense - just one note about the Connectors naming, otherwise great work! 🚀

[christinaausley]

Thank you for the review @mesellings! Backported 👍

[github-actions]

The preview environment relating to the commit 0b8f1d1 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4553/index.html

[mesellings]

Lgtm 👍 🥇