Contributions guide - Nosp1/Dnd GitHub Wiki
Thank you for considering contributing to StoryTeller. To better aid you in aiding us, we´ve set up this guide for you to follow so that you can get insight into how our development process works and we can more easily implement the features or ideas you have.
Custom Content
If you wish to contribute with custom content: E.g., new roles (classes), races or backgrounds you can send us an email to this address: [email protected] with this format:
Subject: StoryTeller; new Feature
Introduction
Containing a brief explanation of your custom content
Type of content: Is it a race, role or background?
Name of the content type (Race name:, role name: Background name:)
Features of the content
- Stats it increases: if any
- Languages it adds: if any
- Age limit: if any
- Skills it gives proficiency in: if any
- Tools it has: if any
- The equipment it gives: if any
Code contributions
Before you can contribute be sure to have all the necessary tools.
Fork and Clone
First fork the repository and type: git clone https://github.com/Nosp1/Dnd.git in the terminal window. Open the files in a suitable IDE of your choice and look around.
Familiarize yourself with the content
It´s a good idea to familiarize yourself with the files provided to ensure that you are not doing duplicate work. If you find a part of the software lacking, check whether an issue is already posted regarding this issue before posting your own.
Issues
If a particular issue interests you, consider assigning yourself to the issue, check out current issues here.
When posting an issue of your own provide an accurate description of the issue and describe the problem in detail.
Adding content
We greatly appreciate any contributions. If you want to add a feature to the software:
- fork the repository
- clone our repository with
git clone https://github.com/Nosp1/Dnd.git
- create an upstream remote to your fork by typing
git remote add
<name of remote> <https://github./yourstuffhere/Dnd.get>
- Implement new features or fix issues and push them upstream to your fork with a descriptive commit message.
- Issue a pull request with detailed commentary about the changes or new features.
- We will then review your additions and release the newly added content or changes with our next version.