Welcome to the Camunda Champion Platform

Thank you for being one of our most loyal, helpful and collaborative community members. We are so grateful for your contributions to the community, and we’re proud to recognize you as a champion!

Join our Slack

PAGE NAVIGATION

Champion status = activated

You’re one of our most valuable contributers, and we think people should know! We’ll do our best to make sure our other community members know that you hold this title – but of course, you’re also entitled to brag about it yourself.

As a Champion, you can expect the following:

  • Camunda Champion welcome box with special swag
  • Access to Camunda Experts and fellow Champions
  • You get featured on our Champion webpage & receive exclusive badges
  • First-hand information about updates from the Camunda Universe
  • Invitation to exclusive Champion Summit & free ticket for CamundaCon
  • Camunda books (reach out to [email protected])
  • Access to Camunda Academy
  • Access to Camunda 8 Community Organization

Connect with fellow Champions

Join our Slack workspace

With this program, we want to support your contributions to the community, set you up for success, and create a global network of Camunda Champions. It’s so much more fun to work together on projects, and you can help each other along the way.

Join the Slack workspace to connect with fellow champions. We’ll also post important updates and announcements, so make sure to check it regularly! You’ll have access to Camunda experts and employees who can answer your questions.

We’ll also organize regular meetings for everyone, so keep your eyes peeled for invites. We look forward to sharing this awesome journey with you!

Let others know that you’re a Champion

We encourage you to share what you’re doing as a Camunda Champion on your social profiles. The Camunda Social Media Team will help amplify the work you’re doing whenever possible. To make this easier, be sure to mention/@tag Camunda’s social profiles across networks.
  • Feel free to add “Camunda Champion” to your social channels (for example, in your Twitter or LinkedIn bio, or in your volunteer experience on LinkedIn)
  • Explore our library of social media graphics you can use
  • Please reach out to [email protected] if there is anything you need
Whether you are hosting a Camunda Meetup, sharing your Camunda/process automation expertise at an event, adding a new extension, or publishing a new blog post, our team can help amplify your reach! If you contributed to the community in any way, please submit it to this form so we know about it.

Share on Social Media

Just like you would on our Forum, in Slack or at one of our virtual or in-person events, you’re expected to follow Camunda’s Code of Conduct and Community Values when sharing and commenting on any social network – particularly when representing Camunda.

A few things to keep in mind:

  • Provide ample notice, including relevant links, any photos, dates and times. This will give our team the ability to optimize your content by either creating custom images or best timing the content for maximum reach. 
  • Include images or videos. This can range from a current photo of you if you have an upcoming speaking event or screenshots/photos from a previous meetup.
  • We only post in English on the Camunda corporate profiles.
Things We Love to ShareWhat We Do Not Share
  • Meetups
  • Speaking opportunities if Camunda/process automation is highlighted in the presentation
  • Blog posts if Camunda/process automation is the focus
  • Content you are contributing to the Community Hub
  • Thought leadership
  • Helpful, educational content
  • Strictly promotional content
  • Anything that is completely unrelated to Camunda or process automation

Any questions, reach out to [email protected].

 

Camunda 8 Community Organization

You do such valuable work as part of the Camunda ecosystem, and that’s why we want you to be able to easily try out Camunda 8, explore new features, and create demo applications for your events. To do all of this, we offer you access to a joint Camunda 8 organization.

We offer you access to a Camunda 8 organization with three clusters. Other members of the organization are fellow Camunda Champions and Camunda Chapter Leaders. Being part of one organization will make it easy for you to collaborate.

What can I do as part of the Camunda 8 organization?

We want you to be able to try out the product, explore new features, and create demo applications
for your events with the product. 

You might want to do the following things:

  • Present Camunda 8 demos at events
    • Internally or externally
  • Create complex Camunda 8 projects.
    Requirements:
    • The project must clearly benefit the community
    • The project should not be for production
  • Run teaching events, e.g.:
    • Lectures at universities
    • Internal or external workshops
  • Build a C8 project intended for the community, e.g.:
    • New connectors or templates
    • New exporters

How to get access?

What clusters do I have access to?

You have access to the following three clusters as part of the organization:

Playground Cluster

Demo Cluster

Cutting Edge Cluster

Playground Cluster:

  • Goal: The “playground cluster” exists for you to play around and build demo applications that you don’t want to keep permanently.
  • The data from this cluster will be cleared on a regular basis, so it doesn’t get too crowded.
  • Downtime will not necessarily be communicated to users.

Demo Cluster:

  • Goal: The “demo cluster” exists for you to create final demos that should be kept permanently. 
  • The cluster will be always the latest stable release and will be kept up to date by Camunda.
  • Any downtime for this cluster will be communicated min. 24 hours prior in the #c8-community-organization channel.

Cutting edge cluster

  • Goal: The “cutting edge cluster” exists for you  to test and try out newest features.
  • The cluster will be deleted after every alpha release to make sure it is always up-to-date. Be aware that you will lose your data once the cluster will be deleted.
  • There should not be an expectation that this cluster will always be available – by virtue of using an alpha version it’s likely less stable than other clusters.

Guidelines

  • Each Champion is eligible to to get added to the Community C8 Organization. The access cannot be transferred to another person since this is a exclusive reward associated with the Champion Program.

  • The access to the organization will be granted until the next Champion renewal period. If a Champion is eligible to extend the right to access the organization, is dependent on if they remain in the Champion program and if they actively utilize the access (e.g. for demos, presentations, trying out new features etc.).

Submit your contributions

One thing that makes our community so strong is our diversity of talent. We love seeing all the ways in which our Champions contribute to the Camunda Community. From organizing meetups, writing blog posts, creating and sharing code, and a million other things, we wouldn’t be who we are without you.

Keep us informed about your community contributions by filling out this form (view this list to see what has been already added by you and fellow Champions). If you submit your contributions on a regular basis, it will make it easier for us to renew your Champion status after one year. Plus, we would love to share your projects with the wider community. We can’t wait to see what you’ll be working on!

Write a blog post

Are you interested in writing a blog post about your experience with Camunda? Great! We’ve created a template to help you get started.

To submit your blog post or receive further support on your content, please contact [email protected].

<Title of Post>

The title should be a short (5-7 word) summary of your post. What question did you answer? What problem did you solve?

Tips:

  • Think about what phrase someone might use to find your blog post if they were searching for it on Google
  • If necessary, you can include a subtitle to add more context 

Introduction

Start your post with a brief hook to help people understand the goal of your blog post and get them excited to continue reading. Be conversational and personal! 

Tell a short story (max 2-3 sentences) to draw the reader in, or start your post with a straightforward opening problem statement (e.g. the problem you ran into, the question you’re addressing from the forum, the interesting concept you’re going to talk about, etc.). 

End your introduction with a sentence that explains the problem you want to solve, sets the stage for the story you’re telling, and touches on how you came to your conclusion.

Body

The body of your post provides the substance that supports your main idea, or explains the solution you found to the problem you’ve established in your opening paragraph. 

Write about 3-5 paragraphs to explain the process you followed to arrive at your solution/conclusion.

Each paragraph can share information that expresses a key value of your solution or explain a step that was taken to find the solution and its findings.

Tips:

  • Include screenshots, code snippets, or gifs to illustrate the steps that you’re taking along the way. If you’re writing a blog post to go along with a video tutorial, you could embed segments of the video for each step of the blog post.
  • Don’t forget to add alt text for any images you embed into a post.
  • For code snippets, we will use a code block setting in WordPress to properly format the code. Simply let us know in the Google doc that this section should be formatted appropriately.
  • Be sure to address everyone referenced in your post by their correct pronouns. If you’re not sure of their pronouns, ask!
  • Limit your use of jargon. If you do use jargon or industry specific terminology, make sure to define it clearly.
  • Write short, concise sentences.
  • Don’t make your post region specific. Keep it global!
  • Use inclusive language, e.g. Use “everyone” or people,’ instead of ‘Guys’; “they” instead of “he.”

Concept Building 

This is where you’ll build on the topic you introduced in your first paragraph. It’s an opportunity to dig deeper into the concept you outlined. This can include going into more detail about:

  • Your use case, including how Camunda and/or process automation has helped solve a particular problem or use case
  • An interesting customer success story made possible with process automation
  • How you solved a problem or challenge you were facing
  • Why you chose a particular technology, built a specific project, or worked on a piece of software

(Optional) Further Exploration Paragraph

Here’s where you can dig into complex topics, back up a customer use case story with interesting data, walk through a tutorial, or really show off some in-depth code or a technical process. This paragraph is also an opportunity to explore how you implemented any solutions you outlined above, and what steps you plan to take in the future.

Conclusion

Let the reader know they’ve made it to the end. Finish your post with a brief restatement of your main point. Tell the reader you hope they found your post helpful and encourage them to get started with your idea. 

Key Takeaways and CTAs

Here’s where you can highlight the top 3-4 key takeaways a reader can bring back to their organization after having read your article. These are high-level, one-sentence summaries of each of your paragraphs. For example:

  • Here’s how you implement process automation
  • Why our organization chose Camunda
  • Relying on data is important
  • In the end, automation = success

Close out your post with an explicit call to action that says what you’d like the reader to do next: sign up for an account, use a particular feature, build something, etc. If nothing else, ask the reader to leave you a comment about the post or join us on the Camunda community forums.

Technical blog post formatting tips:

  • Break up large chunks of text with screen captures, images, code snippets, etc.
  • If you think a post is getting too long, consider making it a series instead!
  • Make sure your code snippets are readable in your screen captures
    • Use alt text for images containing code, and give an example of what that code does in the description.

Blog Post Template Formatted in Markdown

If you’d prefer to write your blog post in Markdown, you can use this template as a skeleton to help you get started:

author: “Your Name”

categories:

  – “Execution”

tags:

  – “X”

  – “Y”

title: “Camunda Introduces BPEL Support”

date: 2019-06-17T14:24:30Z

# Title of Post

Start your post with a brief hook. Be conversational and personal… maybe use a brief story to draw the reader in.

End your introduction with a simple statement that explains the problem you want to solve and a brief one or two sentence summary of how you’re going to solve the problem.

## Introductory Paragraph

The body of your post provides the substance that supports your main idea, or explains the solution you found to the problem you’ve established above. 

Try to include screenshots, code snippets, and gifs to illustrate the steps that you’re taking along the way.

For code snippets, you can write in Markdown and/or use [code blocks](https://www.w3schools.com/tags/tag_code.asp).

## Concept Building Paragraph

This is where you’ll build on the topic you introduced in your lede and introduction. It’s an opportunity to dig deeper into the concept you outlined. This can include going into more detail about:

* Your use case, including how Camunda and/or process automation has helped your organization

* An interesting customer success story made possible with process automation

* How you solved a problem or challenge you were facing

* Why you chose a particular technology, built a specific project, or worked on a piece of software

* How you applied what you learned in your introduction

## (Optional) Further Exploration Paragraph

Here’s where you can dig into complex topics, back up a customer use case story with interesting data, or really show off some in-depth code or a technical process. This paragraph is also an opportunity to explore how you implemented any solutions you outlined above, and what steps you plan to take in the future.

## Conclusion

Let the reader know they’ve made it to the end. Finish your post with a brief restatement of your main point. Tell the reader you hope they found your post helpful and encourage them to get started with your idea. 

## Key Takeaways and CTAs

Here’s where you can highlight the top 3-4 key takeaways a reader can bring back to their organization after having read your article. These are high-level, one-sentence summaries of each of your paragraphs. For example:

* Here’s how you implement process automation

* Why our organization chose Camunda

* Relying on data is important

* In the end, automation = success

Close out your post with an explicit call to action that says what you’d like the reader to do next: sign up for an account, use a particular feature, build something, etc. If nothing else, ask the reader to leave you a comment about the post or join us on the Camunda community forums.

Get started with the Camunda Community Hub

The Camunda Community Hub is the home for Camunda open source community-contributed extensions. For open source project developers, it’s a community of maintainers and Camunda employees that provides peer support, aims to streamline release automation, and aids in project discoverability. The hub also provides best practices and resources for maintainers hoping to build a new Camunda community extension. Any interested Camunda community maintainer can migrate an existing extension they’ve developed to the Camunda Community Hub, or create a new community extension. We look forward to seeing the ways that you iterate on and extend Camunda.

To learn more about the Camunda Community Hub, visit our Github page or read our blog post, Introducing the Camunda Community Hub.

If you have any questions about getting started with the Camunda Community Hub, you can reach out to us at [email protected].

Engage on our Camunda Forums

There are two official Camunda forums:

Our community forums are a place for active, thriving discussion with the broader community as a whole. Sometimes, Camunda team members may even reply to a topic or start a new thread. They’re a great place to go if you’re stuck with something, need to troubleshoot an issue, or just want to toss around ideas and best practices surrounding process automation.

Keep in mind that our forums adhere to a standardized set of community guidelines and expectations in addition to our Code of Conduct that Champions are expected to adhere to at all times when interacting with the community.

Participate in the Camunda meet-up program

Mingle + learn with fellow Camunda users

A meet-up brings together people who share similar interests, allowing them to connect, ask questions, and exchange personal user experiences. You can be involved in the program by becoming a chapter leader or attending as a speaker.

If you would like to present a topic in a meet-up, check the existing Camunda Chapters and reach out to [email protected]

You can also become a chapter leader. This is a great way to connect with the wider community, gain public speaking experience, and help the local community grow its knowledge base. 

If you would like to become a Chapter Leader, take a look at the leader’s responsibilities and apply!

Give more talks through the External Speaker’s Bureau

From 2021-2023 Champions have given 64 talks on behalf of Camunda. We’re so grateful you’re willing to help us spread the word about process orchestration and Camunda’s best practices to your communities. If you would be willing to give even more talks, but perhaps don’t have the budget or confidence needed to do that, we would love to support you!

This program provides you resources to level up your speaking abilities, but also be reimbursed for some of your travel expenses (up to or the equivalent of €400).

Fill out this form and we’ll be in touch within the week!

Discover premium features for free