Skip to content

Latest commit

 

History

History
57 lines (37 loc) · 4.75 KB

README.md

File metadata and controls

57 lines (37 loc) · 4.75 KB

TEMPLATE TODO 🗒️🗒️🗒️:

(remove me)

This repository seeks to serve as a template for organizations/groups that would collectively like to participate in the 100 days of code project. To use this project, replace all words in <tags> with the respective value. For instance, <year> -> 2022. You should just be able to search for occurrences of <. Additionally, address wherever there is a TODO. For an example of this template in use, see BBT-2021 and for the auto-generated tracking site, see the rendering of this template.

You may also want to edit mkdocs.yml for static site generation. Contributions are counted in a given day, and will not be counted if the phrases DNT, Update README or Merge pull request are present in a commit message.

Template Button


100 Days Of Code <organization>

<year>

100 days of Code Join the slack channel Contributors Days Docs

TODO: Add more relevant badges. Example badges below. Note that the contributor and days code are automatically generated and can be changed for your repo.

The challenge is to code at least one hour every day for the next 100 days. This is just a repository for members of <organization> to share some of their projects, efforts and notes. Let's see if we can get 100 days of code together!

FAQ:

What Is The #100daysOfCode Challenge?

100 Days Of Code is a social media project, primarily on Twitter, that anyone can participate in via the #100daysOfCode hashtag. Developer Alex Kallaway started it in 2016 based on the idea that consistency is the path to mastery. Plus, the hashtag fosters a sense of community—you can use it to see where others are at in their journey and to stay motivated to document your own.

How Can I Participate?

Do #100daysOfCode with <organization>! Work your way through projects, or document your Tech journey—either way, posting what you’re learning each day is a great way to see your coding progress unfold and find support. We’ll support you with encouraging messages along the way, and you’ll have the entire <organization> online community to supplement your interactions. At the end of your 100 days coding with us, you’ll get a host of experience and several friends that have taken part in this challenge.

Two Main Rules

  1. Code minimum an hour every day for the next 100 days.
  2. Slack your progress every day with the <communication> channel.

Instructions

  • Create a github account
  • Fork our repo locally: https://github.com/``
  • Track the our repo as a remote (Optional)
  • Create a branch and a folder with your name (ex. 100daysOfCode_YourName)
  • Code daily and post to github and <channel> on your progress

Let's have fun and support everyone in their tech journey

Current Status

TODO: Change the link so that the tracker works for your organization.

Current Status

Legal

The template and supporting code for this repo are licensed under the Apache License 2.0 (TLDR legal here). Folders under 100daysOfCode_* are licensed under their respective authors. Derivates of this project must link back to the original Baltimore Black Techie 100 Days of Code template (just keep this subsection folx), and are licensed under the good faith that sub-licensers will up hold some meaningful interpretation of our Code Of Conduct.