This Repo contains a collection of resources collected for and during the Hack Evenings event series. It is supposed to help anyone looking to learn and improve their coding skills to find tutorial, resources and inspiration.
We love contributions! We would like to extend this collection to contain resources of all kind related to all programming languages, frameworks, general programming knowledge and IT careers. If you have anything you liked and found useful, please share it with us:
You can check out the existing resources and see if you know anything that fits any of the categories. Make sure to also have a look at the Content Guidelines to learn more about what types of content we like and what information should be provided. If you are motivated to help out, but are not sure what to do, you can also check out the open Issues. These are a collection of tasks that we (or others) think should be done to improve this repository. Maybe there is something open that would be perfect for you? If you start working on an issue, it is recommended to comment on the issue to let others know about your work. This can help avoid duplicate work :)
To add your contribution to this repository you will need a Github account. You can sign up for free at https://github.com/join.
If you have an account and your are signed in, you can create your own fork of this repo. (Learn more about forks here). Click the button labelled "Fork" in the top right corner. You might see a popup that asks you where to create the fork if you are part of any organization - select your personal account.
This means you will create your own copy of the repository where you are allowed to freely add and edit anything. This repository is owned by Women Who Code and only members of the organization can make changes.
If all contributions were only spread across different forks, it would not be very useful. So how do your changes get into this repository?
You basically "propose" your changes to us, the owners of the original repository by creating a pull request (often abbreviated as "PR"). In your forked repository, select the "Pull Requests" tab, then click the button "New Pull Request" (green button in the top right). You will see a new view where you can select the repositories and branches. By default it should show you WomenWhoCode/Berlin as the base repositiory and your fork (/Berlin) as the "head repository". The branch for the base should be master and for your repo it is the branch where you made the changes (if you did not create a branch, it will be master).
Continue by giving your pull request a title that helps us to know what changes it contains. Ideally you also add at least a little bit of detail to the description of the PR. When you are done, submit the pull request by clicking the green "Create Pull Request" button.
We will get a notification about the new pull requests and can have a look at the changes you proposed. We can then merge the changes from your PR to the original repository. This means they will become part of the original repositiory and you will officially be a contributor. Congratulations, you have shared your knowledge & tips with our community and potentially the whole world!
To make sure everything goes smoothly, here are a few more tips:
- If you create the Pull requests, try to make sure that your fork is up to date with the master branch of this repo.
- If you intend to work on a task where we have an open issue, make a comment on the issue to let everyone know what you are doing.
- If you need personal support or have any questions, join our slack channel WWCode-hacknights (What is Slack?)
We are happy about any contributions: Tutorials, Guides, (free) books, video courses, online exercises, ... Look at the categories and see if it fits any of the existing categories and/or sub-categories. If you think the appropriate category is missing, add it.
If you are not sure where your resource belongs, you can also create an issue to ask about it. Or ask in the our slack channel.
Ideally you will not only add a link, but also a little bit of information:
- What is it exactly? Try to describe it in a sentence or two
- Why do you like it / or think it is useful?
- a link to the resource (Learn about how to create a clickable link in this markdown guide)