4 |
5 |
6 |
7 | Coding Books
8 |
9 |
10 |
14 |
15 |
19 |
20 |
24 |
66 | About
67 |
68 |
69 |
70 |
128 |
129 |
130 |
131 |
132 |
--------------------------------------------------------------------------------
/CodeOfConduct.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, gender identity and expression, level of experience,
9 | education, socio-economic status, nationality, personal appearance, race,
10 | religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at {{ email }}. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2021 Mohit Jaisal
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 | 
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 | # About The Project
23 |
24 | 
25 |
26 |
27 |
28 | As you begin your path on becoming a coding specialist it is always pleasant to find good sources of information. Many computer languages might be tricky to learn at the beginning so you need reliable references to double-check your mistakes and learn how to not make them again. This project has a vast range of programming books which you can read online or download locally.
29 |
30 |
31 |
32 |
33 |
34 |
35 | ## Getting Started
36 |
37 | This is an example of how you can set up this project locally.
38 | To get a local copy up and running follow these simple example steps.
39 |
40 | ### Installation
41 |
42 | 1. Fork this repository
43 | 
44 |
45 |
46 |
47 |
48 | 2. Clone the repo
49 |
50 | ```sh
51 | git clone https://github.com/mohitjaisal/CodingBooks.git
52 | ```
53 |
54 | 3. Run index.html
55 |
56 |
57 |
58 | # Contributing Guidelines 🏗
59 | Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**.
60 |
61 |
62 | #### Steps for contribution
63 |
64 | 1. Fork the repo
65 |
66 | 2. Clone the forked repo into your local machine
67 | ``` bash
68 | $ git clone https://github.com/your_username/CodingBooks.git
69 | ```
70 |
71 | 3. cd to the repo
72 | ```bash
73 | $ cd CodingBooks
74 | ```
75 |
76 | 4. Create a branchz
77 | ```bash
78 | $ git checkout -b mybranch
79 | ```
80 |
81 | 5. Open the repo code using any IDE/text-editors
82 |
83 |
84 | 6. Do changes or add the specific feature you are looking in the desired package.
85 |
86 | 7. Add, Commit and Push the changes to your forked repo
87 | ``` bash
88 | $ git add .
89 |
90 | $ git commit -m "your commit message"
91 |
92 | $ git push origin mybranch
93 | ```
94 |
95 | 8. Create a pull request from `mybranch` of your forked repo to `main` branch of this(upstream) repo.
96 |
97 | # Code of Conduct 📜
98 |
99 | To maintain a safe and inclusive space for everyone, to learn and grow, contributors are advised to follow the Code of Conduct and also go through Guidelines for Contributing at least once.
100 | 
101 |
102 |
--------------------------------------------------------------------------------
/addABook.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Coding Books
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
41 |
42 |
43 |
44 |
45 |
46 |
Drive link here :
47 |
add your book to google drive and make sure its public.