so-sc / sosc-website

The official website for sahyadri open source community

Sahyadri OpenSource Community

Official website for Sahyadri OpenSource Community.
All contribution to this website including contents are made through Pull Requests. If you are new to Git and GitHub and don't know how to submit a Pull Request(PR), please refer our friendly guide on submitting your first pull request at gitme.js.org.

All the contents to the website is in Markdown format, Please follow the below guidelines for any contributions.
If you don't know how to write a markdown file, take quick look at GitHub's markdown guide.

Adding your profile 👦 👧

Submit a pull request by adding your profile to the src/contents/members directory.

• Create a new file with your github username and .md as extenstion. eg: haxzie.md
• In the file add the following lines by filling out the details.

---
username: YOUR_GITHUB_USERNAME
name: YOUR_FULL_NAME
designation: YOUR_DESIGNATION_IN_SOSC
email: YOUR_EMAIL_ADDRESS
linkedin: YOUR_LINKEDIN_PROFILE_URL (optional)
skills: YOUR_SKILLS (separated by comma)
---

eg:

---
username: haxzie
name: Musthaq Ahamad
designation: Community Lead
email: [email protected]
linkedin: https://www.linkedin.com/in/haxzie/
skills: Android, Design, web, Public speaking
---

Creating a new Blog Post 📝

To submit a new Blog post, create a new folder in the src/contents/blogs directory.
Name the folder with date of posting and slug eg: 2018-08-02--First-blog-post.
Add the images you want to include in yor blog inside this directory and create a markdown file with the name index.md. Add the following frontmatter details into the markdown file followed by your blog post in markdown format. And finally submit a Pull Request.

PS:

• Slug is where your blog post will be available on the website and the prefix /blog/ is required to identify it as a blog.
• Description should be written in a single line, with considerably almost 2-3 lines as viewable. Make it short and descriptive.
• Date should be in the format YYYY-mm-dd
• Your author name should be your github profile url.

---
slug: /blog/YOUR-BLOG-POST-URL (add your post title with hyphens instead of spaces, in Lowercase only)
date: 2018-08-02
author: haxzie
name: Musthaq Ahamad
title: Second blog post
tags: blog post
cover: './cover.jpg'
description: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure'
---

# Your blog post in Markdown

Creating a new Event 🚩

To submit a new event details, create a folder in the src/contents/events/ directory with the name of the event.
Create a new Markdown file with the name index.md and add any images if you want to refer in the same directory.
Follow the below format with all the details inside the markdown file and submit a Pull Request to this repository.

PS:

• Slug is where your blog post will be available on the website and the prefix /events/ is a must to identify it as an event.
• Date should be in the format YYYY-mm-dd

eg.

---
slug: /events/devhost18
name: devhost:18
date: 2018-12-02
location: Seminar Hall
cover: './cover.png'
link: REGISTRATION_LINK (leave empty if not needed)
feedback_link: LINK_TO_SUBMIT_THE_FEEDBACK (leave empty if not needed)
---

# Other event details
And descriptions in Markdown

Contributing to the Project

We welcome Pull Requests for Bug Fixes, Missing or Fixing Documentation or even a brand new feature.
Open an issue with your concern and we'll help you out in the way.
While submitting the Pull Request make sure you have added proper comments in the code. Having a proper PR message will help us review your PR fast. Please follow consistent commit message throughout development, we follow Highlight with prefix guideline for commit messages where you need add a prefix text indicating what you have made changes in the commit.
A few of the prefixes are listed below.

• FIX: Bug fix or correction
• SFIX: Security fix
• TYPO: any typo in docs or strings
• RFT: refactored code
• ADD: Added files or contents
• FEAT: implemented a new feature
• WIP: work in progress
• INIT: Initialized files to start working on.

PS: Only use the prefix before your commit followed by an understandable commit message.

Meet our Contributors 🎉

• haxzie
• rumaan
• Chaman
• Shravan
• Afroz Hussain
• Nathaniel Ryan Mathew
• DominikTrojcak
• David Brunnthaler
• Davidgorel
• Pedro Féo
• Dhanush Bangera

sosc-website's Issues

Scale first image according to width of the tab

[DISCUSSION] Create a separate page for Clubs.

We need a separate page to display all the details of clubs and campus ambassadors within SOSC.

Recruitment information

A lot of first years don't know about the procedures about joining the community and how it works, we could probably have a link or page telling people about how community works. i.e. Community part and Core Team part and how they can join.

Improve image loading

Improve image loading experience with lazy loading or medium like loading using plugins.

Update with New Community Members

Update the src/contents/members folder with new community members mardown file

Force Enable HTTPS

Add React-Helmet tags for meta details on layout templates

Use React helmet to apply meta tags based on post/event title and caption for improving SEO of the website. The files you need to update are in src/templates improve the site's social media sharing information through appropriate meta tags inside React Helmet.

Add .vscode directory to .gitignore

The .vscode sub directory in the project is to hold settings and debug Options of the VSCode editor, since we aren't using any of those options, remove it from the git cache and add the directory to .gitignore

[BUG] Feedback button link takes to registration link

When Feedback button is pressed, it takes to registration form instead of Feedback form.

Create sitemap

Generate sitemap.xml file during gatsby build.

Prevent "Register Now" / "Give feedback" button from disappearing behind footer

While scrolling down on any of the event's pages, the "Register Now" / "Give feedback" button seems to disappear behind the footer container of the webpage.
It would be much more convenient if it is made to rest at the bottom of the Event page when the scrolling limit is achieved.

Create connect page with links to all of our community channels

It'd be great to have a separate page on our website with links to all the community channel including telegram notification channel and telegram members group (we can setup a google form script to mail them the members group link).

Create a web manifest file

Create a manifest.json file

Create new layout for Member details page.

• create new layout and template
• Add option to view volunteered events
• Add ability to view blog post under user
• Prepare showcase for individual or collaborated projects
• convert to a portfolio or resume

Sort Team Designations based on Hierarchy

It would be a lot better to have the team members sorted based on the following hierarchy:

1. President
2. Vice-President
3. General Secretary
4. Heads of Respective Fields
5. Members

Remove old registration link in Cyber Security Workshop Page

@coderhawk999 @nathanielmathew If you can submit a PR removing the link from md file since it's not valid anymore. 👍

COGNIT - Cyber Security Workshop

Make each Blog/Event card fully clickable

On the Events and Blogs Page, only the text is clickable, ie, their respective cards are unclickable.
It would be a better user experience if the entire card, when clicked can redirect to its concerned content

Missing one of the cybersecurity lead in member list

Add cybersecurity lead Sushruth to the member list.

Donate Us link in the footer is broken.

Update favicon to higher quality SOSC logo

the current logo is a really low quality .ico file of the old SOSC logo,
It would be better if we had a higher quality favicon of our current SOSC logo

overflow of link to the gaps between the boxes

In the teams page, the gaps between the member boxes are clickable and redirects to one of the page.

Example gaps:

Twitter handle link

The footer area in the website could stand to have the official Twitter link of SOSC. Seeing as it's a small feature/improvement, we could assign a Hacktoberfest label to it. @coderhawk999

Page for SOSWC

A separate page for SOSWC with objectives and logo of Athena.

Warning: Each child in an array or iterator should have a unique "key" prop.

Check Console.
I guess adding unique key it is.

Page for Alumni

A page for showcasing the alumnus of SOSC core team members.

No backlink on SOSC logo to the home page in 'Events' page

[BUG] Overlapping text in events listing

Current Behaviour

The Date in the event listing cards gets overlapped when refreshing the page in Mobile devices.

Create custom layout for Event details

• Create a new layout
• Add options to view registration button
• Add options to view feedback button

Add apple touch icons

[DISCUSSION] Yearly report page

Hey, Everyone 👋
We had planned for weekly newsletters but it didn't work out as we planned 😅 we gonna have to prepare an yearly report page in the website with all the details of activities and events happened in this year. Let's keep the deadline to around mid of December, we gotta send out mails to entire college 🔥

• It should be beautiful
• Contents can be about blog posts, events and other activities we conducted
• Have to include the details of new members and the new team with their responsibilities

If multiple people are working on it we gotta divide the work by giving each of them each component to work on. But, the design comes first. Everything will follow after reviewing the design 😁 So, our design team will be involved in this and their work is put into highest priority.

Event Registration stops on the day of Event

Currently the event registration stops on the day of event and a feedback form is shown before the event starts. So people aren't able to register on the day of event before event starts.

Delete the `synergy.md` file after the event is finished

Bring that damn footer down

Make the footer stay at the end of the page.

Convert the tabs to bottom navigation on mobile devices.

Create bottom navigation with icons instead of tabs in mobile devices.

Remove the fixed top navbar for more space in small screens.

SOSC phone number update

Update the phone number in the footer.

Update the Events list

We conducted a few events last year which are not updated in src/contents/events.

The events

• Devhost 2K22
• Node-express Workshop
• Synergy 2023
• Beyond UI/UX
• Commit to Success

Event Markdown files have varible text sizes

After updating the markdown for an event, checking the preview before making a PR shows us text in varying sizes. For example:

Maybe it's a GitHub markdown issue. If it is let's update the README in the repo to reflect how to deal with these font problems.

Prevent Non-Square Club Logos from being Cut Off

On the Clubs page of mobile devices, some Club logos seem to get cut off by its parent div ( Possibly an object-fit issue? )

Update the contact number in the website

Fix inconsistent cover image in blogs page

The blog view page currently has the cover image placed inconsistently. It changes the position and size in large screen sizes. It might be a good idea to update the blog display layout to prevent this from happening.

Profile photos in Team page shrinks on mobile devices

The profile images of team members with long name or designations seems to shrink on mobile devices/smaller screens. This might be due to flex box, I think it can be solved by giving the image fixed height and width.