"
4 | labels: ["Goal: fix"]
5 | body:
6 | - type: checkboxes
7 | attributes:
8 | label: Is there any existing issue for this?
9 | description: Please search to see if an issue already exist for the bug you have encountered.
10 | options:
11 | - label: I have searched the existing issues
12 | required: true
13 | - type: textarea
14 | attributes:
15 | label: Description
16 | id: description
17 | description: A brief description of the issue or bug you are facing, also include what you tried and what didn't work.
18 | validations:
19 | required: false
20 | - type: textarea
21 | attributes:
22 | label: Screenshots
23 | id: screenshots
24 | description: Please add screenshots if applicable
25 | validations:
26 | required: false
27 | - type: textarea
28 | attributes:
29 | label: Any additional information?
30 | id: extrainfo
31 | description: Any additional information or Is there anything we should know about this bug?
32 | validations:
33 | required: false
34 | - type: dropdown
35 | id: browsers
36 | attributes:
37 | label: What browser are you seeing the problem on?
38 | multiple: true
39 | options:
40 | - Firefox
41 | - Chrome
42 | - Safari
43 | - Microsoft Edge
44 | - label: "I am a GSSoC'23 contributor"
45 | required: false
46 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/docs.yml:
--------------------------------------------------------------------------------
1 | name: 🔖 Documentation update
2 | description: Improve Documentation
3 | title: "[Docs]: "
4 | labels: ["documentation"]
5 | body:
6 | - type: markdown
7 | attributes:
8 | value: |
9 | Thanks for taking the time to fill out this documentation update template!
10 | - type: textarea
11 | id: improve-docs
12 | attributes:
13 | label: what's wrong in the documentation?
14 | description: which things need to add?
15 | placeholder: Add descriptions
16 | value: "We need to add "
17 | validations:
18 | required: true
19 | - type: textarea
20 | id: screenshots
21 | attributes:
22 | label: Add screenshots
23 | description: Add screenshots to see the demo
24 | placeholder: Add screenshots
25 | value: "Add screenshots"
26 | - type: checkboxes
27 | id: terms
28 | attributes:
29 | label: Code of Conduct
30 | description: By submitting this issue, you agree to follow our Code of Conduct
31 | options:
32 | - label: I agree to follow this project's Code of Conduct
33 | - label: "I am a GSSoC'23 contributor"
34 | required: false
35 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature-request.yml:
--------------------------------------------------------------------------------
1 | name: "Feature Request 💡"
2 | description: "Have any new idea or new feature for DevsInTech? Please request!"
3 | title: "[Feature] "
4 | labels: ["Goal: addition"]
5 | body:
6 | - type: textarea
7 | id: description
8 | attributes:
9 | label: Description
10 | description: A clear and concise description of any alternative solution or features you've considered.
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: screenshots
15 | attributes:
16 | label: Screenshots
17 | description: Please add screenshots if applicable
18 | validations:
19 | required: false
20 | - type: textarea
21 | id: extrainfo
22 | attributes:
23 | label: Additional Information
24 | description: Add any other context or anything else about this idea
25 | validations:
26 | required: false
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 | - label: "I am a GSSoC'23 contributor"
35 | required: false
36 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/other.yml:
--------------------------------------------------------------------------------
1 | name: Other
2 | description: Use this for any other question or issue. Please do not create blank issues
3 | title: "[OTHER]"
4 | labels: ["status: awaiting triage"]
5 | body:
6 | - type: textarea
7 | id: issuedescription
8 | attributes:
9 | label: What would you like to share or ask?
10 | description: Provide a clear and concise explanation of your issue.
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: extrainfo
15 | attributes:
16 | label: Additional information
17 | description: Is there anything else you want to add?
18 | validations:
19 | required: false
20 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/style.yml:
--------------------------------------------------------------------------------
1 | name: "Style Changing Request"
2 | description: "Suggest style designs"
3 | title: "[style]: "
4 | labels: ["style"]
5 | body:
6 | - type: markdown
7 | attributes:
8 | value: |
9 | Thanks for taking the time to fill out this template!
10 | - type: textarea
11 | id: style-idea
12 | attributes:
13 | label: What's the style idea?
14 | placeholder: Add descriptions
15 | value: "We need to improve "
16 | validations:
17 | required: true
18 | - type: textarea
19 | id: screenshots
20 | attributes:
21 | label: Add screenshots
22 | description: Add screenshots to showcase the style
23 | placeholder: Add screenshots
24 | value: "Add screenshots"
25 | - type: checkboxes
26 | id: terms
27 | attributes:
28 | label: Code of Conduct
29 | description: By submitting this issue, you agree to follow our Code of Conduct
30 | options:
31 | - label: "I agree to follow this project's Code of Conduct"
32 | - type: checkboxes
33 | id: gssoc
34 | attributes:
35 | label: GSSoC'23
36 | description: "This is for GSSoC'23 contributors only."
37 | options:
38 | - label: "I am a GSSoC'23 Contributor."
39 |
--------------------------------------------------------------------------------
/.github/dependabot.yml:
--------------------------------------------------------------------------------
1 | version: 2
2 | updates:
3 | - package-ecosystem: 'npm'
4 | directory: '/'
5 | schedule:
6 | interval: 'daily'
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | ## Fixes Issue
4 |
5 |
6 |
7 |
8 |
9 | ## Changes proposed
10 |
11 |
12 |
13 | ## Screenshots
14 |
15 |
16 |
17 | ## Note to reviewers
18 |
19 |
20 |
--------------------------------------------------------------------------------
/.github/workflows/auto-comment.yml:
--------------------------------------------------------------------------------
1 | name: Auto Comment
2 | on:
3 | issues:
4 | types:
5 | - opened
6 | - closed
7 | - assigned
8 | pull_request:
9 | types:
10 | - opened
11 | - closed
12 |
13 | jobs:
14 | run:
15 | runs-on: ubuntu-latest
16 | steps:
17 | - name: Auto Comment on Issues Opened
18 | uses: wow-actions/auto-comment@v1
19 | with:
20 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
21 | issuesOpened: |
22 | 👋 @{{ author }}
23 |
24 | Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
25 |
26 | Please make sure you have given us as much context as possible.
27 |
28 | - name: Auto Comment on Issues Closed
29 | uses: wow-actions/auto-comment@v1
30 | with:
31 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
32 | issuesClosed: |
33 | 👋 @{{ author }} This issue is closed.
34 |
35 | - name: Auto Comment on Pull Request Merged
36 | uses: wow-actions/auto-comment@v1
37 | with:
38 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
39 | pullRequestMerged: |
40 | 👋 @{{ author }} 🎉 Congrats on your merged pull request! Thanks for the valuable contribution! 👏🎉 Congrats on your merged pull request! Thanks for the valuable contribution! 👏
41 |
42 | - name: Auto Comment on Pull Request Opened
43 | uses: wow-actions/auto-comment@v1
44 | with:
45 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
46 | pullRequestOpened: |
47 | Hello👋 @{{ author }}, I hope you are doing well!
48 |
49 | Thank you for raising your pull request and contributing to our Community 🎉
50 |
51 | Please make sure you have followed our contributing guidelines. We will review it as soon as possible.
52 |
53 | - name: Auto Comment on Issues Assigned
54 | uses: wow-actions/auto-comment@v1
55 | with:
56 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
57 | issuesAssigned: |
58 | Hello @{{ author }}, thank you for raising an issue. 🙌 Kindly wait for the maintainers to assign you the issue before starting any work on it. If you encounter any problems, please feel free to connect with us. 👍
59 |
60 |
61 |
--------------------------------------------------------------------------------
/.github/workflows/close_old_issues.yml:
--------------------------------------------------------------------------------
1 | ---
2 | name: Close Old Issues
3 | on:
4 | schedule:
5 | - cron: 0 0 * * *
6 | jobs:
7 | close-issues:
8 | runs-on: ubuntu-latest
9 | steps:
10 | - name: Checkout Repository
11 | uses: actions/checkout@v3
12 | - name: Close Old Issues
13 | run: >
14 | open_issues=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}"
15 | \
16 | "https://api.github.com/repos/${{ github.repository }}/issues?state=open" \
17 | | jq -r '.[] | .number')
18 | for issue in $open_issues; do
19 | # Get the last updated timestamp of the issue
20 | last_updated=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
21 | "https://api.github.com/repos/${{ github.repository }}/issues/$issue" \
22 | | jq -r '.updated_at')
23 | days_since_update=$(( ( $(date +%s) - $(date -d "$last_updated" +%s) ) / 86400 ))
24 | if [ $days_since_update -gt 20 ]; then # Modify the condition to check if days_since_update is greater than 20
25 | curl -s -X PATCH -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
26 | -H "Accept: application/vnd.github.v3+json" \
27 | -d '{"state":"closed"}' \
28 | "https://api.github.com/repos/${{ github.repository }}/issues/$issue"
29 | fi
30 | done
--------------------------------------------------------------------------------
/.github/workflows/codeql.yml:
--------------------------------------------------------------------------------
1 | # For most projects, this workflow file will not need changing; you simply need
2 | # to commit it to your repository.
3 | #
4 | # You may wish to alter this file to override the set of languages analyzed,
5 | # or to provide custom queries or build logic.
6 | #
7 | # ******** NOTE ********
8 | # We have attempted to detect the languages in your repository. Please check
9 | # the `language` matrix defined below to confirm you have the correct set of
10 | # supported CodeQL languages.
11 | #
12 | name: "CodeQL"
13 |
14 | on:
15 | push:
16 | branches: [ "main" ]
17 | pull_request:
18 | # The branches below must be a subset of the branches above
19 | branches: [ "main" ]
20 | schedule:
21 | - cron: '43 3 * * 6'
22 |
23 | jobs:
24 | analyze:
25 | name: Analyze
26 | runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
27 | timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }}
28 | permissions:
29 | actions: read
30 | contents: read
31 | security-events: write
32 |
33 | strategy:
34 | fail-fast: false
35 | matrix:
36 | language: [ 'javascript' ]
37 | # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby', 'swift' ]
38 | # Use only 'java' to analyze code written in Java, Kotlin or both
39 | # Use only 'javascript' to analyze code written in JavaScript, TypeScript or both
40 | # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
41 |
42 | steps:
43 | - name: Checkout repository
44 | uses: actions/checkout@v3
45 |
46 | # Initializes the CodeQL tools for scanning.
47 | - name: Initialize CodeQL
48 | uses: github/codeql-action/init@v2
49 | with:
50 | languages: ${{ matrix.language }}
51 | # If you wish to specify custom queries, you can do so here or in a config file.
52 | # By default, queries listed here will override any specified in a config file.
53 | # Prefix the list here with "+" to use these queries and those in the config file.
54 |
55 | # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
56 | # queries: security-extended,security-and-quality
57 |
58 |
59 | # Autobuild attempts to build any compiled languages (C/C++, C#, Go, Java, or Swift).
60 | # If this step fails, then you should remove it and run the build manually (see below)
61 | - name: Autobuild
62 | uses: github/codeql-action/autobuild@v2
63 |
64 | # ℹ️ Command-line programs to run using the OS shell.
65 | # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
66 |
67 | # If the Autobuild fails above, remove it and uncomment the following three lines.
68 | # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
69 |
70 | # - run: |
71 | # echo "Run, Build Application using script"
72 | # ./location_of_script_within_repo/buildscript.sh
73 |
74 | - name: Perform CodeQL Analysis
75 | uses: github/codeql-action/analyze@v2
76 | with:
77 | category: "/language:${{matrix.language}}"
--------------------------------------------------------------------------------
/.github/workflows/issues.yml:
--------------------------------------------------------------------------------
1 | ---
2 | name: Add Comment to Newly Open Issue
3 | on:
4 | issues:
5 | types:
6 | - opened
7 | jobs:
8 | add-comment:
9 | runs-on: ubuntu-latest
10 | permissions:
11 | issues: write
12 | steps:
13 | - name: Checkout repository
14 | uses: actions/checkout@v3
15 | - name: Add Comment
16 | uses: actions/github-script@v4
17 | with:
18 | github-token: ${{ secrets.GITHUB_TOKEN }}
19 | script: >
20 | const { issue } = context.payload;
21 |
22 | const author = issue.user.login;
23 |
24 | const issueNumber = issue.number;
25 |
26 | const comment = `Hello @${author}! \n Thank you for raising this issue. \nPlease make sure to follow our [Contributing Guidelines.](https://github.com/devs-in-tech/DevsInTech/blob/main/CONTRIBUTING.md) \nDon't forget to ⭐ our [DevsInTech](https://github.com/devs-in-tech/DevsInTech)\n\nOur review team will carefully assess the issue and reach out to you soon!\n We appreciate your patience!`;
27 |
28 | const { owner, repo } = context.repo;
29 |
30 | await github.issues.createComment({
31 | owner: owner,
32 | repo: repo,
33 | issue_number: issueNumber,
34 | body: comment
35 | });
36 |
37 | console.log(`Comment added to the Issue #${issueNumber}.`);
--------------------------------------------------------------------------------
/.github/workflows/lint.yml:
--------------------------------------------------------------------------------
1 | name: Linting
2 |
3 | on: [push, pull_request]
4 |
5 | jobs:
6 |
7 | Linting:
8 |
9 | runs-on: ubuntu-latest
10 |
11 | steps:
12 |
13 | - name: Checkout
14 | uses: actions/checkout@v3
15 | with:
16 | ref: ${{ github.head_ref }}
17 |
18 | - name: Lint code with prettier
19 | uses: creyD/prettier_action@v4.3
20 | with:
21 | prettier_options: --write **/*.{js,md}
22 |
--------------------------------------------------------------------------------
/.github/workflows/lock.yml:
--------------------------------------------------------------------------------
1 | name: 'Issue Lockdown'
2 |
3 | on:
4 | issues:
5 | types: opened
6 |
7 | permissions:
8 | issues: write
9 |
10 | jobs:
11 | action:
12 | runs-on: ubuntu-latest
13 | steps:
14 | - uses: dessant/repo-lockdown@v3 # Reference: https://github.com/dessant/repo-lockdown
15 | with:
16 | close-issue: false
17 | process-only: 'issues'
18 | issue-labels: 'gssoc23'
19 | exclude-issue-labels: '🚀 ready'
20 | skip-closed-issue-comment: true
21 | issue-comment: >
22 | To reduce notifications, issues are locked. Your issue will be unlocked when we add the label, `🚀 ready`.
--------------------------------------------------------------------------------
/.github/workflows/nextjs.yml:
--------------------------------------------------------------------------------
1 | # Sample workflow for building and deploying a Next.js site to GitHub Pages
2 | #
3 | # To get started with Next.js see: https://nextjs.org/docs/getting-started
4 | #
5 | name: Deploy Next.js site to Pages
6 |
7 | on:
8 | # Runs on pushes targeting the default branch
9 | push:
10 | branches: ["main"]
11 |
12 | # Allows you to run this workflow manually from the Actions tab
13 | workflow_dispatch:
14 |
15 | # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
16 | permissions:
17 | contents: read
18 | pages: write
19 | id-token: write
20 |
21 | # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
22 | # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
23 | concurrency:
24 | group: "pages"
25 | cancel-in-progress: false
26 |
27 | jobs:
28 | # Build job
29 | build:
30 | runs-on: ubuntu-latest
31 | steps:
32 | - name: Checkout
33 | uses: actions/checkout@v3
34 | - name: Detect package manager
35 | id: detect-package-manager
36 | run: |
37 | if [ -f "${{ github.workspace }}/yarn.lock" ]; then
38 | echo "manager=yarn" >> $GITHUB_OUTPUT
39 | echo "command=install" >> $GITHUB_OUTPUT
40 | echo "runner=yarn" >> $GITHUB_OUTPUT
41 | exit 0
42 | elif [ -f "${{ github.workspace }}/package.json" ]; then
43 | echo "manager=npm" >> $GITHUB_OUTPUT
44 | echo "command=ci" >> $GITHUB_OUTPUT
45 | echo "runner=npx --no-install" >> $GITHUB_OUTPUT
46 | exit 0
47 | else
48 | echo "Unable to determine package manager"
49 | exit 1
50 | fi
51 | - name: Setup Node
52 | uses: actions/setup-node@v3
53 | with:
54 | node-version: "16"
55 | cache: ${{ steps.detect-package-manager.outputs.manager }}
56 | - name: Setup Pages
57 | uses: actions/configure-pages@v3
58 | with:
59 | # Automatically inject basePath in your Next.js configuration file and disable
60 | # server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
61 | #
62 | # You may remove this line if you want to manage the configuration yourself.
63 | static_site_generator: next
64 | - name: Restore cache
65 | uses: actions/cache@v3
66 | with:
67 | path: |
68 | .next/cache
69 | # Generate a new cache whenever packages or source files change.
70 | key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json', '**/yarn.lock') }}-${{ hashFiles('**.[jt]s', '**.[jt]sx') }}
71 | # If source files changed but packages didn't, rebuild from a prior cache.
72 | restore-keys: |
73 | ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json', '**/yarn.lock') }}-
74 | - name: Install dependencies
75 | run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
76 | - name: Build with Next.js
77 | run: ${{ steps.detect-package-manager.outputs.runner }} next build
78 | - name: Static HTML export with Next.js
79 | run: ${{ steps.detect-package-manager.outputs.runner }} next export
80 | - name: Upload artifact
81 | uses: actions/upload-pages-artifact@v1
82 | with:
83 | path: ./out
84 |
85 | # Deployment job
86 | deploy:
87 | environment:
88 | name: github-pages
89 | url: ${{ steps.deployment.outputs.page_url }}
90 | runs-on: ubuntu-latest
91 | needs: build
92 | steps:
93 | - name: Deploy to GitHub Pages
94 | id: deployment
95 | uses: actions/deploy-pages@v2
96 |
--------------------------------------------------------------------------------
/.github/workflows/prevent_multiple_issues.yml:
--------------------------------------------------------------------------------
1 | name: Close Issue if Opener has Opened Issues
2 |
3 | on:
4 | issues:
5 | types:
6 | - opened
7 |
8 | jobs:
9 | close_issue:
10 | runs-on: ubuntu-latest
11 |
12 | steps:
13 | - name: Check if opener has multiple open issues
14 | id: check_open_issues
15 | uses: actions/github-script@v4
16 | with:
17 | github-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
18 | script: |
19 | const owner = context.repo.owner;
20 | const repo = context.repo.repo;
21 | const issueNumber = context.issue.number;
22 | const issueOpener = context.payload.issue.user.login;
23 | const previousIssuesResponse = await github.request('GET /repos/{owner}/{repo}/issues', {
24 | owner,
25 | repo,
26 | state: 'open',
27 | creator: issueOpener
28 | });
29 | const previousOpenIssues = previousIssuesResponse.data.filter(issue => issue.number !== issueNumber && !issue.pull_request);
30 | const previousOpenIssueNumbers = previousOpenIssues.map(issue => `#${issue.number}`);
31 | const openerName = context.payload.issue.user.login;
32 | const closeIssue = previousOpenIssues.length > 0;
33 | console.log(`Close issue: ${closeIssue}`);
34 | if (closeIssue) {
35 | const comment = `Hey @${openerName} , You can't have another issue before completing the previous one 😀 \n you already have the following ${previousOpenIssues.length} open issues 👀 ! :\n\n${previousOpenIssueNumbers.join('\n')}`;
36 | core.exportVariable('comment_body', comment); // Export the variable
37 | core.setOutput('close_issue', true);
38 | } else {
39 | core.exportVariable('comment_body', '');
40 | core.setOutput('close_issue', false);
41 | }
42 | - name: Close the issue and add a comment
43 | if: always() && ${{ needs.check_open_issues.outputs.close_issue }}
44 | uses: actions/github-script@v4
45 | with:
46 | github-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
47 | script: |
48 | const owner = context.repo.owner;
49 | const repo = context.repo.repo;
50 | const issueNumber = context.issue.number;
51 | const comment = process.env.comment_body; // Retrieve the exported variable
52 |
53 | if (comment.trim() === '') {
54 | console.log('Comment body is empty. Skipping comment creation.');
55 | return;
56 | }
57 | const closeComment = `${comment}`;
58 | await github.issues.createComment({
59 | owner,
60 | repo,
61 | issue_number: issueNumber,
62 | body: closeComment
63 | });
64 | await github.issues.update({
65 | owner,
66 | repo,
67 | issue_number: issueNumber,
68 | state: 'closed'
69 | });
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Logs
2 | logs
3 | *.log
4 | npm-debug.log*
5 | yarn-debug.log*
6 | yarn-error.log*
7 | lerna-debug.log*
8 |
9 | # Diagnostic reports (https://nodejs.org/api/report.html)
10 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
11 |
12 | # Runtime data
13 | pids
14 | *.pid
15 | *.seed
16 | *.pid.lock
17 |
18 | # Directory for instrumented libs generated by jscoverage/JSCover
19 | lib-cov
20 |
21 | # Coverage directory used by tools like istanbul
22 | coverage
23 | *.lcov
24 |
25 | # nyc test coverage
26 | .nyc_output
27 |
28 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
29 | .grunt
30 |
31 | # Bower dependency directory (https://bower.io/)
32 | bower_components
33 |
34 | # node-waf configuration
35 | .lock-wscript
36 |
37 | # Compiled binary addons (https://nodejs.org/api/addons.html)
38 | build/Release
39 |
40 | # Dependency directories
41 | node_modules/
42 | jspm_packages/
43 |
44 | # TypeScript v1 declaration files
45 | typings/
46 |
47 | # TypeScript cache
48 | *.tsbuildinfo
49 |
50 | # Optional npm cache directory
51 | .npm
52 |
53 | # Optional eslint cache
54 | .eslintcache
55 |
56 | # Microbundle cache
57 | .rpt2_cache/
58 | .rts2_cache_cjs/
59 | .rts2_cache_es/
60 | .rts2_cache_umd/
61 |
62 | # Optional REPL history
63 | .node_repl_history
64 |
65 | # Output of 'npm pack'
66 | *.tgz
67 |
68 | # Yarn Integrity file
69 | .yarn-integrity
70 |
71 | # dotenv environment variables file
72 | .env
73 | .env.test
74 | .env.local
75 |
76 | # parcel-bundler cache (https://parceljs.org/)
77 | .cache
78 |
79 | # Next.js build output
80 | .next
81 |
82 | # Nuxt.js build / generate output
83 | .nuxt
84 | dist
85 |
86 | # Gatsby files
87 | .cache/
88 | # Comment in the public line in if your project uses Gatsby and *not* Next.js
89 | # https://nextjs.org/blog/next-9-1#public-directory-support
90 | # public
91 |
92 | # vuepress build output
93 | .vuepress/dist
94 |
95 | # Serverless directories
96 | .serverless/
97 |
98 | # FuseBox cache
99 | .fusebox/
100 |
101 | # DynamoDB Local files
102 | .dynamodb/
103 |
104 | # TernJS port file
105 | .tern-port
106 |
107 | # package-lock.json
108 | package-lock.json
--------------------------------------------------------------------------------
/.husky/commit-msg:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env sh
2 | . "$(dirname -- "$0")/_/husky.sh"
3 |
4 | npx --no -- commitlint --edit "$1"
5 |
--------------------------------------------------------------------------------
/.husky/pre-commit:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env sh
2 | . "$(dirname -- "$0")/_/husky.sh"
3 |
4 | npm run lint
5 | npm run build
6 |
--------------------------------------------------------------------------------
/.npmrc:
--------------------------------------------------------------------------------
1 | engine-strict=true
2 | auto-install-peers=true
--------------------------------------------------------------------------------
/.prettierignore:
--------------------------------------------------------------------------------
1 | .yarn
2 | .next
3 | dist
4 | node_modules
--------------------------------------------------------------------------------
/.prettierrc:
--------------------------------------------------------------------------------
1 | {
2 | "trailingComma": "es5",
3 | "tabWidth": 2,
4 | "semi": true,
5 | "singleQuote": false
6 | }
7 |
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "editor.defaultFormatter": "esbenp.prettier-vscode",
3 | "editor.formatOnSave": true,
4 | "editor.codeActionsOnSave": {
5 | "source.fixAll": true,
6 | "source.organizeImports": true
7 | },
8 | "[javascriptreact]": {
9 | "editor.defaultFormatter": "vscode.typescript-language-features"
10 | }
11 | }
--------------------------------------------------------------------------------
/CNAME:
--------------------------------------------------------------------------------
1 | https://devsintech.co
2 |
--------------------------------------------------------------------------------
/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, caste, color, religion, or sexual
10 | identity 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 overall
26 | community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | - The use of sexualized language or imagery, and sexual attention or advances of
31 | 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 address,
35 | 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 behavior and will take appropriate and fair corrective action in
43 | response to any behavior 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 behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | support@devsintech.co.
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 of
86 | 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 permanent
93 | 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 the
113 | community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.1, available at
119 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120 |
121 | Community Impact Guidelines were inspired by
122 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123 |
124 | For answers to common questions about this code of conduct, see the FAQ at
125 | [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126 | [https://www.contributor-covenant.org/translations][translations].
127 |
128 | [homepage]: https://www.contributor-covenant.org
129 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130 | [Mozilla CoC]: https://github.com/mozilla/diversity
131 | [FAQ]: https://www.contributor-covenant.org/faq
132 | [translations]: https://www.contributor-covenant.org/translations
133 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to DevsInTech
2 |
3 | Welcome to **_DevsInTech_**✨, and thank you for your interest in contributing! After reading this documentation you'll be able to contribute efficiently to our project. **Tip:** Use the Table of Contents to navigate through the document quickly.
4 |
5 | ## Table Of Contents
6 |
7 | - [Resources for new contributors](#resources-for-new-contributors)
8 | - [How to get started](#how-to-get-started)
9 | - [Using the Command Line](#using-the-command-line)
10 | - [Using GitHub Desktop](#using-github-desktop)
11 | - [How to set up your Development Environment](#how-to-set-up-your-development-environment)
12 | - [How to Contribute](#how-to-contribute)
13 | - [How to Raise an Issue](#how-to-raise-an-issue)
14 | - [How to report a bug](#how-to-report-a-bug)
15 | - [How to submit a Documentation Issue/Update](#how-to-submit-a-documentation-issueupdate)
16 | - [How to make a Feature Request](#how-to-make-a-feature-request)
17 | - [How to make a style change](#how-to-make-a-style-change)
18 | - [How to Solve an Issue](#how-to-solve-an-issue)
19 | - [How to Submit Pull Requests](#how-to-submit-pull-requests)
20 | - [Using Command Line for Pull Requests](#using-command-line-for-pull-requests)
21 | - [Using GitHub Desktop for Pull Requests](#using-github-desktop-for-pull-requests)
22 | - [Code of Conduct](#code-of-conduct)
23 | - [Community Guidelines](#community-guidelines)
24 | - [Licensing](#licensing)
25 |
26 | ## Resources for new contributors
27 |
28 | Are you new to open source? or to open source contributions in general? Well, you came to the right place: here are some resources to help you get started contributing to open source.
29 |
30 | - [Learn Git and GitHub from scratch](https://youtu.be/apGV9Kg7ics) - This tutorial explains Git and GitHub for version control and collaborative coding.
31 | - [Complete Guide to Open Source - How to Contribute](https://youtu.be/yzeVMecydCE) - Learn about how to find projects to contribute to, how to make issues and PRs, and more.
32 | - [Learn Git Branching](https://learngitbranching.js.org/) - This website provides an interactive platform for learning and practicing Git commands and branching strategies.
33 | - [GitHub Training Kit](https://training.github.com/) - It contains cheatsheets and training manuals in multiple languages
34 | - [Git and GitHub for Beginners - Crash Course](https://youtu.be/RGOj5yH7evk) - This tutorial explains users how to effectively utilize Git version control within the Visual Studio Code editor
35 | - [GitHub Documentation](https://docs.github.com/en) - Contains essential guides for mastering GitHub's features
36 |
37 | ## How to get started
38 |
39 | Before making any changes to this repository, please take your time to go through our project and become familiar with our vision for it. After that, discuss your proposed modifications to improve our project with the repository owners and mentors. Feel free to use issues, email, or any other convenient method of communication to initiate the discussion.
40 |
41 | It's worth noting that we have a [Code of Conduct](https://github.com/TanmayAdithya/DevsInTech/blob/main/CODE_OF_CONDUCT.md) in place, and we kindly ask that you follow it when engaging with the project. We appreciate your cooperation and respectful interactions.
42 |
43 | ## What are the tools needed to contribute to this project
44 |
45 | Before you start, you must install the necessary tools mentioned below onto your device.
46 |
47 | [](https://nodejs.org/en/download/) [](https://git-scm.com/downloads) [](https://pnpm.io/)
48 |
49 | ## How to set up your Development Environment
50 |
51 | ##### Using the **Command Line**
52 |
53 | 1. Fork the repo.
54 | 
55 |
56 | 2. Clone the Forked Repository to your local machine.
57 |
58 | ```bash
59 | git clone https://github.com/YOUR_USER_NAME/DevsInTech.git
60 | ```
61 |
62 | 3. Change the working directory.
63 | ```bash
64 | cd DevsInTech
65 | ```
66 | 4. Install all dependencies.
67 | ```bash
68 | pnpm i
69 | ```
70 | 5. Start the application.
71 | ```bash
72 | pnpm dev
73 | ```
74 | 6. Visit [http://localhost:3000](http://localhost:3000) to view the application
75 |
76 | ##### Using **GitHub Desktop**
77 |
78 | 1. Fork the repo.
79 |
80 | 
81 |
82 | 2. In the forked repository click **Open with GitHub Desktop** (make sure to download GitHub Desktop [here](https://desktop.github.com/))
83 |
84 | 
85 |
86 | 3. Once **GitHub Desktop** opens up, make sure "**To contribute to the parent project**" option is selected and then click on **Continue**
87 |
88 | 
89 |
90 | 4. Finally, open the project in your preferred code editor. (**Warning:** To contribute to the project, all code and documentation modifications should be committed to a separate branch rather than **main/master**.)
91 |
92 | 
93 |
94 | ## How To Contribute
95 |
96 | Your contributions, whether code-related or not, are highly valued and appreciated. Every contribution, no matter how small, helps make the project better. Outlined below are several ways you can contribute to the project.
97 |
98 | ### What are Github Issues
99 |
100 | ---
101 |
102 | GitHub issues are a way to track and manage tasks, bugs, and discussions in a project. You can find the issues tab within a GitHub repository, usually located in the navigation menu at the top of the repository page.
103 |
104 | [](https://postimg.cc/zbNmXGK6)
105 |
106 | ### How to Raise an Issue
107 |
108 | ---
109 |
110 | _Raising an issue_ involves creating a new entry in the repository's issue tracker to report problems, suggest improvements, or start discussions, facilitating collaboration and issue resolution. **Note:** Always look for existing issues that are similar to the one you want to raise. If you find any, please do not raise the same issue again; otherwise, you may continue to raise your issue.
111 |
112 | You can raise an issue by visiting the issues page and clicking the green **New issue** button.
113 |
114 | [](https://postimg.cc/R6wCV0hn)
115 |
116 | By choosing the correct issue type, such as bug report, feature request, documentation update, or any other types of issues, you provide clarity and help streamline the issue management process for project maintainers and other contributors.
117 |
118 | [](https://postimg.cc/k6Wjj0Ym)
119 |
120 | ### How to report a bug
121 |
122 | ---
123 |
124 | When reporting bugs on GitHub, it is important to include the following information:
125 |
126 | - Steps to reproduce the bug.
127 | - Error messages encountered, if any.
128 | - Screenshots or visual examples illustrating the issue.
129 | - Any relevant code snippets or configuration settings.
130 | - Details about the environment (operating system, browser, etc.).
131 | - Any specific inputs or conditions that trigger the bug.
132 | - Additional observations or context that may be helpful in understanding the problem.
133 |
134 | This helps expedite the identification and resolution of the bug.
135 |
136 | ### How to submit a Documentation Issue/Update
137 |
138 | ---
139 |
140 | When reporting a documentation issue or update, it is important to provide clear details and suggestions for improvement. Here are the key points to include:
141 |
142 | - Clearly describe the problem or issue with the documentation.
143 | - Identify the specific section or page of the documentation where the problem exists.
144 | - Suggest specific improvements, corrections, or additions to address the issue.
145 | - Provide examples or code snippets that can help illustrate the problem or proposed changes.
146 | - Mention any confusion or misunderstandings caused by the current documentation.
147 | - Offer any additional context or information that can assist in resolving the issue.
148 |
149 | ### How to make a Feature Request
150 |
151 | ---
152 |
153 | When submitting a feature request, it is important to provide clear details and suggestions to help project maintainers and contributors understand and evaluate your request. Here are the key points to include:
154 |
155 | - Clearly describe the feature you are requesting, including its purpose and the problem it aims to solve.
156 | - Explain the potential benefits and impact of implementing the requested feature.
157 | - Consider including any relevant examples, code snippets, or mock-ups to illustrate your request.
158 | - Explain how the requested feature aligns with the goals and scope of the project.
159 |
160 | ### How to make a style change
161 |
162 | ---
163 |
164 | When suggesting a style change on GitHub, it is important to provide clear details and explanations to help project maintainers and contributors understand the proposed change. Here are the key points to include as bullet points:
165 |
166 | - Clearly describe the specific aspect of the project's style that you would like to change.
167 | - Explain the rationale behind the suggested style change and why it would be beneficial.
168 | - Provide specific examples or comparisons to illustrate the current style and the desired style.
169 | - Offer any additional context or information that can assist in evaluating and implementing the style change.
170 |
171 | **Note:** If the issue you wish to raise does not fit into one of these categories, create a blank issue.
172 |
173 | ### How to solve an Issue
174 |
175 | ---
176 |
177 | If you'd like to solve an issue, you can browse our list of open issues in the repository or on our issue tracker. Using relevant labels, you can identify issues which you are capable of resolving. Some of these labels are listed below:
178 |
179 | [`GSSoC23`](https://github.com/devs-in-tech/DevsInTech/labels/GSSoC23) - This label is assigned to those who want to work on an issue under GSSoC23
180 |
181 | [`Level 1`](https://github.com/devs-in-tech/DevsInTech/labels/Level%201) - 10 Points (Docs/Minor bugs)
182 |
183 | [`Level 2`](https://github.com/devs-in-tech/DevsInTech/labels/Level%202) - 25 Points (Enhancement of Exisiting feature)
184 |
185 | [`Level 3`](https://github.com/devs-in-tech/DevsInTech/labels/Level%203) - 45 Points (Refactoring/adding functionalities)
186 |
187 | [`question`](https://github.com/devs-in-tech/DevsInTech/labels/question) - Further information is requested
188 |
189 | [`under review`](https://github.com/devs-in-tech/DevsInTech/labels/under%20review) - PR is under review by maintainers.
190 |
191 | [`bug`](https://github.com/devs-in-tech/DevsInTech/labels/bug) - Something isn't working
192 |
193 | [`documentation`](https://github.com/devs-in-tech/DevsInTech/labels/documentation) - Improvements or additions to documentation
194 |
195 | [`duplicate`](https://github.com/thekavikumar/love-simple-ui/labels/duplicate) - This issue or pull request already exists
196 |
197 | [`enhancement`](https://github.com/thekavikumar/love-simple-ui/labels/enhancement) - New feature or request
198 |
199 | [`good first issue`](https://github.com/thekavikumar/love-simple-ui/labels/good%20first%20issue): Good for new contributors
200 |
201 | [`help wanted`](https://github.com/thekavikumar/love-simple-ui/labels/help%20wanted) - Extra attention is needed
202 |
203 | [`invalid`](https://github.com/thekavikumar/love-simple-ui/labels/invalid) - This doesn't seem right
204 |
205 | [`wontfix`](https://github.com/thekavikumar/love-simple-ui/labels/wontfix) - This will not be worked on
206 |
207 | If the issue is unassigned and you are interested in working on it, comment on the issue expressing your intention to contribute and ask to be assigned. Alternatively, if self-assignment is allowed, you can assign yourself to the issue. Discuss your approach with maintainers and contributors to align efforts and receive feedback.
208 |
209 | ## How to Submit Pull Requests
210 |
211 | Before you create a pull request, please take a moment to review the guidelines outlined below. Following these guidelines will help ensure a smooth and efficient collaboration process.
212 |
213 | ### Format for Pull Requests
214 |
215 | Make sure to commit following the Conventional Commits Standards. Your commit message should follow the pattern: `[optional scope]: `
216 |
217 | `type` refers to :
218 |
219 | - **feat**: A new feature
220 | - **fix**: A bug fix
221 | - **refactor**: Code refactoring
222 | - **test**: Additions or modifications to test cases
223 | - **docs**: README, or anything related to documentation
224 | - **chore**: Regular code maintenance
225 |
226 | `scope` (optional) refers to the section of the codebase you're working on _(eg. api, frontend, backend)_
227 |
228 | `description` : A short summary providing additional contextual information about the code changes.
229 |
230 | Read more about [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
231 |
232 | ### Using Command Line for Pull Requests
233 |
234 | - If you have already forked the project, update your copy before working.
235 |
236 | ```bash
237 | git remote update
238 | git checkout
239 | git rebase upstream/
240 |
241 | ```
242 |
243 | ⚠️ **Warning:** Avoid commting changes in the Main Branch ⚠️
244 |
245 | - Create a new branch for your changes:
246 | **Note:** Creating a new branch allows for isolated development and avoids merge conflicts while making PRs
247 |
248 | ```bash
249 | git checkout -b my-branch
250 | #Utilize the branch name to specify the type of issue you are addressing, whether it's a feature, bug fix, or enhancement.
251 |
252 | ```
253 |
254 | - Commit and push your changes to your forked repository:
255 | **Note:** A PR should have only one commit. Multiple commits should be squashed. Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should be more descriptive.
256 | - Make sure all of your commits are atomic (one feature per commit).
257 |
258 | ```bash
259 | git add .
260 | git commit -m "Add my changes"
261 | git push origin my-branch
262 |
263 | ```
264 |
265 | - Go to your repository in browser and click on compare and pull requests. Then add a title and description to your pull request that explains your contribution.
266 | 
267 |
268 | ### Using GitHub Desktop for Pull Requests
269 |
270 | - Create a new branch for your changes:
271 | [](https://postimg.cc/4mcM7Bb0)
272 | - Open your external code editor and connect to the repository. When you're through with your changes, commit and push them to your forked repository.:
273 | **Note:** Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should be more descriptive.
274 | 
275 | - Click on **Push origin** or press `Ctrl`+`P` or `⌘`+`P` to push your commits to the branch of your repository on Github. Learn more GitHub Desktop keyboard shortcuts [here](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/overview/github-desktop-keyboard-shortcuts).
276 | 
277 | - Go to your repository in browser and click on compare and pull requests. Then add a title and description to your pull request that explains your contribution or press `Ctrl` + `R` or `⌘` + `R` on the keyboard in GitHub Desktop.
278 | 
279 |
280 | ### Best Practices for Creating a Pull Request (PR):
281 |
282 | - **Clear and Descriptive Title:** Provide a concise, descriptive title for your PR.
283 | - **Detailed Description:** Include a thorough description of your changes.
284 | - List specific changes made in a clear and concise manner. Mention any major code modifications, added functionality, or removed features.
285 | - Create a checklist to help maintainers review the changes more effectively.
286 | - Include screenshots or GIFs showcasing visual changes or new features.
287 | - Mention any additional information or considerations that might be relevant.
288 | - Be responsive to any feedback or change requests during the review process.
289 |
290 | **Note:** [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop. Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)!
291 |
292 | ## Code of Conduct
293 |
294 | By participating and contributing to this project, you agree to adhere to [this](https://github.com/devs-in-tech/DevsInTech/blob/main/CODE_OF_CONDUCT.md) Code of Conduct throughout your involvement. We appreciate your cooperation in fostering a positive and inclusive community for all.
295 |
296 | ## Community Guidelines
297 |
298 | Join our [community chat on discord](https://discord.com/channels/1099745007172329592/1109164707241271368) to engage with other contributors and maintainers. Feel free to ask questions or seek clarification on any aspects of the project.
299 |
300 | ## Licensing
301 |
302 | By contributing to this project, you agree that your contributions will be licensed under our [project's license](https://github.com/devs-in-tech/DevsInTech/blob/main/LICENSE).
303 |
--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
1 | # Using latest Node.js base image
2 | FROM node:18
3 |
4 | # Set the working directory in the container
5 | WORKDIR /usr/src/app
6 |
7 | # Copy package.json and package-lock.json
8 | COPY package*.json ./
9 |
10 | # Install app dependencies
11 | RUN npm install
12 | # If you are building your code for production
13 | # RUN npm ci --omit=dev
14 |
15 | # Bundle app source
16 | COPY . .
17 |
18 | # Expose the PORT
19 | EXPOSE 3000
20 |
21 | # Start the server by building the app
22 | CMD [ "npm", "start" ]
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2022 OpenSourceHub
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 | # DevsInTech 🚀
2 |
3 |
13 | Welcome to DevsInTech, an all inclusive community where developers come to learn, grow, and create together. Whether you're a beginner or an experienced developer, you'll find a place here to connect, collaborate, and build new skills. With weekly coffee chats, movie nights, expert sessions, and more, we offer endless opportunities to improve your craft and connect with like-minded individuals. Join us today and become a part of a community that's all about helping you succeed.
14 |
24 | At DevsInTech, we believe in the power of community. We know that when
25 | developers come together, amazing things can happen. That is why we are
26 | dedicated to creating a space where everyone feels welcome and
27 | supported. Whether you are looking for a new job, seeking advice on a
28 | tricky coding problem, or just want to meet some new friends, DevsInTech
29 | is the place for you. Our community is open to developers of all levels
30 | and backgrounds. Whether you are a beginner just starting out on your
31 | coding journey or an experienced developer looking to learn new skills,
32 | DevsInTech is the place for you. We offer a variety of events and
33 | activities designed to help you grow your skills and connect with other
34 | like-minded individuals.
35 |
23 | >
24 | );
25 | };
26 |
27 | export default Revealingsoon;
28 |
--------------------------------------------------------------------------------
/src/components/testimonial.js:
--------------------------------------------------------------------------------
1 | import { useEffect, useState } from "react";
2 | import Header from "./header";
3 | import Image from "next/image";
4 |
5 | const testimonials = [
6 | {
7 | id: 1,
8 | name: "Aarav Patel",
9 | text: "DevsInTech's collaborative community has accelerated my learning and inspired me to tackle ambitious projects, thanks to the talented and supportive developers always ready to lend a hand.",
10 | image: "boy.png",
11 | },
12 | {
13 | id: 2,
14 | name: "Aanya Gupta",
15 | text: "Through expert sessions at DevsInTech, I've gained valuable knowledge from industry professionals, opening doors to exciting career opportunities and enhancing my personal and professional growth.",
16 | image: "girl.jpg",
17 | },
18 | {
19 | id: 3,
20 | name: "Rohan Sharma",
21 | text: "DevsInTech's code reviews have significantly improved the quality of my work, thanks to constructive feedback from experienced developers, helping me refine my coding skills and develop a more efficient style.",
22 | image: "boy.png",
23 | },
24 | {
25 | id: 4,
26 | name: "Aditi Verma",
27 | text: "DevsInTech's hackathons have fueled my problem-solving abilities and creativity, providing an exhilarating platform to collaborate with talented developers, innovate, and showcase my skills.",
28 | image: "girl.jpg",
29 | },
30 | {
31 | id: 5,
32 | name: "Aryan Desai",
33 | text: "The mentorship program at DevsInTech has transformed my development journey, with a seasoned developer guiding me, setting goals, and offering personalized support, accelerating my growth and fostering a sense of community.",
34 | image: "boy.png",
35 | },
36 | {
37 | id: 6,
38 | name: "Mike Smilga",
39 | text: "DevsInTech's inclusive and supportive community has been a breath of fresh air for me as a beginner developer. The encouragement and guidance I've received from fellow community members have boosted my confidence and helped me overcome obstacles.",
40 | image: "boy.png",
41 | },
42 | {
43 | id: 7,
44 | name: "Richard Paul",
45 | text: "As an experienced developer, DevsInTech has provided me with a platform to share my knowledge and give back to the community. The opportunity to mentor aspiring developers and contribute to the growth of others has been fulfilling and rewarding..",
46 | image: "boy.png",
47 | },
48 | ];
49 |
50 | const Testimonial = ({ testimonial }) => (
51 |
14 | Join our DevsInTech community for an array of exciting online tech events. Attend insightful webinars featuring industry experts, dive deep into practical workshops to enhance your skills, and unleash your creativity in our competitive hackathons. Engage with fellow developers, expand your network, and stay updated on cutting-edge technologies and industry trends.
15 |
14 | Join our DevsInTech community for an array of exciting online tech events. Attend insightful webinars featuring industry experts, dive deep into practical workshops to enhance your skills, and unleash your creativity in our competitive hackathons. Engage with fellow developers, expand your network, and stay updated on cutting-edge technologies and industry trends.
15 |
14 | Join our DevsInTech community for an array of exciting online tech events. Attend insightful webinars featuring industry experts, dive deep into practical workshops to enhance your skills, and unleash your creativity in our competitive hackathons. Engage with fellow developers, expand your network, and stay updated on cutting-edge technologies and industry trends.
15 |
14 | Join our DevsInTech community for an array of exciting online tech events. Attend insightful webinars featuring industry experts, dive deep into practical workshops to enhance your skills, and unleash your creativity in our competitive hackathons. Engage with fellow developers, expand your network, and stay updated on cutting-edge technologies and industry trends.
15 |
16 | Join our DevsInTech community for an array of exciting online tech events. Attend insightful webinars featuring industry experts, dive deep into practical workshops to enhance your skills, and unleash your creativity in our competitive hackathons. Engage with fellow developers, expand your network, and stay updated on cutting-edge technologies and industry trends.
17 |