POC: developer landing page

[mesellings]

Description

This POC adds a new standalone (version-agnostic) landing page for developers (similar to the Getting started workflow).

This was prompted by discussion around adding a c8ctl based getting started page into the docs site, which may be followed by downloads pages in further iterations.

This was based on the work done by @MaxTru in another POC PR: #8334.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[mesellings]

Due to problems with preview env, you cannot use the dark/light mode switcher on this page, but you can see it as follows:

• Dark: https://preview.docs.camunda.cloud/pr-8374/build-with-camunda/index.html?docusaurus-theme=dark
• Light: https://preview.docs.camunda.cloud/pr-8374/build-with-camunda/index.html?docusaurus-theme=light

Note there are outstanding discussion items around whether this page needs to live within the versioned docs structure or remain outside it.

• As c8ctl is 8.9 only, the links go to the /next docs and will need to be changed when 8.9 is released.
• All other links go to the current /docs structure (i.e. current version 8.8) but will naturally become more relevant when 8.9 is released (at which point they will go to the 8.9 docs like the c8ctl links)

Additional points:

• If we go ahead with this page into docs prod, we should look at linking to this from the home page itself, and anywhere else that might be relevant.
• Should the URL be /build-with-camunda or something more concise, e.g. /build?
• This page would also benefit from a short video I think, covering a quick start with c8ctl - wdyt @bojtospeter?

[afgambin]

@bojtospeter I did a review pass, LGTM for now. Only pending this comment. I understand we’re adding examples, so please ping me once that’s ready and I’ll do another pass. Thanks!

[PhilippaC22]

couple of things from me:

• I feel that we should bring the pre-requisites up higher on the page? E.g Desktop Modeler OS download options and also info that they need about JDK versions? We do have a getting started page that we could add this information to and just link to that if preferable.

• Sub-heading doesn't make it obvious if I need to do both things. Suggest "Choose how you want to get started with Camunda 8"

• Language in the first SaaS card:
  Fastest start - this may be true but it's not necessarily the chosen path for local developers so I think it depends on which personas we are focussing on, I think free trial and the ~60s to your set-up works better.

Connect via C8 login - unsure about what that means or the value it communicates

• Language in the 2nd run locally CLI card:
  We had some of this type of copy in mind, it needs cutting down and simplifying:

Your infrastructure, your rules. From c8run on your laptop to scaling to enterprise clusters: same runtime and stack.

Built for every stage of the journey. Start locally, deploy anywhere. Design workflows alongside your favorite IDE and keep orchestration on the networks and systems you already trust.

Production-ready from day one. One command to get started, one runtime all the way to production. No surprises, no lock-in — just true dev/prod parity on infrastructure you control.

• not keen on the copy of the 'See the install' CTA - i think it needs a better action word. 'Install and start' 'Download now' 'Run and build' something like that I think might work better.

• Also we have two primary CTA's on the page - Is there a path that we want to promote more? Otherwise it works.

[mesellings]

couple of things from me:

• I feel that we should bring the pre-requisites up higher on the page? E.g Desktop Modeler OS download options and also info that they need about JDK versions? We do have a getting started page that we could add this information to and just link to that if preferable.
• Sub-heading doesn't make it obvious if I need to do both things. Suggest "Choose how you want to get started with Camunda 8"
• Language in the first SaaS card:
  Fastest start - this may be true but it's not necessarily the chosen path for local developers so I think it depends on which personas we are focussing on, I think free trial and the ~60s to your set-up works better.

Connect via C8 login - unsure about what that means or the value it communicates

• Language in the 2nd run locally CLI card:
  We had some of this type of copy in mind, it needs cutting down and simplifying:

Your infrastructure, your rules. From c8run on your laptop to scaling to enterprise clusters: same runtime and stack.
Built for every stage of the journey. Start locally, deploy anywhere. Design workflows alongside your favorite IDE and keep orchestration on the networks and systems you already trust.
Production-ready from day one. One command to get started, one runtime all the way to production. No surprises, no lock-in — just true dev/prod parity on infrastructure you control.

• not keen on the copy of the 'See the install' CTA - i think it needs a better action word. 'Install and start' 'Download now' 'Run and build' something like that I think might work better.
• Also we have two primary CTA's on the page - Is there a path that we want to promote more? Otherwise it works.

Thanks @PhilippaC22 - @afgambin FYI 👍

[afgambin]

Thanks @PhilippaC22 - I’ve addressed your feedback. A few comments:

I think we should move the prerequisites higher on the page (e.g., Desktop Modeler OS download options and the required JDK versions). We do have a Getting Started page where we could add this information and link to it, if preferable.

Desktop Modeler isn’t really an installation prerequisite. Obviously, it will be needed for design purposes later on. Ideally, as I mentioned above, c8ctl would come with it preinstalled as part of a bundle.

The subheading doesn’t make it obvious whether I need to do both things. I suggest: “Choose how you want to get started with Camunda 8.”

I’ve applied the suggestion and simplified the subheading.

“Connect via C8 login” — I’m unsure what that means or what value it communicates.

I agree, I reworked the sentence and added the AI skills set, which I believe is also available in SaaS.

Language in the second “Run locally” CLI card: we had some copy like this in mind, but it needs to be cut down and simplified.

I’ve simplified the text and applied the suggestion.

I’m not keen on the copy for the “See the install” CTA — I think it needs a stronger action verb (e.g., “Install and start,” “Download now,” “Run and build,” etc.).

Agree, I updated it to “Install now.”

Also, we have two primary CTAs on the page. Is there one path we want to promote more? Otherwise, this works.

Based on previous conversations, I believe we don’t want to prioritize one over the other (I had the same question), but I’m not sure if that’s still the case for this page.

[github-actions]

The preview environment relating to the commit 6f52759 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-8374/