├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── bug.md │ ├── ideas.md │ └── questions.md ├── pull_request_template.md └── workflows │ ├── community.yml │ └── stale.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE └── README.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | custom: ["https://paystack.com/pay/chryzhub"] 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug 3 | about: Create a bug-report to help us address errors in the repo. 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Description** 11 | 12 | 13 | 14 | **Stack** 15 | 16 | Project stack or language (eg. Frontend): 17 | 18 | **Working Environment** 19 | 20 | Operating System (eg Linux): 21 | 22 | Browser (eg. Chrome): 23 | 24 | Device (eg. Laptop or Phone): 25 | 26 | **Screenshots** 27 | 28 | Please add a screenshot if applicable 29 | 30 | [Optional] **Additional Context** 31 | 32 | Add any other context about the problem here. 33 | 34 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ideas.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Ideas 3 | about: Bringing up ideas for the smooth running of the community 4 | title: 'I have an idea' 5 | labels: 'ideas' 6 | assignees: 'chryzcodez' 7 | 8 | --- 9 | 10 | 11 | **Description** 12 | 13 | A brief description of the ideas: 14 | 15 | **Goals** 16 | 17 | The aim and objectives of the ideas: 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/questions.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Open Source Question 3 | about: I am stuck please can someone help 4 | title: '' 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Description** 11 | 12 | A brief description of the question , also include what you tried and what didn't work: 13 | 14 | **Screenshots** 15 | 16 | Please add a screenshot if applicable 17 | 18 | [Optional] **Additional Context** 19 | 20 | Add any other context about the problem here. 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | #ISSUE-NO 2 | 3 | #### What does this PR do? 4 | 5 | #### Description of Task to be completed? 6 | 7 | #### How can this be manually tested? 8 | 9 | #### Any background context you want to provide? 10 | 11 | #### What is the relevant issue link? 12 | 13 | #### Screenshots (if appropriate) 14 | 15 | #### Questions: 16 | 17 | 18 | -------------------------------------------------------------------------------- /.github/workflows/community.yml: -------------------------------------------------------------------------------- 1 | on: 2 | issues: 3 | types: [opened] 4 | pull_request_target: 5 | types: [opened] 6 | 7 | jobs: 8 | welcome: 9 | runs-on: ubuntu-latest 10 | steps: 11 | - uses: actions/first-interaction@v1 12 | with: 13 | repo-token: ${{ secrets.GITHUB_TOKEN }} 14 | issue-message: '

It''s great having you contribute to this community

Thank you for raising an Issue!
Welcome to Chryz-Hub

If you are willing to join the community, connect via the Chryz-Hub Connect Website
You can make a pratice pull request and also add your name been a member of the community ~~ here.

' 15 | pr-message: '

It''s great having you contribute to this community

Thank you for creating a Pull Request!
Welcome to Chryz-Hub

If you are willing to join the community, connect via Chryz-Hub Connect Website
You can make a pratice pull request and also add your name been a member of the community ~~ here.

' 16 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | name: 'Close stale issues and PRs' 2 | on: 3 | schedule: 4 | - cron: '30 1 * * *' 5 | 6 | jobs: 7 | stale: 8 | runs-on: ubuntu-latest 9 | steps: 10 | - uses: actions/stale@v3 11 | with: 12 | repo-token: ${{ secrets.GITHUB_TOKEN }} 13 | stale-issue-label: 'stale' 14 | stale-pr-label: 'stale' 15 | stale-issue-message: 'This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.' 16 | stale-pr-message: 'This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 20 days.' 17 | close-issue-message: 'This issue was closed because it has been stalled for 15 days with no activity.' 18 | close-pr-message: 'This PR was closed because it has been stalled for 15 days with no activity.' 19 | days-before-issue-stale: 20 20 | days-before-pr-stale: 20 21 | days-before-issue-close: 15 22 | days-before-pr-close: 15 23 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | chryzhub@gmail.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via issue, 4 | email, or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a [CODE of CONDUCT](https://github.com/chryz-hub/web-dev-resources/blob/master/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project. 7 | 8 | 9 | ## Pull Request Process 10 | 11 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 12 | build. 13 | 2. Update the README.md with details of changes to the interface, this includes new environment 14 | variables, exposed ports, useful file locations and container parameters. 15 | 3. Increase the version numbers in any examples files and the README.md to the new version that this 16 | Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). 17 | 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 18 | do not have permission to do that, you may request the second reviewer to merge it for you. 19 | 20 | ## Commit Message Guidelines 😎 21 | 22 | In order to make git commit messages **easier to read** and faster to reason about, we follow some guidelines on most commits to keep the **format predictable**. Check [Conventional Commits specification](https://conventionalcommits.org) for more information about our guidelines. 23 | 24 | **Examples**: 25 | 26 | 27 | ``` 28 | docs(changelog): update changelog to beta.5 29 | docs: add API documentation to the bot 30 | test(server): add cache tests to the movie resource 31 | fix(web): add validation to phone input field 32 | fix(web): remove avatar image from being required in form 33 | fix(release): need to depend on latest rxjs and zone.js 34 | ``` 35 | 36 | ### Type 37 | 38 | Must be one of the following: 39 | 40 | - **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm). 41 | - **ci**: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs) 42 | - **docs**: Documentation only changes 43 | - **feat**: A new feature 44 | - **fix**: A bug fix 45 | - **perf**: A code change that improves performance 46 | - **refactor**: A code change that neither fixes a bug nor adds a feature 47 | - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) 48 | - **test**: Adding missing tests or correcting existing tests 49 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Chryz-Hub 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Web-Dev Resources 2 | 3 | 4 | 5 | 6 | 7 | 8 | This repository is geared towards accumulating world class resources for web developers! 9 | 10 | ### This resources include these various languages 11 | 12 | - HTML 13 | - Javascript 14 | - Python 15 | - CSS 16 | - React 17 | 18 | 19 | # Contributing 20 | 21 | If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request. 22 | Feel free to create an [issue](https://github.com/chryz-hub/web-dev-resources/issues) or make a Pull Request. Please see our [Contributing file](https://github.com/chryz-hub/web-dev-resources/blob/master/CONTRIBUTING.md) 23 | first and our [Code of Conduct](https://github.com/chryz-hub/web-dev-resources/blob/master/CODE_OF_CONDUCT.md), before making new commits or opening a pull request, we appreciate it! 24 | In order for us not to ignore your effort, please check well not to make a duplicate of a Pull Request (contribution)/ issue! 25 | 26 | ## Resources 27 | 28 |
HTML
29 | You can create segments for html blogs, documentations, repositories, books and the rest by adding contents. 30 |
31 |
32 |
.html websites
33 | 48 |
49 | 50 |
.html courses/videos
51 | 62 |
63 |
64 | 65 |
Javascript
66 | You can create segments for javascript blogs, documentations, repositories, books and the rest by adding contents. 67 |
68 |
69 |
.js websites
70 | 87 |
88 | 89 |
.js courses/videos
90 | 108 |
109 | 110 |
.js repositories
111 | 157 |
158 | 159 |
.js blogs
160 | 163 |
164 | 165 |
.js books
166 | 172 |
173 |
174 | 175 |
Python
176 | You can create segments for python blogs, documentations, repositories, books and the rest by adding contents. 177 |
178 |
179 |
.py websites
180 | 219 |
220 | 221 |
.py courses/videos
222 | 255 |
256 | 257 |
.py repositories
258 | 290 |
291 | 292 |
.py podcasts
293 | 302 |
303 | 304 |
.py blogs
305 | 309 |
310 | 311 |
.py books
312 | 331 |
332 | 333 |
.py newsletters
334 | 339 |
340 |
341 | 342 | 343 |
CSS
344 | You can create segments for css blogs, documentations, repositories, books and the rest by adding contents. 345 |
346 |
347 |
.css websites
348 | 364 |
365 | 366 |
.css courses/videos
367 | 374 |
375 | 376 |
.css games
377 | 387 |
388 | 389 |
.css repositories
390 | 398 |
399 |
400 | 401 |
React JS
402 | You can create segments for react blogs, documentations, repositories, books and the rest by adding contents. 403 |
404 |
405 |
.js(react) websites
406 | 414 |
415 | 416 |
.js(react) repositories
417 | 431 |
432 | 433 |
.js(react) courses/videos
434 | 453 |
454 |
455 | 456 |
Frontend
457 | You can create segments for frontend development blogs, documentations, repositories, books and the rest by adding contents. 458 |
459 |
460 |
frontend websites
461 | 470 |
471 | 472 |
frontend courses/videos
473 | 489 |
490 | 491 |
frontend repositories
492 | 504 |
505 | 506 |
frontend bootcamps
507 | 510 |
511 |
512 | 513 |
Coding Challenge Websites
514 | 562 |
563 | 564 | 565 |
Other Learning/Programming Resources
566 | 567 |
Repositories
568 | 638 |
639 | 640 |
Courses/Videos
641 | 647 |
648 | 649 |
Blogs
650 | 659 |
660 |
661 | --------------------------------------------------------------------------------