wolkenkit
Documentation
News
DocumentationGetting startedContributing to wolkenkitDeveloping ideas for contributions

Developing ideas for contributions

If you would like to contribute to wolkenkit, you may already have a specific idea – or none at all. Just like there are no stupid questions there are also no worthless contributions. We strongly believe that every contribution is important, from code to documentation, from asking questions to providing answers.

In the following we describe different aspects how you can contribute to wolkenkit. Before you start working on an issue, please read submitting a contribution.

Unsure what to contribute?

Maybe you would like to contribute something to wolkenkit, but are unsure about your idea, or maybe you don't know where to start. Actually, we are always there to help, so feel free to contact us.

Contributing code

The most obvious way to add value to wolkenkit is by contributing code. This includes fixing bugs, extending existing features, and even implementing new features. In the thenativeweb/wolkenkit repository you can find a list of all currently open issues. There you can also find a list of good first issues to start with. Additionally, to get a high-level overview of what is planned for wolkenkit, have a look at the roadmap.

Typical questions to come up with ideas are:

  • What feature does not work as expected?
  • What feature could be extended in its functionality?
  • What feature are you missing completely?

Reporting issues and raising ideas

If you found a bug or have an idea for a new feature, report an issue for it. To prevent the identical issue being reported multiple times, you should verify whether there is already an issue for your concern in the list of open issues.

Typical questions to come up with ideas are:

  • What feature does not work as expected?
  • What feature could be extended in its functionality?
  • What feature are you missing completely?

Improving the documentation

A helpful contribution can be to correct a typo or to improve and enhance an explanation that is too vague. For this purpose, each page of the documentation contains a link at the bottom, which you can use to directly edit the page on GitHub.

Typical questions to come up with ideas are:

  • What part of the documentation is not described with sufficient detail?
  • What part of the documentation could use an image to make things more clear?
  • What part of the documentation is there, but hard to find?

Developing a sample application

Sample applications help others interested in wolkenkit to get a better understanding of how things work. Whether you want to develop a new sample application or enhance an existing one, we would love to know what you are building with wolkenkit.

Typical questions to come up with ideas are:

  • What application have you ever wanted to build?
  • What application would you like to rebuild for learning purposes?
  • What application could be needed by your family or friends?

If you have something to share, we would love to hear from you, so please feel free to contact us.

Spreading the word

Are you writing a blog, or articles for an IT magazine? Do you use Twitter or other social media regularly? Are you giving talks at meetups or conferences? If any of this applies to you, you can contribute to wolkenkit by spreading the word.

Typical questions to come up with ideas are:

  • What story could be interesting to tell about wolkenkit?
  • What have been your experiences with using wolkenkit?
  • What have you learned from using wolkenkit?

If you would like to write, but don't have your own blog, we can also talk about a guest post for the blog by the native web. Additionally, we would be happy to link to your content, such as videos of your talks. Either way, feel free to contact us.