#1 for some reason did not mention this issue 0.o

Where do you see the problem?
I have to scroll a lot in the dashboard

Suggested by: Marti

The website is still not responsive***.

We are working on this issue currently. You can expect a fully responsive website once it releases for the first time.

The image and the Dutch text in the linkboxes on the landing page on a mobile phone viewing screen overlap

Where do you see the problem?
The linkboxes have too much whitespace below link & not enough above

Also the linklist is not responsive on phone.

Do you have to do something for the problem to appear?
No

Is it an element of the website or an image/svg?
Element of the website

Implementation

• Make "keywords" key for each link
• Just make a simple algorithm (like the tag filter one) that filters out links whose "keywords"-array doesn't include any items from the "search" array (that contains all words in the search box)
• Make a good design for the searchbox
• Add all keywords to each link

Suggested by @AntoniosBarotsis

Same things as #3.

Originally posted by @dnbln in #4 (review)

This website still doesn't follow the a11y standard.

Where do you see the problem?
People might have a hard time figuring out that there are more sections in the common Dashboard

Add Checklist Guidelines as a new page.

Guidelines like this will surely help new students figure out all the stuff they need to do!

Things we need to do first

1. #18
2. #13
3. #14

Implementation progress

• Create page
• Create guides as a new JSON file
• Make page responsive and accessible

Often when I open the site and always when I switch between "Home", "To links" and "About" the sites crashes, or starts loading very slowly.

Is your feature request related to a problem? Please describe.
Links provide lots of options which may push the most used links behind

Describe the solution you'd like
One dashboard, containing all the icons to the most used websites.

More of the site place their button for changing language on the right side. It woud be easier for them if ours is there too.

When selecting either the home page or links page it is hard to see their difference so users might think that they are still on the same page, which could cause issues

How to Reproduce

Navigating to the /about page switches the website's title from RoTUer to About | RoTUer which persists even when navigating back to other parts of the website.

Possible Solutions

These lines could be removed. Alternatively, this thread might help.

This is the most minute thing but since I saw it, thought I'd mention it 👍 Nice work on the project so far!

Problem Description

There is no place for programme-specific links, but a lot of important links for students are specific to their programme.

Proposed Sollution

A page for every programme with links useful only for students in that programme. There should also be a list of all programmes in some menu, to get to each page page.

Alternatives Considered

A page for each faculty. But that's not a good idea, because faculties combine multiple programmes, so many links would be useless to other students even in the same faculty. For example, EEMCS combines Computer Science, Mathematics and Electrical Engineering.

Additional Context

An example of a website which is very useful to students in the BSc CSE programme but not others is CSHub (https://cshub.nl). Some students made this very useful website which has summaries for various courses.

There are also some interesting study associations which offer jobs, lectures, career events etc., but they are only for some programmes. For example CH (https://ch.tudelft.nl/), a study association for CS and math. But it's not for other students, not even EE students from the same faculty.

It would also be nice for the tags to be clickable (the mouse icon already changes when hovering over them so it is a bit confusing that clicking them does nothing). Clicking them should select them similarly to using the drop-down menu. Additionally, clicking the same tag twice should remove the tag filter.

Issue guidelines & scope and requirement

Link the discussion tab with the information about Issue guidelines to the README

• Upload the requirement
• Write scope

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 [...]

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

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.