draft bpmn copilot

[christinaausley]

Description

Relates to feedback iteration of the Web Modeler BPMN copilot with https://github.com/camunda/product-hub/issues/2511.

Before merging, must confirm:

• Screenshot is accurate based on product UI.
• Links are provided for feedback and opting into the feature.
• Confirmed this iteration is either alpha or experimental.

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/).

• 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]

👋 🤖 🤔 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/early-access/alpha/bpmn-copilot/bpmn-copilot.md
• docs/components/early-access/alpha/bpmn-copilot/img/bpmn-copilot-chat.png

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.

[ev-codes]

Thanks @christinaausley ! I'll take a look at this later this week 😄

[HanselIdes]

@ev-codes I added some thoughts. Please review them for accuracy and integrate them in. I do not need to re-review this doc

[ev-codes]

Thanks @christinaausley ! I left a few points.

We should also revisit the screenshot in January closer to launch, as the UI and text may change slightly.

[christinaausley]

Thanks all for your feedback -- I will clean up this PR next week, with plans for a final review/any minor updates closer to January.

[christinaausley]

This has been tidied based on the comments. I will revisit this PR in January to confirm the UI references and screenshots.

[christinaausley]

@lmbateman @ev-codes Can you please have another look over these changes and confirm the UI? Would you like this to go out with alpha-3 next week?

[ev-codes]

@christinaausley thanks for checking in!

We won't be releasing this publicly for a few weeks. I'll do a final UI check closer to release.

Also: @YanaSegal is now the primary designer working on this project. I'll add her as a reviewer closer to release.

Thanks 😄

[christinaausley]

@YanaSegal can you confirm the capabilities and UI references outlined in this PR? Will this still be released this Thursday 1/23?

[ev-codes]

@christinaausley we will only do an internal release to Camundi during the Kick-off Week.

For internal releases, would you recommend releasing the documentation publicly already?

For a release to external customers, we're aiming for alpha4.

[christinaausley]

@christinaausley we will only do an internal release to Camundi during the Kick-off Week.

For internal releases, would you recommend releasing the documentation publicly already?

For a release to external customers, we're aiming for alpha4.

@ev-codes I would not release the documentation publicly until the product is public as well. We can always pull the existing documentation into Confluence if you have an existing page or issue there already, if you would like.

[christinaausley]

@YanaSegal can you confirm the capabilities and UI references outlined in this PR for release next week?

[ev-codes]

@christinaausley thanks! Docs look accurate overall.

Two small things:

• I pushed an updated screenshot
• In the UI, we use the capitalization BPMN/Camunda Copilot. Should we also use this in the technical docs? Whatever you think makes sense 😄

@YanaSegal is on FTO this week, but we can incorporate any changes she proposes when she's back Monday.

[christinaausley]

In the UI, we use the capitalization BPMN/Camunda Copilot. Should we also use this in the technical docs? Whatever you think makes sense 😄

@ev-codes @mesellings Do we want to standardize on "copilot" lowercased?

[mesellings]

In the UI, we use the capitalization BPMN/Camunda Copilot. Should we also use this in the technical docs? Whatever you think makes sense 😄

@ev-codes @mesellings Do we want to standardize on "copilot" lowercased?

Hmm, I would have said if it's the product name, it would be BPMN Copilot, like Camunda Copilot, unless we're just informally referring to it as a 'copilot' (i.e. concept rather than a specific product)? Feels like Connectors/connectors again 😄

• Is it marketed as the 'BPMN Copilot' do we know, or more just as one of many copilots (e.g. FEEL copilot)?
• If in doubt, perhaps the PM should have a say?
• Convention seems to be capitalized, e.g. Github Copilot, Microsoft Copilot etc

[ev-codes]

@mesellings in the product and the upcoming release blog, this feature is labelled as BPMN Copilot.

There are plans in the 1-3 month horizon to offer a FEEL Copilot. In the future, we might want to release additional Copilots. That said, I haven't seen them referred to in the lower case, even when discussed internally.

As you note, Copilot seems to be the most common capitalization form in the industry.

I now have a preference to use the capitalized form "Copilot".

@HanselIdes what do you think?

[HanselIdes]

I now have a preference to use the capitalized form "Copilot".

@HanselIdes what do you think?

"Copilot" LGTM - I care that things are at least internally consistent

[ev-codes]

@christinaausley awesome work, thanks for all your work and patience!

[christinaausley]

This is ready for final review and merge 👍

[ev-codes]

Thanks for catching the sidebar!

[github-actions]

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