├── .github
├── pull_request_template.md
└── workflows
│ ├── checker.yml
│ └── main.yml
├── .vscode
└── settings.json
├── CNAME
├── CONTRIBUTING.md
├── GITHUB.MD
├── HACTOBERFEST.md
├── LICENSE
├── README.md
├── favicon.png
├── index.html
├── index.js
└── styles.css
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## Description
2 |
3 | _Give a summary of the change that you have made_
4 |
5 | Fixes #[ISSUENO]
6 |
7 | ## Mentions
8 |
9 | _Mention and tag the people_
10 |
11 | ## Screenshots of relevant screens
12 |
13 | _Add screenshots of relevant screens_
14 |
15 | ## Developer's checklist
16 |
17 | - [ ] My PR follows the style guidelines of this project
18 | - [ ] I have performed a self-check on my work
19 |
20 | **If changes are made in the code:**
21 |
22 | - [ ] I have followed the [coding guidelines](https://google.github.io/styleguide/jsguide.html)
23 | - [ ] My changes in code generate no new warnings
24 | - [ ] My changes are breaking another fix/feature of the project
25 | - [ ] I have added test cases to show that my feature works
26 | - [ ] I have added relevant screenshots in my PR
27 |
--------------------------------------------------------------------------------
/.github/workflows/checker.yml:
--------------------------------------------------------------------------------
1 |
2 | name: PR has a valid Issue?
3 |
4 | on:
5 | pull_request_target:
6 | types: [ edited, synchronize, opened, reopened ]
7 |
8 | jobs:
9 | checker:
10 | runs-on: ubuntu-latest
11 |
12 | steps:
13 | - uses: actions/checkout@v2
14 |
15 | - name: Issue Validator
16 | uses: HarshCasper/validate-issues-over-pull-requests@v0.1.1
17 | id: validator
18 | with:
19 | prbody: ${{ github.event.pull_request.body }}
20 | prurl: ${{ github.event.pull_request.url }}
21 |
22 | - name: PR has a valid Issue
23 | if: ${{ steps.validator.outputs.valid == 1 }}
24 | env:
25 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
26 | PRNUM: ${{ github.event.pull_request.number }}
27 | run: |
28 | gh pr edit $PRNUM --add-label "PR:Ready-to-Review"
29 | gh pr edit $PRNUM --add-label "hacktoberfest-accepted"
30 | gh pr edit $PRNUM --remove-label "PR:No-Issue"
31 |
32 | - name: PR has no valid Issue
33 | if: ${{ steps.validator.outputs.valid == 0 }}
34 | env:
35 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
36 | PRNUM: ${{ github.event.pull_request.number }}
37 | run: |
38 | gh pr comment $PRNUM --body "PR is not linked to any issue, please make the corresponding changes in the body."
39 | gh pr edit $PRNUM --add-label "PR:No-Issue"
40 |
--------------------------------------------------------------------------------
/.github/workflows/main.yml:
--------------------------------------------------------------------------------
1 | name: 'Add contributors to readme'
2 | on:
3 | push:
4 | branches: [ master ]
5 |
6 | jobs:
7 | contrib-readme-job:
8 | runs-on: ubuntu-latest
9 | name: A job to automate contrib in readme
10 | steps:
11 | - name: Contribute List
12 | uses: akhilmhdh/contributors-readme-action@v2.3.6
13 | env:
14 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
15 |
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "liveServer.settings.port": 5502
3 | }
4 |
--------------------------------------------------------------------------------
/CNAME:
--------------------------------------------------------------------------------
1 | devtrack.club
2 |
--------------------------------------------------------------------------------
/CONTRIBUTING.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 | ## Code Standards
40 | - Every addressed issue solution must be within its own folder.
41 | - Every folder must contain a README.md file with the problem statement and guides to run your code.
42 | - Put requirements.txt file in the folder if the solution requires any external libraries.
43 | - The code must be written in Python 3.
44 |
45 | ## Enforcement Responsibilities
46 |
47 | Community leaders are responsible for clarifying and enforcing our standards of
48 | acceptable behavior and will take appropriate and fair corrective action in
49 | response to any behavior that they deem inappropriate, threatening, offensive,
50 | or harmful.
51 |
52 | Community leaders have the right and responsibility to remove, edit, or reject
53 | comments, commits, code, wiki edits, issues, and other contributions that are
54 | not aligned to this Code of Conduct, and will communicate reasons for moderation
55 | decisions when appropriate.
56 |
57 | ## Scope
58 |
59 | This Code of Conduct applies within all community spaces, and also applies when
60 | an individual is officially representing the community in public spaces.
61 | Examples of representing our community include using an official e-mail address,
62 | posting via an official social media account, or acting as an appointed
63 | representative at an online or offline event.
64 |
65 | ## Enforcement
66 |
67 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
68 | reported to the community leaders responsible for enforcement at @anshrathod1999 on twitter.
69 | All complaints will be reviewed and investigated promptly and fairly.
70 |
71 | All community leaders are obligated to respect the privacy and security of the
72 | reporter of any incident.
73 |
74 | ## Enforcement Guidelines
75 |
76 | Community leaders will follow these Community Impact Guidelines in determining
77 | the consequences for any action they deem in violation of this Code of Conduct:
78 |
79 | ### 1. Correction
80 |
81 | **Community Impact**: Use of inappropriate language or other behavior deemed
82 | unprofessional or unwelcome in the community.
83 |
84 | **Consequence**: A private, written warning from community leaders, providing
85 | clarity around the nature of the violation and an explanation of why the
86 | behavior was inappropriate. A public apology may be requested.
87 |
88 | ### 2. Warning
89 |
90 | **Community Impact**: A violation through a single incident or series
91 | of actions.
92 |
93 | **Consequence**: A warning with consequences for continued behavior. No
94 | interaction with the people involved, including unsolicited interaction with
95 | those enforcing the Code of Conduct, for a specified period of time. This
96 | includes avoiding interactions in community spaces as well as external channels
97 | like social media. Violating these terms may lead to a temporary or
98 | permanent ban.
99 |
100 | ### 3. Temporary Ban
101 |
102 | **Community Impact**: A serious violation of community standards, including
103 | sustained inappropriate behavior.
104 |
105 | **Consequence**: A temporary ban from any sort of interaction or public
106 | communication with the community for a specified period of time. No public or
107 | private interaction with the people involved, including unsolicited interaction
108 | with those enforcing the Code of Conduct, is allowed during this period.
109 | Violating these terms may lead to a permanent ban.
110 |
111 | ### 4. Permanent Ban
112 |
113 | **Community Impact**: Demonstrating a pattern of violation of community
114 | standards, including sustained inappropriate behavior, harassment of an
115 | individual, or aggression toward or disparagement of classes of individuals.
116 |
117 | **Consequence**: A permanent ban from any sort of public interaction within
118 | the community.
119 |
120 | ## Attribution
121 |
122 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
123 | version 2.0, available at
124 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
125 |
126 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
127 | enforcement ladder](https://github.com/mozilla/diversity).
128 |
129 | [homepage]: https://www.contributor-covenant.org
130 |
131 | For answers to common questions about this code of conduct, see the FAQ at
132 | https://www.contributor-covenant.org/faq. Translations are available at
133 | https://www.contributor-covenant.org/translations.
134 |
--------------------------------------------------------------------------------
/GITHUB.MD:
--------------------------------------------------------------------------------
1 | # **Steps to Contribute**
2 | To contribute to this project and other open-source projects, you need to have knowledge of Git and GitHub/Gitlab.
3 | You need to have Git installed on your system. To check whether your system has Git installed, run `git --version`. If you get any version, it means Git is installed on your system otherwise it is not.
4 | To install Git, visit https://git-scm.com/downloads and follow the instructions.
5 |
6 | To make your own local copy of this repository, open up your terminal/ command-line.
7 |
8 | ### **1. Clone the Repository**
9 | We'll use the `git clone` command to clone the repository on our local system.
10 | Copy the repository HTTPS URL and then run the following command: `git clone https://github.com/DevTrackClub/DevTrackWebsite.git`.
11 |
12 | ### **2. Make a new branch**
13 | To create your branch, from your terminal window, change your directory so that you are working in the directory of the repository. Be sure to use the actual name of the repository (i.e. Hacktoberfest-22) to change into that directory.
14 |
15 | ```
16 | cd DevTrackWebsite
17 | ```
18 |
19 | Now, we’ll create our new branch with the `git branch` command. Make sure you name it descriptively so that others working on the project understand what you are working on.
20 |
21 | ```
22 | git branch new-branch
23 | ```
24 |
25 | Now that our new branch is created, we can switch to make sure that we are working on that branch by using the git checkout command:
26 |
27 | ```
28 | git checkout new-branch
29 | ```
30 |
31 | Once you enter the git checkout command, you will receive the following output:
32 |
33 | ```
34 | Output:
35 | Switched to branch 'new-branch'
36 | ```
37 |
38 | At this point, you can now modify existing files or add new files to the project on your own branch.
39 |
40 | ### **3. Make Changes Locally**
41 |
42 | Once you have added new files to the project, you can add them to your local repository, which you can do with the `git add` command. Let’s add the `-A` flag to add all changes that we have made:
43 |
44 | ```
45 | git add -A
46 | ```
47 | or
48 | ```
49 | git add .
50 | ```
51 |
52 | Next, we’ll want to record the changes that we made to the repository with the git commit command.
53 |
54 | The commit message is an important aspect of your code contribution; it helps the other contributors fully understand the change you have made, why you made it, and how significant it is. Additionally, commit messages provide a historical record of the changes for the project at large, helping future contributors along the way.
55 |
56 | If you have a very short message, you can record that with the `-m` flag and the message in quotes:
57 |
58 | Example:
59 |
60 | ```
61 | git commit -m "Updated Readme.md"
62 | ```
63 |
64 | At this point you can use the `git push` command to push the changes to the current branch of your forked repository:
65 |
66 | Example:
67 |
68 | ```
69 | git push --set-upstream origin new-branch
70 | ```
71 |
72 | ### **4. Update Local Repository**
73 |
74 | While you are working on a project alongside other contributors, it is important for you to keep your local repository up-to-date with the project as you don’t want to make a pull request for code that will cause conflicts. To keep your local copy of the code base updated, you’ll need to sync changes.
75 |
76 | We’ll first go over configuring a remote for the fork, then syncing the fork.
77 |
78 | ### **5. Configure a Remote for the Fork**
79 |
80 | Next, you’ll have to specify a new remote upstream repository for us to sync with the fork. This will be the original repository that you forked from. You’ll have to do this with the `git remote add` command.
81 |
82 | ```
83 | git remote add upstream https://github.com/DevTrackClub/DevTrackWebsite.git
84 | ```
85 |
86 | In this example, `upstream` is the shortname we have supplied for the remote repository since in terms of Git, “upstream” refers to the repository that you cloned from. If you want to add a remote pointer to the repository of a collaborator, you may want to provide that collaborator’s username or a shortened nickname for the shortname.
87 |
88 | ### **6. Sync the Fork**
89 |
90 | Once you have configured a remote that references the upstream and original repository on GitHub, you are ready to sync your fork of the repository to keep it up-to-date.
91 |
92 | To sync your fork, from the directory of your local repository in a terminal window, you’ll have to use the `git fetch` command to fetch the branches along with their respective commits from the upstream repository. Since you used the shortname “upstream” to refer to the upstream repository, you’ll have to pass that to the command:
93 |
94 | ```
95 | git fetch upstream
96 | ```
97 |
98 | Switch to the local master branch of our repository:
99 |
100 | ```
101 | git checkout master
102 | ```
103 |
104 | You’ll now have to merge any changes that were made in the original repository’s master branch, that you will access through your local upstream/master branch, with your local master branch:
105 |
106 | ```
107 | git merge upstream/master
108 | ```
109 |
110 | ### **7. Create Pull Request**
111 |
112 | At this point, you are ready to make a pull request to the original repository.
113 |
114 | You should navigate to your forked repository, click on the Contribute button and Open a new PR ( Pull Request ).
115 |
--------------------------------------------------------------------------------
/HACTOBERFEST.md:
--------------------------------------------------------------------------------
1 |
🎃 HacktoberFest-2022 🎃
2 |
3 |    
4 |
5 | # What is HacktoberFest?
6 |
7 | Hacktoberfest is a month long event where people are awarded for contributing to open source projects 🙌, and we're joining the party .Hosted by DigitalOcean for the 8th year in a row, Hacktoberfest encourages participation in giving back to the open source community by completing pull requests, participating in events, and donating to open source projects.
8 |
9 | # More details
10 |
11 | Hacktoberfest is open to everyone in our global community. Whether you’re a seasoned contributor or looking for projects to contribute to for the first time, you’re welcome to participate.
12 |
13 | Pull requests can be made in any participating GitHub or GitLab hosted repository/project. Look for the 'hacktoberfest' topic to know if a repository/project is participating in Hacktoberfest. Pull requests must be approved by a maintainer of the repository/project to count.
14 |
15 | You can sign up anytime between October 1 and October 31. Just be sure to sign up on the official Hacktoberfest website for your pull requests to count.
16 |
17 | # Rules for participation
18 |
19 | * Pull requests can be submitted to any opted-in repository on GitHub or GitLab.
20 | * The pull request must contain commits you made yourself.
21 | * If a maintainer reports your pull request as spam, it will not be counted toward your participation in Hacktoberfest.
22 | * If a maintainer reports behavior that’s not in line with the project’s code of conduct, you will be ineligible to participate.
23 | * To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone.
24 | * This year, the first 55,000 participants can earn a T-shirt.
25 |
26 | # Quality Guidelines
27 |
28 | * Pull requests that are automated e.g. scripted opening pull requests to remove whitespace / fix typos / optimize images.
29 | * Pull requests that are disruptive e.g. taking someone else's branch/commits and making a pull request.
30 | * Pull requests that are regarded by a project maintainer as a hindrance vs. helping.
31 | * Something that's clearly an attempt to simply +1 your pull request count for October.
32 | * Last but not least, one pull request to fix a typo is fine, but 5 pull requests to remove a stray whitespace is not.
33 |
34 | ### Note
35 |
36 | **A pull request is considered approved once it has an overall approving review from maintainers, or has been merged by maintainers, or has been given the 'hacktoberfest-accepted' label. A pull request with any label containing the word 'spam' or 'invalid' will be considered ineligible for Hacktoberfest.**
37 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2022 < Dev / Track >
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 |
DevTrack
2 |
3 | **A Student centric club that aspires to help and encourage students to build projects**
4 | **This repo is of our official website, [DEVTRACK](https://devtrack.tech)**
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 | # How to start
20 |
21 | * It's easy, all you need to know is basic html, css and js to work on this repo.
22 | * I am attaching few links that you could refer to.
23 | * [Refer here for getting the basics](https://www.w3schools.com/)
24 | * [Video tutorial](https://scrimba.com/learn/htmlandcss)
25 | * [Another tutorial](https://scrimba.com/learn/learnjavascript)
26 | * That's it, you are good to fork.
27 |
28 | ## Hacktoberfest 2022 Update
29 |
30 | **See full details and guidelines on**
31 | * [Hacktober cheat sheet](https://github.com/DevTrackClub/DevTrackWebsite/blob/main/HACTOBERFEST.md)
32 | * [Official website](https://hacktoberfest.digitalocean.com/)
33 |
34 |
How to Contribute 🤔
35 |
36 | * Look out for the issues in the issues section.
37 | * If you find a bug or you can enhance the existing code then open a issue and the following.
38 | 1. What's the problem with the existing code. (necessary screenshot along with it could do much better)
39 | 2. What are you planning to do.
40 | * Once done, you can follow these [instructions](https://github.com/DevTrackClub/DevTrackWebsite/blob/main/GITHUB.MD) to do a pull request (Important).
41 |
42 | ## Here are the steps to make a contribution 👣
43 |
44 | - [x] Take a look at [Contributing Guide](https://github.com/DevTrackClub/DevTrackWebsite/blob/main/CONTRIBUTING.md) (Necessary)
45 | - [x] Look out the issue section for any new issues. If you can do it, then ask to assign it to you. (**Note:** It's **goodToFirst**)
46 | - [x] If you find a bug or you wanna enhance the code then create an issue for making any change to code. Once the issue is approved you can make a change.
47 | - [x] Pull latest change from upstream branch before starting the changing code.
48 | - [x] Mention what you have changed with relevant **screenshots**.
49 | - [x] Add your **issue number** along with your pull request.
50 |
51 | # Congratulations!🤩🥳
52 |
53 | Congratulation! You just made your first pull request and if it gets merged, you can view it using this link [https://hacktoberfest.com](https://hacktoberfest.com)
54 |
55 | # Contributors 🤩👩💻👨💻
56 | Kudos to all our contributors. This wouldn't be be possible without you guys. 🎉👏
57 |
58 |
59 |
60 |
61 |
62 |
63 |
--------------------------------------------------------------------------------
/favicon.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/DevTrackClub/DevTrackWebsite/d4cd4be88f6f25a51f14d5d7348487adb95e9401/favicon.png
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | DEV/TRACK
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
39 |
40 |
DEV/TRACK
41 |
A community driven programming and designing club, encouraging hackers to shape their ideas
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
WHO ARE WE ?
51 |
52 |
Dev/Track is our university's premiere student circle to ideate, innovate and
53 | implement various solutions to tackle real-world problems in different tracks including
54 | AI/ML, web3, Mobile App Development, and Web development.
55 | Our mission revolves around connecting enthusiastic minds seeking opportunities
56 | to collaborate and contribute. Dev/Track provides a forum for students to showcase
57 | their skills while building their repertoire and Resume.
58 | We aim to sculpt an environment to help students realize their potential and encourage them
59 | to contribute to a broader tech eco-space.
60 |
61 |
62 |
63 |
64 |
65 |
66 |
WHAT WE DO
67 |
68 |
We at Dev/track are dedicated to helping students upskill their stacks while diversifying
69 | their portfolios.Each idea comes to life in the form of "Projects", each track at D/T has
70 | a set of projects under it led by a "Project Lead" under the guidance of a "Project Guide".
71 | Working on various projects under Dev/Track instills a sense of responsibility among students
72 | and gives them a taste of working in a tech eco-space. The process of Development is held in
73 | "cycles" with each cycle resulting in an addition to your repo. By the end of an academic year,
74 | students will have a sizable amount of contributions under their name and a sharp set of skills.
75 | Experiences at DevTrack cultivate qualities like problem-solving, resourcefulness, collaboration,
76 | and many more, which are considered very much essential in a workforce.
77 | Ultimately Dev/track tries to prepare students for their eventual careers, careers that are
78 | more than just a job.
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
Tracks
87 |
88 |
89 |
90 |
91 |
AI/ML
92 |
Procure, train, integrate and deploy innovative AI-Based solutions for problems of the past, present, and Future.
The advent of technology has furthered the reach and accessibility of Mobile devices. This track is instrumental in providing solutions that are accessible to the masses
A good UI goes a long way in attracting a user base to your projects. Provide engaging solutions that keep your user base invested in your applications.
Being the most popular track in the market, Web 2.0 is still the go-to approach for most solutions. Build cutting-edge sites that solve more than just a problem.