├── .github
├── ISSUE_TEMPLATE
│ ├── bug.yml
│ ├── feature_request.md
│ └── style.yml
├── pull_request_template.md
└── workflows
│ └── greetings.yml
├── .gitignore
├── .vscode
├── extensions.json
└── launch.json
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENCE
├── README.md
├── SECURITY.md
├── astro.config.mjs
├── package-lock.json
├── package.json
├── public
├── hemang.png
├── icon.png
├── icons
│ ├── discord.png
│ ├── github.png
│ ├── instagram.png
│ ├── linkedin.png
│ ├── spotify.png
│ └── x.png
├── screenshot_laptop.png
└── screenshot_phone.png
├── src
├── content
│ └── types.ts
├── env.d.ts
└── pages
│ └── index.astro
├── tailwind.config.cjs
└── tsconfig.tson
/.github/ISSUE_TEMPLATE/bug.yml:
--------------------------------------------------------------------------------
1 |
2 |
3 | name: 🐞 Bug Report
4 | description: File a bug report
5 | title: '[Bug]: '
6 | labels: ['bug']
7 | body:
8 | - type: markdown
9 | attributes:
10 | value: |
11 | Thanks for taking the time to fill out this bug report!
12 | - type: textarea
13 | id: what-happened
14 | attributes:
15 | label: What happened?
16 | description: Also tell us, what did you expect to happen?
17 | placeholder: Add descriptions
18 | value: 'Briefly Describe the bug you found'
19 | validations:
20 | required: true
21 | - type: textarea
22 | id: screenshots
23 | attributes:
24 | label: Add screenshots
25 | description: Add screenshots to see the problems
26 | placeholder: Add screenshots
27 | value: 'Add screenshots'
28 | - type: dropdown
29 | id: browsers
30 | attributes:
31 | label: What browsers are you seeing the problem on?
32 | multiple: true
33 | options:
34 | - Firefox
35 | - Chrome
36 | - Safari
37 | - Microsoft Edge
38 | - Brave
39 | - Other
40 | - type: checkboxes
41 | id: self-grab
42 | attributes:
43 | label: Self - Grab
44 | description: By checking this box, you can fix this bug
45 | options:
46 | - label: I would like to work on this issue
47 | id: terms
48 | attributes:
49 | label: Code of Conduct
50 | description: By submitting this issue, you agree to follow our Code of Conduct
51 | options:
52 | - label: I agree to follow this project's Code of Conduct
53 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | name: Feature request
4 | about: Suggest an idea for this project
5 | title: ''
6 | labels: ''
7 | assignees: ''
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/style.yml:
--------------------------------------------------------------------------------
1 |
2 |
3 | name: 👯♂️ Style Changing Request
4 | description: Suggest a style designs
5 | title: '[style]: '
6 | labels: ['enhancement']
7 | body:
8 | - type: markdown
9 | attributes:
10 | value: |
11 | Thanks for taking the time to fill out this template!
12 | - type: textarea
13 | id: style-idea
14 | attributes:
15 | label: What's the style idea?
16 | placeholder: Add descriptions
17 | value: 'We need to improve '
18 | validations:
19 | required: true
20 | - type: textarea
21 | id: screenshots
22 | attributes:
23 | label: Add screenshots
24 | description: Add screenshots to see the demo
25 | placeholder: Add screenshots
26 | value: 'Add screenshots'
27 | - type: checkboxes
28 | id: terms
29 | attributes:
30 | label: Code of Conduct
31 | description: By submitting this issue, you agree to follow our Code of Conduct
32 | options:
33 | - label: I agree to follow this project's Code of Conduct
34 |
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | ## Fixes Issue
5 |
6 |
7 |
8 |
9 |
10 | ## Changes proposed
11 |
12 |
13 |
14 |
15 |
21 |
22 | ## Check List (Check all the applicable boxes)
23 |
24 | - [ ] My Changes follow the Code of Conduct of this Project.
25 | - [ ] My Post or Change does not contain any **Plagarized** Content.
26 | - [ ] The title of the PR is a short description of the Changes made.
27 |
28 | ## Note to reviewers
29 |
30 |
31 |
--------------------------------------------------------------------------------
/.github/workflows/greetings.yml:
--------------------------------------------------------------------------------
1 |
2 | name: Greetings
3 |
4 | on:
5 | pull_request:
6 | types: [opened]
7 | issues:
8 | types: [opened]
9 |
10 | permissions:
11 | issues: write
12 | pull-requests: write
13 |
14 | jobs:
15 | greet:
16 | runs-on: ubuntu-latest
17 | steps:
18 | - name: Greet on PRs and Issues
19 | uses: actions/github-script@v7
20 | with:
21 | script: |
22 | try {
23 | const isPR = context.payload.pull_request !== undefined;
24 | const number = isPR ? context.payload.pull_request.number : context.payload.issue.number;
25 | const commentBody = isPR
26 | ? `Welcome, @${{ github.actor }}! Thanks for raising the issue!`
27 | : `Great job, @${{ github.actor }}! Thanks for creating the pull request`;
28 |
29 | await github.rest.issues.createComment({
30 | owner: context.repo.owner,
31 | repo: context.repo.repo,
32 | issue_number: number,
33 | body: commentBody
34 | });
35 |
36 | console.log('Comment successfully created.');
37 | } catch (error) {
38 | console.error('Error creating comment:', error);
39 | // Do not mark the step as failed; continue with the workflow.
40 | }
41 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # build output
2 | dist/
3 | # generated types
4 | .astro/
5 |
6 | # dependencies
7 | node_modules/
8 |
9 | # logs
10 | npm-debug.log*
11 | yarn-debug.log*
12 | yarn-error.log*
13 | pnpm-debug.log*
14 |
15 |
16 | # environment variables
17 | .env
18 | .env.production
19 |
20 | # macOS-specific files
21 | .DS_Store
22 |
23 | # Local Netlify folder
24 | .netlify
25 |
--------------------------------------------------------------------------------
/.vscode/extensions.json:
--------------------------------------------------------------------------------
1 | {
2 | "recommendations": ["astro-build.astro-vscode"],
3 | "unwantedRecommendations": []
4 | }
5 |
--------------------------------------------------------------------------------
/.vscode/launch.json:
--------------------------------------------------------------------------------
1 | {
2 | "version": "0.2.0",
3 | "configurations": [
4 | {
5 | "command": "./node_modules/.bin/astro dev",
6 | "name": "Development server",
7 | "request": "launch",
8 | "type": "node-terminal"
9 | }
10 | ]
11 | }
12 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | # Contributor Covenant Code of Conduct
4 |
5 | ## Our Pledge
6 |
7 | We as members, contributors, and leaders pledge to make participation in our
8 | community a harassment-free experience for everyone, regardless of age, body
9 | size, visible or invisible disability, ethnicity, sex characteristics, gender
10 | identity and expression, level of experience, education, socio-economic status,
11 | nationality, personal appearance, race, religion, or sexual identity
12 | and orientation.
13 |
14 | We pledge to act and interact in ways that contribute to an open, welcoming,
15 | diverse, inclusive, and healthy community.
16 |
17 | ## Our Standards
18 |
19 | Examples of behavior that contributes to a positive environment for our
20 | community include:
21 |
22 | * Demonstrating empathy and kindness toward other people
23 | * Being respectful of differing opinions, viewpoints, and experiences
24 | * Giving and gracefully accepting constructive feedback
25 | * Accepting responsibility and apologizing to those affected by our mistakes,
26 | and learning from the experience
27 | * Focusing on what is best not just for us as individuals, but for the
28 | overall community
29 |
30 | Examples of unacceptable behavior include:
31 |
32 | * The use of sexualized language or imagery, and sexual attention or
33 | advances of any kind
34 | * Trolling, insulting or derogatory comments, and personal or political attacks
35 | * Public or private harassment
36 | * Publishing others' private information, such as a physical or email
37 | address, without their explicit permission
38 | * Other conduct which could reasonably be considered inappropriate in a
39 | professional setting
40 |
41 | ## Enforcement Responsibilities
42 |
43 | Community leaders are responsible for clarifying and enforcing our standards of
44 | acceptable behavior and will take appropriate and fair corrective action in
45 | response to any behavior that they deem inappropriate, threatening, offensive,
46 | or harmful.
47 |
48 | Community leaders have the right and responsibility to remove, edit, or reject
49 | comments, commits, code, wiki edits, issues, and other contributions that are
50 | not aligned to this Code of Conduct, and will communicate reasons for moderation
51 | decisions when appropriate.
52 |
53 | ## Scope
54 |
55 | This Code of Conduct applies within all community spaces, and also applies when
56 | an individual is officially representing the community in public spaces.
57 | Examples of representing our community include using an official e-mail address,
58 | posting via an official social media account, or acting as an appointed
59 | representative at an online or offline event.
60 |
61 | ## Enforcement
62 |
63 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
64 | reported to the community leaders responsible for enforcement at
65 | zemerikY@gmail.com.
66 | All complaints will be reviewed and investigated promptly and fairly.
67 |
68 | All community leaders are obligated to respect the privacy and security of the
69 | reporter of any incident.
70 |
71 | ## Enforcement Guidelines
72 |
73 | Community leaders will follow these Community Impact Guidelines in determining
74 | the consequences for any action they deem in violation of this Code of Conduct:
75 |
76 | ### 1. Correction
77 |
78 | **Community Impact**: Use of inappropriate language or other behavior deemed
79 | unprofessional or unwelcome in the community.
80 |
81 | **Consequence**: A private, written warning from community leaders, providing
82 | clarity around the nature of the violation and an explanation of why the
83 | behavior was inappropriate. A public apology may be requested.
84 |
85 | ### 2. Warning
86 |
87 | **Community Impact**: A violation through a single incident or series
88 | of actions.
89 |
90 | **Consequence**: A warning with consequences for continued behavior. No
91 | interaction with the people involved, including unsolicited interaction with
92 | those enforcing the Code of Conduct, for a specified period of time. This
93 | includes avoiding interactions in community spaces as well as external channels
94 | like social media. Violating these terms may lead to a temporary or
95 | permanent ban.
96 |
97 | ### 3. Temporary Ban
98 |
99 | **Community Impact**: A serious violation of community standards, including
100 | sustained inappropriate behavior.
101 |
102 | **Consequence**: A temporary ban from any sort of interaction or public
103 | communication with the community for a specified period of time. No public or
104 | private interaction with the people involved, including unsolicited interaction
105 | with those enforcing the Code of Conduct, is allowed during this period.
106 | Violating these terms may lead to a permanent ban.
107 |
108 | ### 4. Permanent Ban
109 |
110 | **Community Impact**: Demonstrating a pattern of violation of community
111 | standards, including sustained inappropriate behavior, harassment of an
112 | individual, or aggression toward or disparagement of classes of individuals.
113 |
114 | **Consequence**: A permanent ban from any sort of public interaction within
115 | the community.
116 |
117 | ## Attribution
118 |
119 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
120 | version 2.0, available at
121 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
122 |
123 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
124 | enforcement ladder](https://github.com/mozilla/diversity).
125 |
126 | [homepage]: https://www.contributor-covenant.org
127 |
128 | For answers to common questions about this code of conduct, see the FAQ at
129 | https://www.contributor-covenant.org/faq. Translations are available at
130 | https://www.contributor-covenant.org/translations.
131 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 | Zemerik's Linktree
15 |
16 |
17 |
18 | Central Hub of Connections
19 |
20 |
21 |
22 |
23 |
24 |
25 | ## ❓ How to Contribute?
26 |
27 | - All Contributions are highly appreciated, if you would like to contribute to this project, follow the steps below.
28 |
29 | 1. Fork a copy of this Repository on your Github account by clicking below,
30 |
31 | - [Fork](https://github.com/Zemerik/Linktree/fork)
32 |
33 | 2. Clone your Forked Repository by using the following `GIT` command:
34 |
35 | ```bash
36 | git clone https://github.com/[YOUR GITHUB USERNAME]/Linktree.git
37 | ```
38 |
39 | 3. Navigate into the Project's `Directory` by using the command below:
40 |
41 | ```bash
42 | cd Linktree
43 | ```
44 |
45 | 4. Initialize a Remote to the original Repository by the following `GIT` command:
46 |
47 | ```bash
48 | git remote add upstream https://github.com/Zemerik/Linktree
49 | ```
50 |
51 | 5. Create a new `branch` in which you can make your desired changes:
52 |
53 | ```bash
54 | git checkout -b newcontribution
55 | ```
56 |
57 | 6. After making your changes, add all your files to the Staging Area:
58 |
59 | ```bash
60 | git add --all
61 | ```
62 |
63 | 7. Commit your Changes:
64 |
65 | ```bash
66 | git commit -m "[COMMIT MSG]"
67 | ```
68 |
69 | > [!Note]
70 | > Remember to live a good commit message
71 |
72 | 8. Push all your Changes:
73 |
74 | ```bash
75 | git push origin newcontribution
76 | ```
77 |
78 | 9. Create a new Pull - Request (PR) on the Original Repository
79 |
80 | > Your Pull Request will be merged / reviewed as soon as possible.
81 |
82 | ## 🐞Bug/Issue/Feedback/Feature Request:
83 |
84 | - If you would like to report a bug, a issue, implement any feedack, or request any feature, you are free to do so by opening a issue on this repository. Remember to give a detailed explanation of what you are trying to say, and how it will help the website.
85 |
86 | ## 💁 Support:
87 |
88 | For any kind of support or inforrmation, you are free to join our **Discord Server**,
89 |
90 |
91 |
92 |
93 |
94 |
--------------------------------------------------------------------------------
/LICENCE:
--------------------------------------------------------------------------------
1 |
2 |
3 | MIT License
4 |
5 | Copyright (c) 2025 Hemang Yadav
6 |
7 | Permission is hereby granted, free of charge, to any person obtaining a copy
8 | of this software and associated documentation files (the "Software"), to deal
9 | in the Software without restriction, including without limitation the rights
10 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
11 | copies of the Software, and to permit persons to whom the Software is
12 | furnished to do so, subject to the following conditions:
13 |
14 | The above copyright notice and this permission notice shall be included in all
15 | copies or substantial portions of the Software.
16 |
17 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
18 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
19 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
20 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
21 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
22 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
23 | SOFTWARE.
24 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Zemerik's Linktree
16 |
17 |
18 |
19 | Central Hub of Connections
20 |
21 |
22 |
23 |
24 |
25 |
26 | ## ❗About:
27 |
28 | Welcome to my Central Hub of Connections! Discover an organized and seamless collection of all my key digital links, offering direct access to my projects, social media, portfolio, and more. This hub provides an effortless way to explore the various facets of my online presence, whether you're looking to dive into my work, connect professionally, or stay updated with my latest activities. With a simple yet powerful layout, this central resource allows you to navigate through everything in one convenient place. Explore my links and stay connected to everything I have to offer!
29 |
30 | ## ⭐ Key Features:
31 |
32 | - Find all of my Links
33 |
34 | - Connect through Social Media
35 |
36 | - Modernized Gradient Background
37 |
38 | ## 💻 Screenshots:
39 |
40 | 
41 |
42 | ## 🚀 Quick Start:
43 |
44 | ### Prerequisites:
45 |
46 | - [NodeJS](https://nodejs.org) installed on your machine
47 | - [GIT](https://git-scm.com) installed on your machine
48 | - A Code Editor
49 |
50 | ### Cloning:
51 |
52 | - To make a local copy of this Project on your machine, enter the following `GIT` Commmand in your Terminal:
53 |
54 | ```bash
55 | git clone https://github.com/Zemerik/Linktree
56 | ```
57 |
58 | ### Installing Dependencies:
59 |
60 | - To run this project locally, we first need to download a few `npm` dependencies by using the command below:
61 |
62 | ```bash
63 | npm i
64 | ```
65 |
66 | ### Locally Running:
67 |
68 | - We can locally run this Project on our Network and see the output using the following Command of `NodeJS`:
69 |
70 | ```bash
71 | npm run dev
72 | ```
73 |
74 | ## 😎 Happy Coding!!
75 |
76 | ## 🚀 Project Structure
77 |
78 | ```text
79 | ├── public/
80 | │ ├── icons/
81 | ├── src/
82 | │ ├── content
83 | │ └── pages/
84 | ├── .gitignore
85 | ├── astro.config.mjs
86 | ├── README.md
87 | ├── CODE_OF_CONDUCT.md
88 | ├── CONTRIBUTING.md
89 | ├── SECURITY.md
90 | ├── Licence
91 | ├── package.json
92 | ├── package-lock.json
93 | ├── tailwind.config.mjs
94 | └── tsconfig.tson
95 | ```
96 |
97 | ## 🤝 Contributing:
98 |
99 | Contributions are always welcome and appreciated! **Kindly visit the [CONTRIBUTING.md](https://github.com/Zemerik/Resume/blob/main/CONTRIBUTING.md) file for more information**
100 |
101 |
102 | ## 💁 Support:
103 |
104 | For any kind of support or inforrmation, you are free to join our **Discord Server**,
105 |
106 |
107 |
108 |
109 |
110 | #
111 |
112 |
4 |
5 | 
23 | 
70 | 98 |
101 | ))
102 | }
103 |