Coder Social home page Coder Social logo

website's People

Contributors

dakshchan avatar daniyalb avatar dependabot[bot] avatar dev-jesse avatar ggggg avatar herschalo avatar huonggiangbui avatar jwucode avatar logonoff avatar rishav1707 avatar shubhbapna avatar

Stargazers

 avatar

website's Issues

social media buttons for the team

Is your feature request related to a problem? Please describe.
There is no way to contact the team from the website homepage.

Describe the solution you'd like
Social media links provided by each member below their avatar with appropriate entries into each team member's entry in team.json

Describe alternatives you've considered
Their usernames placed below their avatars instead?

improve home page UI

Is your feature request related to a problem? Please describe.
at the moment, the home page is very text-heavy. it would be nice if the "who are we" section was expanded to have more graphics to be more visually appealing and readable.

migrate to MUI CSS theme variables

Is your feature request related to a problem? Please describe.
We are currently using MUI ThemeProvider for dark theme which has the unfortunate side effect of a brief white flash while loading any page for dark theme users

Describe the solution you'd like
When the MUI CssVarsProvider API becomes stable, migration to it would allow for dark theme to load sooner which would significantly reduce the duration of the white flash

Cache event data

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Now, every time we load the event page, the site calls an API to get event data. But for past events, we can cache those data instead of calling API every time.

Describe the solution you'd like
A clear and concise description of what you want to happen.

We can store past events into local storage, and get data from there every time we load the event page.
Note that right now we already saved event description (fetched from another API) into local storage. We might also change the data structure too, to cache both event data and description into 1 place. Something like a hash map, key is event id, and value is event data + description.

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

Additional context
Add any other context or screenshots about the feature request here.

Move api fetching to page level

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Right now, we are fetching events' data (description and event info) in components. That might not be the best practice.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Move all API fetching to page level -- we should fetch API for specific pages, instead of components

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

Additional context
Add any other context or screenshots about the feature request here.

Note that event cards are used in both home page and events page, so you might want to consider how to reuse event data for both pages

rename Twitter to "X"

Describe the bug
Twitter is now "X". Need to change the icon for Twitter to an X.

To Reproduce

  1. Go to gdscutm.com
  2. Observe the Twitter bird flying strong

Expected behavior
There should be an X

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 11 22H2
  • Browser Edge
  • Version 115.0.1901.188 (Official build) (64-bit)

Additional context
Maybe remove the icon altogether since it isn't maintained

sever-side fetch events

Is your feature request related to a problem? Please describe.
A current issue with this page is that the events page does not work when JS is turned off, which is bad for SEO.

a solution is to use Next.js' built in server-side data fetching, which would also eliminate the need for the usage of localStorage in the client.

add pagination to events & projects page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

it is too long!

Describe the solution you'd like
A clear and concise description of what you want to happen.

pagination for both events & project page

for event page, can add filter section so user can filter by year/school term

For project page: add a "pinned" attribute for projects we want at the top of the first page.

Change GDSC workshop to use new API instead of hardcode json

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We move all slides to archive at workshop archive repo. We will call the API to get all the workshop data to display on website

Describe the solution you'd like
A clear and concise description of what you want to happen.
Call the API as described at workshop archive repo. You should use Next.js app router server-side fetching to prevent the need to cache the workshop to local storage

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

Additional context
Add any other context or screenshots about the feature request here.

categories for the FAQ

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

currently the FAQ is not categorized by tags, which may make it confusing to use.

Describe the solution you'd like
A clear and concise description of what you want to happen.

convert faq.json from an array to an object sort of like team.json, and update the faq component to include section headers

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

leaving it be and having an eventual mess

Additional context
Add any other context or screenshots about the feature request here.

[New Workshop]: Security Workshop

Category

Cybersecurity

Workshop Name

MCSS ร— GDSC: Intro to Cybersecurity Workshop

Date of Workshop

2023-03-10

Host Name

["Michael Pavle", "Ido Ben Haim", "Shrey Vakil", "Sam Chan"]

Workshop Description

In this workshop, we will be covering a broad overview of cybersecurity with a hands-on web app challenge for you to get some experience with web vulnerabilities; particularly, OS command injection. This workshop will be beginner-friendly, although if you have JavaScript experience you will better understand some of the code that we present.

Link to starter code

No response

Link to slides

https://www.slideshare.net/GDSCUofTMississauga/mcss-gdsc-intro-to-cybersecurity-workshop

Link to recording

No response

year/term categorization for the projects page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

community projects are often worked on for only one or two terms. it would be helpful to categorize and sort by those terms so that the newest projects appear first

Describe the solution you'd like
A clear and concise description of what you want to happen.

a change to the projects schema that includes an array of terms that a project has been worked on, then adding headers to the project page, where each project is categorized based on its latest maintenance term, and term when the project started

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

a single string representing the latest term a project has been worked on, but that would give less metadata for future us to use

Additional context
Add any other context or screenshots about the feature request here.

this would work also well with the pagination issue #6 as we can set page breakpoints based on the terms

support markdown for FAQ component

Is your feature request related to a problem? Please describe.
As an FAQ author, I may want to add links for some of the answers in the FAQ page, or format some of the text, however there are currently no mechanisms for that to happen

Describe the solution you'd like
I would like the FAQ to become a markdown document, similar to CSSC's implementation (although I would much prefer headings instead of pipes to delimit questions and answers, e.g.,

## Category 1
### Question 1
Answer 1

### Question 2
Answer 2

## Category 2
### Question 1
Answer 1

)

Describe alternatives you've considered

  • the answer value in the JSON file to be pared differently such that answer can parse markdown syntax

I think a md document would be more readable in the long run however there are still questions on where to place the document, whether the FAQ deserves a separate page after this change, etc

Additional context
Add any other context or screenshots about the feature request here.

Add layout to the website

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Right now, some of the pages have a similar layout (e.g. resources and events page). However, we are duplicating the code (copy-pasting around)

Describe the solution you'd like
A clear and concise description of what you want to happen.

Make layout(s), so we can reuse it among different pages

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

Additional context
Add any other context or screenshots about the feature request here.

migrate to next: image optimization

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Fix the image optimization problem, atm the images are sent uncompressed and take up lots of bandwidth

Describe the solution you'd like
A clear and concise description of what you want to happen.

One solution is to migrate from create-react-app to next.js. It will also improve page loads and SEO which is a nice bonus, especially since most of our content is static, we want to have next.js SSR

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

gatsby, create-react-app SSR plugin (sucks)

Additional context
Add any other context or screenshots about the feature request here.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.