├── .all-contributorsrc
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── index.html
├── package-lock.json
├── package.json
├── postcss.config.cjs
├── public
└── vite.svg
├── readME.md
├── src
├── App.css
├── App.jsx
├── assets
│ ├── Female.png
│ ├── FpfpRandom.png
│ ├── Male.png
│ ├── MpfpRandom.png
│ └── tag.js
├── components
│ ├── home.jsx
│ ├── portfolio.jsx
│ ├── projectCard.jsx
│ └── skills.jsx
├── data.js
├── index.css
└── main.jsx
├── tailwind.config.cjs
├── vercel.json
└── vite.config.js
/.all-contributorsrc:
--------------------------------------------------------------------------------
1 | {
2 | "projectName": "dev-landing-page",
3 | "projectOwner": "rohitranjan-2702",
4 | "repoType": "github",
5 | "repoHost": "https://github.com",
6 | "files": ["readME.md"],
7 | "imageSize": 100,
8 | "commit": false,
9 | "contributorsPerLine": 7,
10 | "contributorsSortAlphabetically": false,
11 | "badgeTemplate": "[](#contributors)",
12 | "contributorTemplate": "\">\" width=\"<%= options.imageSize %>px;\" alt=\"\"/> <%= contributor.name %>",
13 | "types": {
14 | "custom": {
15 | "symbol": "🔭",
16 | "description": "A custom contribution type.",
17 | "link": "[<%= symbol %>](<%= url %> \"<%= description %>\"),"
18 | }
19 | },
20 | "linkToUsage": true,
21 | "skipCi": true,
22 | "contributors": []
23 | }
24 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Logs
2 | logs
3 | *.log
4 | npm-debug.log*
5 | yarn-debug.log*
6 | yarn-error.log*
7 | pnpm-debug.log*
8 | lerna-debug.log*
9 |
10 | node_modules
11 | todo.txt
12 | dist
13 | dist-ssr
14 | *.local
15 |
16 | # Editor directories and files
17 | .vscode/*
18 | !.vscode/extensions.json
19 | .idea
20 | .DS_Store
21 | *.suo
22 | *.ntvs*
23 | *.njsproj
24 | *.sln
25 | *.sw?
26 |
--------------------------------------------------------------------------------
/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 behaviour 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 behaviour and will take appropriate and fair corrective action in
43 | response to any behaviour 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 behaviour may be
62 | reported to the community leaders responsible for enforcement at
63 | .
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 | # 🪛 Want to contribute?
2 |
3 | We welcome you to join us!
4 |
5 | - **Dev Landing Page** is an open-source project, and we are excited to hear your thoughts and ideas.
6 |
7 | - Fork this repository, add your contributions and submit a PR.
8 |
9 | - Found a bug? Accessibility issue? Or do you want to add a new tool to our database? Then go right ahead and create an issue.
10 |
11 | # 🛠️ Tech Stack
12 |
13 | This project uses:
14 | 
15 | 
16 | 
17 | 
18 | 
19 |
20 | ## Prerequisites
21 |
22 | Before installation, you need to have installed/knowledge of the following:
23 |
24 | 
25 | 
26 |
27 | ## STAR THE REPO
28 |
29 | ### How to Contribute to this repository
30 |
31 | 1. Fork the repository (Click the Fork button in the top right of this page, and click your Profile Image)
32 |
33 | 2. Clone the forked repository to your local machine.
34 |
35 | ```markdown
36 | git clone https://github.com/your-username/dev-landing-page.git
37 | ```
38 |
39 | 3. change the present working directory
40 |
41 | ```markdown
42 | cd dev-landing-page.git
43 | ```
44 |
45 | 4. Open CMD in your current directory and install node packages using command.[If node js is not installed, you can install it by clicking on this link to [node js](https://nodejs.org/en)]
46 |
47 | ```markdown
48 | npm i
49 | ```
50 |
51 | > Run it locally using
52 |
53 | ```
54 | npm start
55 | ```
56 |
57 | 6. Make changes to the project.
58 | E.g. Adding the URL of your GitHub Projects in the Skill Sections
59 |
60 | ```
61 | - To ensure that your URLs are short, it is recommended to use **[bitly](https://bitly.com/)** for URL shortening.
62 | - Description should not exceed **10-12 words**
63 | ```
64 |
65 | 7. Add, Commit and push the project by creating a new branch using the following commands:
66 |
67 | > Set upstream command to create a PR
68 |
69 | ```diff
70 | git remote add upstream https://github.com/rohitranjan-2702/dev-landing-page.git
71 | ```
72 |
73 | > Create a new branch
74 |
75 | ```diff
76 | git branch -M
77 | ```
78 |
79 | > Add all files
80 |
81 | ```markdown
82 | git add .
83 | ```
84 |
85 | > Commit the changes
86 |
87 | ```markdown
88 | git commit -m "Write Your commit Message"
89 | ```
90 |
91 | > Push the branch
92 |
93 | ```markdown
94 | git push origin
95 | ```
96 |
97 | 8. Go to https://github.com/rohitranjan-2702/dev-landing-page where you will see a request to create a PR (Pull Request), add your comments and open the PR.
98 |
99 | ### NOTE
100 |
101 | - Make Sure you commit your changes in a new branch.
102 | - Make Sure you Give the proper name to your files describing the addition.
103 | - Also Make Sure you comment on your code wherever necessary.
104 |
105 |
106 | Show some ❤️ by starring this awesome repository!
107 |
6 | A beautifully designed Landing Page for you. Easy to use. Modern UI with your Projects and GitHub repo links.
7 |
8 |
9 |
10 |
11 | # 🙌 Welcome to Dev Landing Page
12 |
13 | - As we all prefer open-source software for our daily use, it can be difficult to find tools that are specific to our needs. This is where **Dev Landing Page** comes in.
14 |
15 | - Dev Landing Page is a Modern UI Portfolio used to display your projects and share them with the World.
16 |
17 | - We all spend hours and weeks creating our own personal Portfolio. Now with Dev Landing Page, it's a few code lines away.
18 |
19 | - Although Dev Landing Page is your stop for your personal portfolio, we recognize that it is still evolving. It will take time for us to add all the projects, resources and additional content that our users want.
20 |
21 | - That's why, we encourage contributions from everyone interested in making Dev Landing Page even more attractive and useful.
22 |
23 | # 🚀 About
24 |
25 | - If you're a developer or a tech enthusiast, you can help us create a better experience for everyone.
26 |
27 | - Dev Landing Page is more than just a tool to create your portfolio. It's also a treasure of useful skills and projects that can help you in many ways.
28 |
29 | - For example, we have curated a list of skill sections which allows you to display a wide range of projects depending on your tech stack.
30 |
31 | - But that's not all – we have big plans for the future. We are working hard to add more useful content that can make your life easier and more productive.
32 | - Stay tuned for updates!
33 |
34 |
35 |
Dev Landing Page can be used by anyone, from casual internet users to professionals!
36 |
37 |
38 | # 🎥 Project Overview
39 |
40 | You can check out the live project [here](https://open-source-dev-landing-page.vercel.app/)
41 |
42 | # 🔍 How to Customize
43 |
44 | 1. Fork the repository.
45 |
46 | 2. Make changes in the file `src/data.js`
47 |
48 |
49 |
50 | 
51 |
52 | `src/data.js`
53 |
54 | 
55 |
56 | 4. Boom! Your landing page is ready !!!
57 |
58 | # 🪛 Want to contribute?
59 |
60 | We welcome you to join us!
61 |
62 | - **Dev Landing Page** is an open-source project, and we are excited to hear your thoughts and ideas.
63 |
64 | - Fork this repository, add your contributions and submit a PR.
65 |
66 | - Found a bug? Accessibility issue? Or do you want to add a new tool to our database? Then go right ahead and create an issue.
67 |
68 | # 🛠️ Tech Stack
69 |
70 | This project uses:
71 | 
72 | 
73 | 
74 | 
75 | 
76 |
77 |
78 | ## Prerequisites
79 |
80 | Before installation, you need to have installed/knowledge of the following:
81 |
82 | 
83 | 
84 |
85 | ## 🤝 Contributing
86 |
87 | Follow the link to contribute to Dev Landing Page - [CONTRIBUTING.md](./CONTRIBUTING.md)
88 |
89 | ## ✨ Project Maintainers
90 |
91 |
Use justify-evenly to justify items along the container’s main axis such that there is an equal amount of space around each item, but also accounting for the doubling of space you would normally see between each item when using justify-around: Use justify-evenly to justify items along the container’s main axis such that there is an equal amount of space around each item