test build for restructure

[christinaausley]

This PR is NOT in a state to merge and should only be for discussion purposes.

• Move all guides from Components to Guides
  • Get started (as-is)
  • Manage > Console guides (as-is)
  • Design > Modeler (requires extensive review, difficult to split or move as-is)
  • Automate > Connectors, Zeebe, Tasklist, Operate
    • Connectors (requires review, content split between Guides & Concepts)
    • Zeebe (all concepts, no guides)
    • Tasklist (move user guide, drop overview/intro page)
    • Operate (move user guide, drop overview/intro page)
  • Improve > Optimize (move user guide, drop overview/intro page)
  • Migrate from C7
• Rename Components to Concepts
• Rework any renaming content in Concepts to a cohesive structure

But I love it! Why can't we just merge this?!

• No actual content moves, just sidebars moves
• No redirects
• No buy-in from stakeholders (yet, hence the draft PR for discussions)
• Renaming a top nav item will impact all supported versions
• Possible duplicate/redundant guide content
• Lacks holistic perspective/intention for Guide and Concepts (could be fixed with an extensive review)

[github-actions]

👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/components/components-overview.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[github-actions]

🚧 The preview environment for the commit f0586d4 is being built. This usually takes 15-20 minutes.

[korthout]

👍 I really like that we don't ship our architecture in the docs as the top-level anymore, and instead introduce the usage patterns in the guides: manage, design, automate, and improve. A user wants to follow a guide to solve a problem or reach a goal. So, IMO, this fits much better