Merge branch 'main' into main

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,39 @@
+name: Bug Report
+description: File a bug report.
+labels: ["bug"]
+title: "[Bug]: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+        Please make sure this won't be a duplicate.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: What was expected?
+      placeholder: Tell us what you expected!
+      value: "X didn't work!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output.
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: false
+  - type: textarea
+    id: more
+    attributes:
+      label: Anything you'd like to reference?
+      description: Please add any links or references to this issue that could be of help.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,31 @@
+name: Feature Request
+description: File a feature request.
+labels: ["enhancement"]
+title: "[Enhancement]: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this form!
+        Please make sure this won't a duplicate.
+  - type: checkboxes
+    attributes:
+      label: Type
+      description: | 
+        Please specify the nature of feature you're requesting.
+        If not sure, check 'others'.
+      options:
+        - label: Documentation
+          required: false
+        - label: Codebase
+        - label: UI/UX
+        - label: Others
+  - type: textarea
+    attributes:
+      label: Feature(s).
+      description: Mention what you'd like to suggest.
+      placeholder: For eg:Add a section for blogs.
+  - type: textarea
+    attributes:
+      label: Additional context.
+      description: Anything you'd like to add that'll help us?

.github/pull_request_template.md

@@ -0,0 +1,28 @@
+**Remove anything that's not been modified from this template.**
+
+
+## Checklist
+- [ ] Documentation is updated if necessary.
+- [ ] The change(s) has/have been tested locally.
+
+
+## Description
+A brief summary of the changes introduced in this pull request.
+
+
+## Related Issues
+Closes #issue-number
+
+
+## Changes Made
+- Main Change 1: Short description
+- Main Change 2: Short description
+
+
+## Notes for Reviewers
+_(unchecked code, possible bugs, found problems, breaking compatibility, etc.)_
+- [ ] Is this ready to be merged?  
+
+
+## Screenshots / Media (Optional)
+If applicable, insert images or videos demonstrating the changes.

.github/workflows/deploy-to-vps.yml

@@ -0,0 +1,30 @@
+name: Build & deploy in VPS
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Deploy using ssh
+        uses: appleboy/ssh-action@master
+        with:
+          host: ${{ secrets.HOST }}
+          username: ${{ secrets.USERNAME }}
+          key: ${{ secrets.PRIVATE_KEY }}
+          port: 22
+          script: |
+            cd ~/website
+            git pull origin main
+            yarn install
+            yarn build
+            if [ $? -ne 0 ]; then
+              echo "Build failed"
+              exit 1
+            fi
+            pm2 restart .
+2 changes: 1 addition & 1 deletion

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+This article demonstrates how you can contribute to projects under KUOSC.
+
+## How to report bugs,issues?
+If you think you have experienced and unexpected behaviour or possibly a bug.
+
+- Check if any related issue(s) is/are [already](https://github.com/kuosc2005/website/issues) open.
+- If none exist, open a [new](https://github.com/kuosc2005/website/issues/new/choose) one.
+
+### What to include in a new issue?
+
+- [Labels](https://github.com/kuosc2005/website/labels) depending on the type of issue(s)
+- Expected behaviour
+- Observed behaviour
+- Steps to reproduce
+- Include log(s) if available
+- The host environment(optional)
+
+## Have any suggestions or new ideas instead?
+
+- Create an issue and [label](https://github.com/kuosc2005/website/labels) it accordingly
+
+## Contributing to the codebase
+Contributing to this project is easy, and we welcome contributions from everyone. Here are a few guidelines to get you started:
+behavior
+
+- [Fork](https://github.com/kuosc2005/website/fork) the repository
+- Clone the repository
+- Make your changes
+- Test your changes
+- Commit your changes
+- Push your changes
+- Submit a [pull request](https://github.com/kuosc2005/website/pulls)
+
+### What to include in a pull request(PR)?
+
+- Changes made in the codebase
+- If any issues are addressed, reference it in the body
+
+### Writing Commit Messages
+
+- **Use the imperative mood**: Start with an imperative verb, such as "Fix", "Add", "Update","Change" etc.
+- **Keep it concise**: Limit the subject line to 50 characters and use the body to provide additional context if necessary.
+- **Reference related issues**: If your commit addresses a specific issue or task, reference it in the body of pull request using the issue number (eg: Resolved #69).  
+
+Example:
+```txt
+Add: blog for sfd
+Fix: avatar image distortion
+```

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023 kuosc2005
+Copyright (c) 2024 kuosc2005
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -41,8 +41,8 @@ $ GIT_USER=<Your GitHub username> yarn deploy
 
 If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.
 
-### Contributing
-
-You can contribute in this repository by forking it, creating a separate branch to do the task, making some changes, and creating pull request in this repository.
+## Contributing
+For contributions see [CONTRIBUTING.md](CONTRIBUTING.md).
 
 **Warning:** DONOT use `npm` or `pnpm` to install dependencies. Rather, just use `yarn`. Github actions will fail if you use anything other than yarn.
+

blog/2024-08-09-osm-day/index.md

@@ -0,0 +1,62 @@
+---
+slug: 2024-08-09-osm-day
+title: OSM-Day Celebration
+authors: [razzat008]
+tags: [open-source,kuosc,osm]
+---
+
+<img
+src={require('./src/img/osm-day.webp').default}
+alt="cute_president"
+height="50%" 
+width="50%"
+/>
+<hr/>
+
+On August 09, 2024; us here at Kathmandu University Open Source Community celebrated
+[OpenStreetMap](https://www.openstreetmap.org/about) day.
+
+## What is OSM?
+
+Founded by [Steve Coast](https://stevecoast.com/) in 2004, OpenStreetMap(OSM) is a collaborative, open-source mapping project with its aim being
+to a free and editable  map of the world.  
+And no, it's not same as Google Maps, while Google Maps is proprietary and focuses more on providing polished
+user interface but limited access to raw data, OSM provides full access to it's underlying geographical data.  
+Which makes it a goto choice for developers interested in customizable mapping solutions.
+
+## Why was OSM founded?
+
+Like many other open-source projects, the OSM was founded in response to the lack of liberty.  
+The project was largely motivated by the restrictive policies of national mapping agencies like the Ordnance Survey,
+which did not release their data for public use. 
+
+Peeking into its history, after the project started in 2004, the OpenStreetMap Foundation was established in 2006 to support the project's
+growth and manage its operations.  
+This nonprofit organization promotes the distribution and development of free geospatial data.
+
+Likewise, in 2007, OSM hosted its first annual conference, "State of the Map," in Manchester, further strengthened its community and outreach efforts.
+By this time, OSM had grown to over 9,000 registered users.  
+To date, OSM has millions of users around the world.
+
+## The event 
+
+Moving toward the event, the speaker for the day was [Mr.Suraj Thapa](https://github.com/suthamakes).  
+He shared his previous experiences and his ideologies toward the OSM project. In addition,
+he also shared problems that could be solved using OSM, he gave examples of: 
+Disaster and Climate Resilience, Humanitarian Mapping, etc.  
+We learned about the impact of the OSM community.
+
+We progressed toward the end of the event by sharing our experiences with OSM or open-source in general, and 
+ended the event by cutting the cake brought especially for this day.
+
+<img
+src={require('./src/img/osm-day-cake.webp').default}
+alt="mata cake khana gako"
+height="50%" 
+width="50%"
+/>
+<hr/>
+
+
+### Resoucres:
+- Slides presented on the event [here](https://docs.google.com/presentation/d/1LZEnJRs0vgzQEc_4UH6Vk5xNdngqtQsenXcKMNZtwaY).

blog/authors.yml

@@ -16,8 +16,16 @@ S-Sigdel:
   url: https://github.com/s-sigdel
   image_url: https://github.com/s-sigdel.png
 
+
 notashwinii:
   name: Ashwini Subedi
   title: KUOSC
   url: https://github.com/notashwinii
-  image_url: https://github.com/notashwinii.png
+  image_url: https://github.com/notashwinii.png
+
+razzat008:
+  name: Rajat Dahal
+  title: General Member, KUCC, KUOSC
+  url: https://github.com/razzat008
+  image_url: https://github.com/razzat008.png
+

docusaurus.config.js

@@ -166,6 +166,10 @@ const config = {
 							{
 								label: 'Facebook',
 								href: 'https://www.facebook.com/groups/kuosc'
+							},
+							{
+								label: 'Discord',
+								href: 'https://discord.gg/UG6VYVxNV2'
 							}
 						]
 					},

src/css/custom.css

@@ -91,3 +91,7 @@
 		flex-direction: column-reverse;
 	}
 }
+
+img{
+  max-width:none;
+}

src/pages/index.tsx

@@ -25,7 +25,7 @@ function HomepageHeader() {
 						Open School
 					</Link>
 					<Link className="button button--secondary button--lg" to="https://sfd.kuosc.org.np/">
-						SFD 2023
+						SFD 2024
 					</Link>
 				</div>
 			</div>

src/pages/leaderboard.module.css

@@ -311,4 +311,4 @@ td {
     border-radius: 50%;
     height: 50px;
   }
-}
+}