Fix: Contact Us Link Reload Issue (#146)

.github/ISSUE_TEMPLATE/beginner.yml

@@ -0,0 +1,166 @@
+name: C4GT Beginner Ticket
+description: Create a new Ticket for C4GT Community
+title: "C4GT Community: Basic Details of [Your name]"
+labels: ["C4GT Community"]
+body:
+  - type: textarea
+    id: ticket-description
+    validations:
+      required: true
+    attributes:
+      label: Ticket Contents
+      value: |
+        ## Description
+        Please provide the following basic details to help us understand your background and context better.
+          - **Name:**
+          - **GitHub Username:**
+          - **LinkedIn Profile:**
+          - **College/University:**
+          _If you feel comfortable, you can also provide additional information such as your area of expertise or any specific information you'd like to share._
+
+
+  - type: textarea
+    id: ticket-goals
+    validations:
+      required: true
+    attributes:
+      label: Goals
+      description: List the goals of the feature.
+      value: |
+        - [ ] Adding your basic details
+
+  - type: textarea
+    id: ticket-implementation-details
+    validations:
+      required: true
+    attributes:
+      label: Implementation Details
+      description: List any technical details about the proposed implementation, including any specific technologies that will be used.
+      value: |
+         To implement the changes in the `Community.md` file on the GitHub repository (https://github.com/Code4GovTech/C4GT/blob/main/Community.md), follow these steps:
+          1. **Fork the Repository:**
+             - Visit the repository (https://github.com/Code4GovTech/C4GT).
+             - Click the "Fork" button in the upper right corner to create a fork of the repository in your GitHub account.
+          2. **Clone Your Fork:**
+             - Open a terminal or command prompt.
+             - Run the following command to clone your fork to your local machine:
+             ```bash
+                  git clone https://github.com/your-username/C4GT.git
+             ```
+          3. **Navigate to the Repository:**
+             - Change into the repository directory:
+             ```bash
+                 cd C4GT
+             ```
+          4. **Edit the Community.md File:**
+             - Open the `Community.md` file in a text editor. You can use any code editor or a simple text editor.
+             - Locate the existing table and replace the details with your own:
+             ```markdown
+                 <table>
+                   <tr>
+                     <td>Name</td>
+                     <td>Your Name</td>
+                   </tr>
+                   <tr>
+                     <td>GitHub</td>
+                     <td>https://github.com/your-username</td>
+                   </tr>
+                   <tr>
+                     <td>LinkedIn</td>
+                     <td>https://www.linkedin.com/in/your-linkedin</td>
+                   </tr>
+                   <tr>
+                     <td>College</td>
+                     <td>Your College/University</td>
+                   </tr>
+                 </table>
+             ```
+          5. **Save Changes:**
+             - Save the changes to the `Community.md` file.
+          6. **Commit Changes:**
+             - In the terminal, run the following commands to commit the changes:
+             ```bash
+                git add Community.md
+                git commit -m "Update my details in Community.md"
+             ```
+          7. **Push Changes to Your Fork:**
+             - Push the changes to your GitHub fork:
+             ```bash
+                git push origin main
+             ```
+          8. **Create a Pull Request:**
+             - Visit your fork on GitHub (https://github.com/your-username/C4GT).
+             - Click on the "New pull request" button.
+             - Ensure the base repository is `Code4GovTech/C4GT` and the base branch is `main`.
+             - Ensure the head repository is your fork and the compare branch is `main`.
+             - Click "Create pull request" and provide a meaningful title and description.
+             - Click "Create pull request" again to submit the pull request.
+            Your changes will now be submitted as a pull request to the original repository, and the maintainers can review and merge them.
+
+
+  - type: input
+    id: ticket-product
+    attributes:
+      label: Product Name
+      placeholder: Enter Product Name
+      value: |
+         C4GT
+    validations:
+      required: true
+
+  - type: dropdown
+    id: ticket-organisation
+    attributes:
+      label: Organisation Name
+      description: Enter Organisation Name
+      multiple: false
+      options:
+        - C4GT
+    validations:
+      required: true
+
+
+  - type: dropdown
+    id: ticket-technical-skills-required
+    attributes:
+      label: Tech Skills Needed
+      description: Select the technologies needed for this ticket (use Ctrl or Command to select multiple)
+      multiple: false
+      options:
+        - Markdown
+    validations:
+      required: true
+
+  - type: textarea
+    id: ticket-mentors
+    attributes:
+      label: Mentor(s)
+      description: Please tag relevant mentors for the ticket
+      value: |
+         @Shruti3004
+    validations:
+      required: true
+
+  - type: dropdown
+    id: ticket-complexity
+    attributes: 
+      label: Complexity
+      description: Choose a complexity describing the complexity of your ticket
+      multiple: false
+      options:
+        - Beginner
+    validations:
+      required: true
+
+  - type: dropdown
+    id: ticket-category
+    attributes: 
+      label: Category
+      description: Choose the categories that best describe your ticket
+      multiple: false
+      options:
+        - Documentation
+    validations:
+      required: true
+
+

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,54 @@
+name: 🪲 Bug Report 
+description: Report your bug by filling the information given below
+title: "[Bug]: "
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Give a brief about the bug ✍️
+      description: Enter a brief description about the bug report
+      placeholder: Please include a summary, also include relevant motivation and context. 
+      value: "Description"
+    validations:
+      required: true
+  - type: textarea
+    id: behaviors
+    attributes:
+      label: What is the expected behavior? 🤔
+      description: Enter the expected behavior of the bug
+      placeholder: Please include a summary, also include relevant motivation and context. 
+      value: "Description"
+    validations:
+      required: true
+  - type: textarea
+    id: instructions
+    attributes:
+      label: Provide step by step information to reproduce the bug 📄
+      description: Enter the description of how you plan to find the bug's solution
+      placeholder: Please include a summary, also include relevant motivation and context. 
+      value: "Description"
+    validations:
+      required: true
+  - type: dropdown
+    id: contribution
+    attributes:
+      label: Select program in which you are contributing
+      multiple: true
+      options:
+        - GSoC'25 
+        - SWoC'25
+        - Other
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [CODE OF CONDUCT]()
+      options:
+        - label: I follow [CONTRIBUTING GUIDELINE]() of this project.
+          required: true
+

.github/ISSUE_TEMPLATE/c4gt.md

@@ -0,0 +1,102 @@
+---
+name: C4GT
+about: C4GT Community Issues Template
+title: "[C4GT] Button for likes"
+labels: C4GT Community
+assignees: ''
+
+---
+
+## Description
+[Provide a brief description of the feature, including why it is needed and what it will accomplish. You can skip any of Goals, Expected Outcome, Implementation Details, Mockups / Wireframes if they are irrelevant. Please note that this section of the ticket is suggestive & you can structure it as per your prerogative.]
+
+## Goals
+- [ ] [Goal 1]
+- [ ] [Goal 2]
+- [ ] [Goal 3]
+- [ ] [Goal 4]
+- [ ] [Goal 5]
+
+## Expected Outcome
+[Describe in detail what the final product or result should look like and how it should behave.]
+
+## Acceptance Criteria
+- [ ] [Criteria 1]
+- [ ] [Criteria 2]
+- [ ] [Criteria 3]
+- [ ] [Criteria 4]
+- [ ] [Criteria 5]
+
+## Implementation Details
+[List any technical details about the proposed implementation, including any specific technologies that will be used.]
+
+## Mockups / Wireframes
+[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]
+
+---
+[Please note that the below section of the ticket ****has to be in the format as mentioned as it is key to enabling proper listing of the project.**** Please only choose the options mentioned under the headings wherever applicable.]
+
+### Product Name
+[Product Name: For eg: Beckn, Sunbird Obsrv etc]
+
+
+### Project Name
+[Project Name: Descriptive of the ticket]
+
+
+### Organization Name:
+[Organization Name]
+
+### Domain
+[Area of governance]
+
+<!-- Choose area of governance from the following list
+
+| #  | Area of governance                          |
+|----|--------------------------------------------|
+| 1  | Education                                  |
+| 2  | Healthcare                                 |
+| 3  | Public Administration                      |
+| 4  | Justice and Law Enforcement                |
+| 5  | Taxation and Revenue Management            |
+| 6  | Urban Planning and Infrastructure          |
+| 7  | Environmental Governance                   |
+| 8  | Social Welfare                             |
+| 9  | E-Governance                               |
+| 10 | Financial Governance                       |
+| 11 | Electoral Systems                          |
+| 12 | Defense and Security                       |
+| 13 | Ethics and Anti-Corruption                 |
+| 14 | Transportation                             |
+| 15 | Energy and Utilities                       |
+| 16 | Agriculture and Rural Development          |
+| 17 | Trade and Commerce                         |
+| 18 | Science and Technology                     |
+| 19 | Labor and Employment                       |
+| 20 | Culture and Tourism                        |
+| 21 | Communications and Media                   |
+| 22 | Disaster Management and Emergency Services |
+| 23 | Indigenous Governance                      |
+| 24 | Sports and Recreation                      |
+| 25 | Water Resource Management                  |
+| 26 | Housing and Urban Development              |
+| 27 | Immigration and Border Control             |
+| 28 | Land Management and Real Estate            |
+| 29 | Regulatory Agencies and Compliance         |
+| 30 | Others                                     |
+-->
+
+### Tech Skills Needed:
+[Required technical skills for the project]
+
+### Mentor(s)
+[@Mentor1] [@Mentor2] [@Mentor3]
+
+### Complexity
+Pick one of [High]/[Medium]/[Low]
+
+### Category
+Pick one or more of [CI/CD], [Integrations], [Performance Improvement], [Security], [UI/UX/Design], [Bug], [Feature], [Documentation], [Deployment], [Test], [PoC]
+
+### Sub Category
+Pick one or more of [API], [Database], [Analytics], [Refactoring], [Data Science], [Machine Learning], [Accessibility], [Internationalization], [Localization], [Frontend], [Backend], [Mobile], [SEO], [Configuration], [Deprecation], [Breaking Change], [Maintenance], [Support], [Question], [Technical Debt], [Beginner friendly], [Research], [Reproducible], [Needs Reproduction].