Description

Addition of separate components

The current directory structures the component in the following way:

├── components
│   ├── contributors.tsx
│   ├── header.jsx
│   ├── layout.jsx
│   └── main.jsx
├── images
│   └── icon.png
├── pages
│   ├── 404.js
│   ├── index.js
│   └── {year}.jsx
├── styles
│   └── global.css
└── types
    └── ContributorType.ts

We suggest that the components be separated into files dependent on their language

.
├── components
│   ├── javascript
│   │   ├── header.jsx
│   │   ├── layout.jsx
│   │   └── main.jsx
│   └── typescript
│       └── contributors.tsx
├── images
│   └── icon.png
├── pages
│   ├── 404.js
│   ├── index.js
│   └── {year}.jsx
├── styles
│   └── global.css
└── types
    └── ContributorType.ts

TL;DR

• [ ] Make a folder for storing TypeScript files
• [ ] Make a folder for storing JavaScript for files

Expected Behaviour

Should store components separately!

Current Behaviour

No response

Additional information

No response

New Pull Request

• :pencil: What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • [x] Addition of a contributors component
  • [x] Small integration of typescript and *.tsx
  • [x] CSS change to fix the Header alignment and design

• :pencil: What is the current behavior? (You can also link to an open issue here)

  • Has no typescript
  • A little appreciation for the people working on the project is missing

• :pencil: What is the new behavior (if this is a feature change)? Described in the first section.

• :pencil: Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) Yes, addition of Typescript. Probably a breaking change? But one for the better

Future changes planned before merge(hopefully)

• [ ] fully transition to typescript
• [ ] Change the current TS variables in content to static content on the Gatsby CMS
• [ ] Add a yearbook page
• [ ] Create components for the individual profiles
• [ ] Create modal views for the Profiles(On click)
• [ ] Add a section for other members to leave comments on profiles(dunno if this is a good idea)

:white_check_mark: Check List (Check all the applicable boxes)

• [x] I have read CONTRIBUTING.md
• [x] I have followed the CODE OF CONDUCT
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] My changes generate no new warnings
• [x] I have done git pull before adding my new changes
• [x] The title of my pull request is a short description of the requested changes.

:pencil: Other Issues :

:scroll: Screenshots (If Applicable)

Original : Updated :

New Pull Request

• :pencil: What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Added contributors addition automation to README with size being 50px x 50px overall

Making a custom workflow

Our current README doesn't update itself when a new contributor commits ! We would like to recognize all of our contributors, so we would like to add a workflow which updates readme.

Links about making a workflow:

• GitHub's Article on how to make one
• Making a custom workflow
• Events that trigger a workflow

New Pull Request

• :pencil: What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature addition
• :pencil: What is the current behavior? (You can also link to an open issue here) #42 Missing Timeline Component as proposed in design
• :pencil: What is the new behavior (if this is a feature change)? Adds a new Timeline Component
• :pencil: Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

:white_check_mark: Check List (Check all the applicable boxes)

• [x] I have read CONTRIBUTING.md
• [x] I have followed the CODE OF CONDUCT
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] My changes generate no new warnings
• [x] I have done git pull before adding my new changes
• [x] The title of my pull request is a short description of the requested changes.

:pencil: Other Issues :

• Responsitivity Issues
• Scrollbar needs to be Styled

:scroll: Screenshots (If Applicable)

Description

Designing a new landing page

Design a new minimalistic landing that would be the best fit for the site. Not too fancy, Not too dull.

Expected Behaviour

N/A

Current Behaviour

N/A

Additional information

A folder should be created in the root directory where the design will be saved in .fig files and in PNG format to get a quick glimpse of the website.

While making the design, make sure that it can be implemented smoothly with the current stack.

Description

We need to have a docs folder which will carry the necessary documentation. This will act as reference on how to get started for our upcoming contributors !

Tasks:

• [x] Add docs folder
• [x] Add a brief document about how to get started with the project

Expected Behaviour

No response

Current Behaviour

No response

Additional information

References:

• Contributing Guide
• Code of Conduct

Description

Currently, we don't store the data for our members who intend to store their record ! We would like to create a folder structure to store our users

├── data
│   └── 2021
│       └── abhijith-ganesh.json

{
  "Name": "Your Name",
  "About": "Your cute tagline",
  "Year_of_graduation": "0000",
  "Links": []
}

TL;DR Check-out the following

• [ ] Add a data directory
• [ ] Add years (of graduation) of your preference (possibly 2020, 2021, 2022, 2023...)
• [ ] Add a sample JSON sticking to the format above mentioned

Expected Behaviour

This Issue should create a directory that would help storing data of interested members!

Current Behaviour

No response

Additional information

No response

New Pull Request

• :pencil: What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Docs update (Issue template).

• :pencil: What is the current behavior? (You can also link to an open issue here)

• :pencil: What is the new behavior (if this is a feature change)?

• :pencil: Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

:white_check_mark: Check List (Check all the applicable boxes)

• [x] I have read CONTRIBUTING.md
• [x] I have followed the CODE OF CONDUCT
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [x] My changes generate no new warnings
• [x] I have done git pull before adding my new changes
• [x] The title of my pull request is a short description of the requested changes.

:pencil: Other Issues :

:scroll: Screenshots (If Applicable)

Original : Updated :

As a sub-task of the related issue, please create a pull request template according to the github documentation:

• https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
• https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates

CI/CD for application

To make deployments and integrate changes to the repository easy, we usually have GitHub Actions to help us automate and track the changes. You can find the reference Action here, for this issue we would like the contributor to add a workflow which deploys a gatsby-application to a branch names gh-pages

Description

According to Design, We need the Navbar with waves.

Expected Behaviour

No response

Current Behaviour

No response

Additional information

Linked Issue: #46

Description

Addition of NavBar

Currently, our Navbar is a minimalistic monochrome design, we would like the contributor to refer to the design mentioned in our Design folder and implement a Navbar

Expected Behaviour

No response

Current Behaviour

No response

Additional information

Similar issues #43 #42

Link to the Design

Description

Making a Hero Component

Currently our website doesn't have a central Hero Component that renders content which is mentioned in the design folder, so we need to implement the changes as mentioned. This Issue is made to track the content according to New Design

TL;DR

• [ ] Make a Typescript/JavaScript component for main page
• [ ] Add the text as mentioned in the design

Expected Behaviour

Current Behaviour

Additional information

Link to the design

Description

Implementing design

As mentioned in the design folder, one needs to impelment the timeline component using Typescript/JavaScript

Tasks:

• [ ] Make a central timeline
• [ ] Add list of years
• [ ] Add hyperlink to years , hyperlinks of the format /yearbook/<year>

The component can be scrollable, that is the div can have more than 100% width horizontally

Expected Behaviour

N/A

Current Behaviour

N/A

Additional information

Reference for TailwindCSS:

• https://flowbite.com/docs/components/timeline/
• https://tailwindcomponents.com/component/simple-vertical-timeline

Description

Addition of pages

We will be representing every year as a url routed like /year:

• [ ] Add page for a generic year

When doing so, you need to create a file in pages named /yearbook/{year.jsx}

Expected Behaviour

This should generate pages for us based on our years

Current Behaviour

There isn't a page which handles years

Additional information

None