How to contribute blog posts for LitmusChaos?
Tags: litmuschaos, kubernetes, cloudnative, devops
Published: 2021-08-25 10:26:03

As the LitmusChaos community continues to grow and recently celebrated completing the milestone of 50 blog posts on its [DEV.to blog page](https://dev.to/t/litmuschaos/latest), I would like to congratulate the community for helping Chaos Engineering reach more and more people out there with their smallest of contributions in the form of blog posts, tweets, videos, and other community content.
[LitmusChaos 2.0](https://github.com/litmuschaos/litmus/releases/tag/2.0.0) is out now with a lot more new features, experiments, enhancements and bug fixes to make your Chaos Engineering journey easier and better. Induce Chaos Engineering tests in a simpler, easier, & faster way with LitmusChaos 2.0!
Don't forget to write down your experience or about a feature through a blog to let the community know!

While most of the present blogs published on LitmusChaos have been by the maintainers and the contributors, it is the need of the hour for the community to come forward and contribute learnings, ideas, features, and principles of LitmusChaos for the betterment of the project as well as the overall Chaos Community.
If you are interested in contributing a blog for the LitmusChaos project, do read the blog find out how you can contribute a blog post for LitmusChaos…

#Topics to cover

There are various topics and ideas one can consider to write a blog post on. As the center of interest is on Litmus and Chaos Engineering as a value, hence, the ideations should focus on the above before anything else. There are plenty of topics that can be covered as blogs regarding the LitmusChaos project. Let us take a look at some of the potential topics that can be covered as blogs and the questions that can be answered:

#### Features of LitmusChaos
* How has the Litmus ChaosHub eased your experience?
* What role does GitOps play in the Chaos Engineering ecosystem?
* How has the LitmusChaos SDK helped you Bring your own Chaos to your infrastructure?
* Chaos Workflows have helped ease inducing Chaos Engineering use cases.
* What are the benefits of LitmusChaos being multi-tenant?

#### Your Experience using LitmusChaos
* How You configured LitmusChaos in your environment?
* How does LitmusChaos fit in your architecture?
* How does LitmusChaos fit in your use case?
* What can be improved with LitmusChaos?

####The LitmusChaos Community
* Translate a meetup/webinar on Litmus into a blog
* Why is community support vital in making an open source/ cloud-native project successful?
* What makes the LitmusChaos community amazing and what could be done better?
* Things to look forward to with LitmusChaos 2.0
* What should be the roadmap ahead for Chaos Engineering and LitmusChaos?
* Cover a LitmusChaos experiment or a Chaos Engineering scenario built using Litmus
* Cover a Gameday you ran using LitmusChaos
* Jot down your encounter of running Chaos in production with LitmusChaos. The pros and cons of it.
* Comparison blog on LitmusChaos with other toolsets. Pros & Cons.
 
#### Running LitmusChaos on different infrastructures
* Running LitmusChaos on Kubernetes infrastructures
* Running LitmusChaos on AWS, Azure, GCP-based infrastructures
* Running LitmusChaos on VMs
* Running Litmus on Baremetals

#### Integration with different projects
* How did you run chaos and validate SLOs with Litmus & Keptn?
* Your experience of running LitmusChaos GitHub Actions or GitLab templates.
* Ideas on integrating Litmus with other CNCF or Cloud-Native projects
* A deep-dive, tutorial, or guide on using LitmusChaos.

Other than the topics stated above, there are many permutations and combinations which can form a blog. You can author mini-blogs covering a particular sub-topic or feature or can curate a series of blogs followed by a meta-blog which will be of interest to the Litmus community as well as to folks practicing or looking forward to Chaos Engineering.
Check out the LitmusChaos blog page to grab an idea of the blogs already published and find the topic you can cover.

In case you are not sure about the topic, feel free to reach out on Slack (We are on the #litmus channel of the Kubernetes slack) or you can tag [@LitmusChaos on Twitter](https://twitter.com/LitmusChaos) and ask. Worst case scenario, you can [DM me on LinkedIn](https://www.linkedin.com/in/prithvi1307/)! :)

#How to contribute?
You can contribute blogs on both DEV.to as well as Medium as both the blog platforms feature Litmus blogs.
Majorly, Litmus-related blogs are hosted on DEV.to. 
You can find the previously published articles here: https://dev.to/t/litmuschaos/latest

![LitmusChaos on DEV](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/v6ryfv94pnxb74f2cs8u.png)

As you can see in the image above, the blogs have been published using the tag: #litmuschaos. And most of them also lie under the LitmusChaos publication. Let’s find out how you can publish on DEV first.

Start by creating a new post by clicking the “Create Post” button on the top-right corner of the page. You will be redirected to a new blog draft where you can add a title, up to 4 tags, and then the blog content.
In the tags section add one of the tags as “litmuschaos”. This ensures that your blog is published under the Litmus blogs.

![LitmusChaos Tag](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/19nho8w7dzmkdxvc96n7.png)

Once published, the blog can be added under the LitmusChaos DEV publication
https://dev.to/litmus-chaos

![Chaos Engineering tool](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/k27h96t17hu3ilalgo8u.png)

Further you can also contribute blogs on the Medium platform as many of you prefer writing blogs on Medium!
On Medium, one can contribute blogs under the LitmusChaos Medium Publication.
https://medium.com/litmus-chaos

![LitmusChaos on Medium](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/cdtssitgogsyq04zr3nh.png)

In case you are are contributing blogs on any other platforms other than DEV.to or Medium, feel free to share the same with us on the Slack channel or tag us on Twitter with your blog!
 
Once you are finished with the draft, you can share the draft with maintainers or the community leaders of the project to confirm facts and then can go ahead publishing the blog post. As the next steps, we will promote it on our Slack channel and other social media platforms and communities.

#Conclusion

In an open source community, contributing blogs is an important aspect and as a matter of fact is absolutely counted as a major contribution. As a community lead of the LitmusChaos CNCF project, I invite you to write blogs for the project to put forward your understandings and learning and further help it grow. Chaos Engineering is growing everyday and such blogs help the Chaos Engineering technology further reach the community!

Join the __#litmus__ slack channel on the [Kubernetes Slack Space](https://slack.k8s.io/) to be a part of the community!

Don't forget to check out the [LitmusChaos GitHub repo](https://github.com/litmuschaos/litmus) and drop a star and add it to your watch list to stay connected on GitHub! Happy Contributing! :)
Below are some links to important resources to get started with Litmus:
* [LitmusChaos Website](https://litmuschaos.io/)
* [LitmusChaos Docs](https://docs.litmuschaos.io/)
* [LitmusChaos on YouTube](https://www.youtube.com/channel/UCa57PMqmz_j0wnteRa9nCaw)