E2E docs experience getting started guides

[akeller]

Description

For scope and updates, see https://camunda.slack.com/archives/C077J92G8LX.

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.
• [x] 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.
• [x] My changes are for the next minor and are in /docs directory (aka /next/).

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

[github-actions[bot]]

:wave: :robot: :thinking: Hello! 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.5/.

• docs/guides/getting-started-java-spring.md
• docs/guides/getting-started-orchestrate-apis.md
• docs/guides/getting-started-orchestrate-human-tasks.md
• docs/guides/getting-started-orchestrate-microservices.md
• docs/guides/model-your-first-process.md
• docs/guides/react-components/install-docker-compose.md
• docs/guides/react-components/install-plain-java.md
• docs/guides/react-components/saas-prerequisites.md
• docs/guides/react-components/sm-prerequisites.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[bot]]

Your preview env has been torn down.

[akeller]

@MaxTru I'm struggling with your feedback - the Connectors runtime and injecting Connectors into Desktop Modeler would impact the "Get Started with API Orchestration" guide, right? Not "Get Started with Microservice Orchestration"? Or both?

=> Isn't this a fundamental flaw in our Connectors SM Install documentation? Maybe it would make sense if the Connectors team documents how to install connectors in SM without HELM and Web Modeler, and then you can link to that?

Yes, 100%. To keep this iterative, I can remove the SM steps in the Get Started with API Orchestration guide for now.

And 10000% I would love to get a culture of testing the guides. We have significantly reduced capacity in DevEx until after the retreat. I'm still having issues running the plain java install on my own machine, but I have time set aside to try again.

[MaxTru]

@MaxTru I'm struggling with your feedback - the Connectors runtime and injecting Connectors into Desktop Modeler would impact the "Get Started with API Orchestration" guide, right? Not "Get Started with Microservice Orchestration"? Or both?

You are right - it is about "Get started with API Orchestration". Sorry!

[MaxTru]

=> Isn't this a fundamental flaw in our Connectors SM Install documentation? Maybe it would make sense if the Connectors team documents how to install connectors in SM without HELM and Web Modeler, and then you can link to that?

Yes, 100%. To keep this iterative, I can remove the SM steps in the Get Started with API Orchestration guide for now.

Can you surface this with Connectors (EM, and PMs)? I can also support if that helps you.