As of now, the main plugin is gatsby-plugin-styled-components & styled-components babel-plugin-styled-components
This will most likely solve the issue of CSS loading late. Rest, up to you @riteshsp2000 to add the necessary plugins.

• Move Taskade, Voiceflow to Delta
• Move Linode, Stickermule to Gamma
• Add DO in Beta
• Add Sawo in Authentication partner

1. Hero Section.

• In the content part, add the updated graphic for dates.
• Arrange the content as per the design
• Don't update the colors as of now, discussion for that is in process.

2. Join us Section.

• A new section is created for judges, mentors and sponsors.
• Use grid to make the section responsive.
• For the mobile version, hide the sponsor us card.

Links for the graphics.

• Join us: https://res.cloudinary.com/dscnitrourkela/image/upload/project-oregano/assets/qt8zgt5yhmsdhqo5qux7.gif
• Sponsor us star: https://res.cloudinary.com/dscnitrourkela/image/upload/project-oregano/assets/e6rksskam1zgn2paopha.png
• Hero section(dates): https://res.cloudinary.com/dscnitrourkela/image/upload/project-oregano/assets/xoptbvvefk1jrkb5pjnp.png

We've to add navItems for the respective sections once these (#121 #122 #118 #116) PRs are merged.

What new navItems are to be introduced?

• Prizes
• Schedule
• Speakers
• Partners(not sure, wait for confirmation)
• Team(to be added after the team profile component is made)

Is your feature request related to a problem? Please describe.

Issue forms is a new way of making issues in GitHub. IMO, we should use them here, too.

Describe the solution you'd like

Convert issue templates into all issue forms.

Additional context

I can work on this if wanted. Please let me know! 🙂

Describe the bug
Spacing and Alignment issues. Following is a list of all the alignment issues on the website.

1. Tracks section. The headings of all the tracks are not properly aligned. There is an extra margin on some cards.
2. Section Heading. The heading and description of all the sections are not aligned correctly. All are out of sync. Ideally, a separate common component should be created since it's the same for all the sections.
3. The buttons used in all sections should have the same styling. Ideally, a common component is to be created. Make the background of the button the background on which it is, add a white border to the button. When hovered on the button, the button background should change to white and the text colour to dark grey.

To Reproduce
Steps to reproduce the behavior:
Checkout preview

When someone clicks a FAQ, we should scroll down to the answer blob so as to ensure that the person sees where the answer is being displayed. High chances that the person won't be able to know where the answer is being displayed.

This will be a permanent issue. We will add the sponsor names in a comment, the assigned person will add the respective sponsor to the website.

DO NOT CLOSE THIS ISSUE

comment format

1. Sponsor Display Name
2. Serial Number
3. Sponsor Logo required format ( @ORKO06 will add the Cloudinary link)
4. Redirect Link
5. Sponsor Tier

@ORKO06 comment format

1. Serial Number
2. Cloudflare link

In the WANT TO REACH OUT TO US Section.

• change the mail to [email protected]
• add a link to the image so that on clicking mail can be sent directly - mailto:[email protected]

Reference: https://www.digitalocean.com/community/tutorials/gatsbyjs-gatsby-pwa

Website Intro - https://www.notion.so/Website-Intro-Part-7cf9607b722144afa86ec0ece8b30e66
Tracks and description - https://www.notion.so/Tracks-628123671487421d9bc637ef7d3274ab
Sponsorship - https://www.notion.so/Sponsors-b54236d437344656950f2c57b253f16c
FAQ - https://www.notion.so/FAQ-9b3913525d7541a8ab5e1e12f063c24d
Be a Hacker section - https://www.notion.so/Be-a-hacker-Harsh-and-f90558ff2d77470696691dc31298451d
Footer - https://www.notion.so/Footer-74c8d399e98345bd88f89eaddc6171d1

Some parts are still in the process of change.
@riteshsp2000 and @CIPHERTron check if you guys have access to the pages

A new design has been created for the sponsors' section.

• Implement the design using css-grids.
• Make sure the entire section is responsive and the order of sponsors as per the design.
• Abstract the section as much as possible so that it is not bound to a particular layout and is easily responsive.
• size of the logos starts decreasing from the top.
• Maintain the ratio for boxes of gamma and delta sponsors.
• instead of just 2 in a row for delta, possibly have 3. the gamma box should be flexible and the number of sponsors in a row should adjust as per the width.
• For mobile view, it should be one below the other.

Is your feature request related to a problem? Please describe.

The Discord logo at the footer is the old logo. It should be the latest one.

Describe the solution you'd like

Update the Discord logo to the latest version at the footer.

Describe alternatives you've considered

None.

What would you like to share?

Even the space between the footer social icons has the cursor set as pointer

Additional information

In order to access the link to the social icons, users must click on them but here user are able to click between them too.

Would you like to work on this issue?

• Yes, I want to work on this issue!

Reference:

Preference-1: gatsby-plugin-smoothscroll

https://www.gatsbyjs.com/plugins/gatsby-plugin-smoothscroll/

Preference-2: gatsby-plugin-scroll-reveal

https://www.gatsbyjs.com/plugins/gatsby-plugin-scroll-reveal/

Preference-3: gatsby-plugin-anchor-links

https://www.gatsbyjs.com/plugins/gatsby-plugin-anchor-links/

Preference-4: react-scroll

https://www.npmjs.com/package/react-scroll
https://www.digitalocean.com/community/tutorials/how-to-implement-smooth-scrolling-in-react

Reference: https://github.com/dscnitrourkela/project-kiwi/blob/dev/pages/index.js

This section will contain three fields(i.e name, email, message) along with a send message button and it'll be positioned right to the FAQ section. Since both are different issues, so you can make the single component only and send a PR linking to this issue and there'll be another separate issue to style the FAQ and Contact Us Section.

In the typography elements like Heading1, Heading2, and others, only the normal view font sizes are mentioned. They don't have breakpoints.
Eg: Heading1 element will have a 5xl size in all the views(Desktop, iPad, mobile) but what we require is that it should be able to resize itself according to the dimensions it is currently displayed in. (basically breakpoints)

Here is the HTML snippet

<iframe class="airtable-embed" src="https://airtable.com/embed/shr3hO4GmOExTOsWA?backgroundColor=blue" frameborder="0" onmousewheel="" width="90%" height="800" style="background: transparent; border: 1px solid #ccc;"></iframe>

Link for adding all events in the personal calendar

https://airtable.com/shr3hO4GmOExTOsWA/iCal?timeZone=Asia%2FCalcutta&userLocale=en
Make sure there is a button for this i.e. adding all events.

Try doing it latest by today!

Detailed description

The logo of twitter has been changed to i want it to update it and also in mobile screen the discord logo box size in different from above box and also their is no hovering effect on the discord logo

Context

It just some minors fix which makes UI more interactive

Possible implementation

No response

Additional information

No response

Is your feature request related to a problem? Please describe.
Some people are not very much well versed with English and that sometimes become an issue while understanding the content of the website. My feature wants to solve this problem.

Describe the solution you'd like
I want to add a feature which will detect location of the user using IP address or using geolocation API . This location will help us to know about the common languages of that place and then with the help of an translation API we will give a option of 3 different language to user from which he/she can select any language and the whole content of the website will be translated into those languages. For example:- If a person is accessing the website from France then he will get 3 different language to choose from 1) English , 2) Hindi and 3) French

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
This will help users to understand the content of the website in their native language.