├── .DS_Store
├── Code-of-conduct.md
├── LICENSE
├── README.md
├── contribution.css
├── contribution.html
├── contribution.md
├── data.json
├── details.css
├── details.html
├── favicon
├── android-chrome-192x192.png
├── android-chrome-512x512.png
├── apple-touch-icon.png
├── favicon-16x16.png
├── favicon-32x32.png
├── favicon.ico
└── site.webmanifest
├── icons8-back-arrow-96.png
├── imgs
├── .DS_Store
└── contriimg.png
├── index.html
├── index.js
└── style.css
/.DS_Store:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/vijayyprajapati/Share-Your-Bookmarks/9482d97e802c87f2e8a5daee6825c8d43de1b07f/.DS_Store
--------------------------------------------------------------------------------
/Code-of-conduct.md:
--------------------------------------------------------------------------------
1 | # Contributor Code of Conduct
2 |
3 | Our [society values](https://gdsc.community.dev/jss-academy-of-technical-education-noida/) guide us in our day-to-day interactions and decision-making. Our open source projects are no exception. Trust, respect, collaboration and transparency are core values we believe should live and breathe within our projects. Our community welcomes participants from around the world with different experiences, unique perspectives, and great ideas to share.
4 |
5 | ## Our Pledge
6 |
7 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
8 |
9 | ## Our Standards
10 |
11 | Examples of behavior that contributes to creating a positive environment include:
12 |
13 | - Using welcoming and inclusive language
14 | - Being respectful of differing viewpoints and experiences
15 | - Gracefully accepting constructive criticism
16 | - Attempting collaboration before conflict
17 | - Focusing on what is best for the community
18 | - Showing empathy towards other community members
19 |
20 | Examples of unacceptable behavior by participants include:
21 |
22 | - Violence, threats of violence, or inciting others to commit self-harm
23 | - The use of sexualized language or imagery and unwelcome sexual attention or advances
24 | - Trolling, intentionally spreading misinformation, insulting/derogatory comments, and personal or political attacks
25 | - Public or private harassment
26 | - Publishing others' private information, such as a physical or electronic address, without explicit permission
27 | - Abuse of the reporting process to intentionally harass or exclude others
28 | - Advocating for, or encouraging, any of the above behavior
29 | - Other conduct which could reasonably be considered inappropriate in a professional setting
30 |
31 | ## Our Responsibilities
32 |
33 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
34 |
35 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
36 |
37 | ## Scope
38 |
39 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
40 |
41 | ## Enforcement
42 |
43 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting us anonymously through our website. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
44 |
45 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
46 |
47 | If you are unsure whether an incident is a violation, or whether the space where the incident took place is covered by our Code of Conduct, **we encourage you to still report it**. We would prefer to have a few extra reports where we decide to take no action, than to leave an incident go unnoticed and unresolved that may result in an individual or group to feel like they can no longer participate in the community. Reports deemed as not a violation will also allow us to improve our Code of Conduct and processes surrounding it. If you witness a dangerous situation or someone in distress, we encourage you to report even if you are only an observer.
48 |
49 | ## Attribution
50 |
51 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), [version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
52 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2022 Vijay Kumar Prajapati
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 |
8 |
9 |
17 |
18 | ## Share-Your-Bookmark:
19 |
20 | A platform where anyone can make their profile, share their Twitter and LinkedIn bookmarks, see other shared bookmarks, and contribute to the community.
21 |
22 | #### Website for this repository :
23 |
24 | ## Technology Stack used:
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 | - **Frontend**: HTML5, CSS3, JavaScript
33 |
34 | - **IDE**: [Visual Studio Code](https://code.visualstudio.com/download)
35 | - **Version Control**: [Git](https://git-scm.com/downloads) and [GitHub](https://git-scm.com/downloads)
36 |
37 | ## Steps to Contribute
38 |
39 | 1. **Fork** this repository by clicking on the fork button on the upper right corner.
40 | 2. **Clone** the repo by typing this command in your command prompt or git bash:
41 |
42 | ```
43 | git clone git@github.com:/Share-Your-Bookmarks.git
44 | ```
45 |
46 | 3. **Edit** `data.json` file in your favourite code editor by pasting this code at the end of the array. See others code for reference.
47 |
48 | ```json
49 | {
50 | "name": "your name here",
51 | "username": "your unique username here",
52 | "bio": "your bio here",
53 |
54 | "links": [
55 | "your first bookmark link",
56 | "your second bookmark link",
57 | "your third bookmark link",
58 | "your fourth bookmark link",
59 | "your fifth bookmark link"
60 | ],
61 | "social": [
62 | {
63 | "twitter": "your twitter/other handle here"
64 | },
65 | {
66 | "linkedin": "your linkedin/other handle here"
67 | }
68 | ]
69 | },
70 | ```
71 |
72 | 4. Type these commands in your cmd/git bash to **stage, commit and push** the changes in your cloned repo.
73 |
74 | ```
75 | git stage .
76 | git commit -m "your message"
77 | git push origin master
78 | ```
79 |
80 | 5. Now, **create and submit a pull request** by clicking on Contribute button on your GitHub repo. But, first be sure to fetch and merge the upstream from the original repo by clicking on Sync fork > Update branch button.
81 |
82 | ## Our Contributors !! ✨
83 |
84 | ### Thanks to these wonderful people: ✨
85 |
86 |