Hacktoberfest contributions are welcome! Any GitHub user may contribute. You may review the issues section; you are welcome to fix any bugs in the existing challenges, add features, or you can submit your own challenge!
To submit a challenge:
- Fork this repository. Clone the forked repository and install dependencies.
- Go to 100 Days CSS Challenge homepage.
- Select a challenge that is not completed yet on this repo.
- Review this document (especially the sections on development) and start on a challenge. Complete the challenge. You are not required to write the
README.md
on your challenge, but if you do, please write it in English and add your GitHub id somewhere on the page, so credit will go where credit is due. - Commit your changes. Please try to use the conventional commit syntax when commiting. It's recommended to commit once per challenge, with a commit message of
feat: 012
. Please submit an individual PR for each challenge.
PRs will not be merged if:
- They are spam, irrelevent, or offensive.
- The
README.md
of other existing challenges are modified. README.md
is written in a non-English language.
Issues and PRs are welcome!
100 days of CSS - OR: 100 days of trying not to suck at CSS.
My goal: to write animations with no javascript. Pure CSS (or pure PostCSS, if you will). I'll make an exception for Pug, because although it's technically Javascript pre-processing HTML, you can't really expect me to write 400 divs by hand, lol.
And PostCSS is technically Javascript post-processing HTML, but the whole point of this is to learn PostCSS, really, so that doesn't count either.
npm install
npm run dev
Open localhost:1234/index.html
. Please don't forget the index.html
.
npm run new
Enter a new challenge from the prompt. Name should be a 3-digit number ranged from 0 to 100 (ie. 046).
npm run dev
Open localhost:1234/${day_number}/index.html
to see the page. Where day_number is a 3-digit
number ranged from 0 to 100 (ie. 046).
npm run build
This is an exercise in the following technologies:
And the following abilities:
- To not give up and not smash one's computer
- To investigate, explain and enforce industry standards as well as I can.
- To find and bookmark some very useful CSS sites
- To hopefully write some reusable CSS snippets