neiist-dev / neiist-website Goto Github PK

When you leave NEIIST website for a few minutes/hours, the auth-code expires in Fenix and presents an error in the backend. The frontend displays a loading page, however, nothing happens since the error still exists. A new code must be asked to proceed with a new login.

When directly entering a page other than the main page:

After entering the home page and returning:

Diferent sizes and colours!!!

we get a ton of emails that need to be handled by different people

some of them even belong to the same "issue" but are separated and the inbox can quickly become quite a mess

it would be nice to host a tickets system (e.g. https://medevel.com/17-ticket-system-self-hosted/) to better handle them :)

A CI would be useful for automating:

• tests (when #17 is closed)
• deployment

When loading a page, the most popular procedure is to wait for all backend data to reach the frontend and then show the page.
The data doesn't usually take a lot of time, but the wait could be avoided if we displayed all the information not dependent on it, and then place a placeholder to be substituted by the real backend data.

in the "Quem Somos" page, we should mention everyone that collaborates with NEIIST, not just the social entities

The istid length should be at least 10 since now we have ppl with ist1XXXXXX

When developing the GAC Page, the tab "Search" was not a priority.
This tab is supposed to be a more focused view on the searched users, where it shows one "large" rectangle with all the information of the people searched in the input (e.g. ist123456,ist123457,ist123458 should return three rectangles, each one with the information of the members ist123456, ist123457 and ist123458, respectively.

might mean having to use bootstrap's layout components: container, row, and col

If we try to access https://neiist.tecnico.ulisboa.pt/quemsomos we receive an error message.

To reach it, we must go through the front-page. This problem also occurs when we try to refresh the page.

right now our permissions are stored in the .env file

we should migrate that to our db and allow for current admins to configure user permissions

i'm not sure but might involve transforming some "functions" into objects in order to test them

probably a markdown type blog would be enough

Unit, smoke and E2E

Right now, members cannot check their status on the website.

We should provide a simple way for them to do so.

just a crazy idea, would be nice tho

suggestion: react-markdown

Speed Up Your React Apps With Code Splitting

We need to implement this technique to speed up NEIIST's website!

The board members of NEIIST should have access to a dashboard where they can manage:

• The roles of each user (Board Member, Collaborator, Outside person)

Collaborators who have been working with NEIIST for three or more months should have the right to vote, according to the Statutes.

Old elections, which are not active anymore, still appear in the members page for some reason.

right now user is logged out on page refresh

i'm going to stop working on this soon so i need other people to be able to understand what is going on

When running it throws an error

Every student when clicking in the "Sócios" tab, it's very easy to make him/her into a NEIIST member. However, most of them don't really know what involves being a member, their rights, and their responsibilities.

• A Button, or icon, or accordion must be added to display this information to no members.

The text is not centered on mobile

We never end up deleting any memberships or theses that might have expired.
Either modify the code or create a periodic SQL procedure to remove useless data.

"Visitar Site" in SINFO section doesn't redirect to sinfo website, instead it leads to NEIIST facebook page.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency html-react-parser to v5.1.10
• Update dependency pg to v8.11.5
• Update dependency react-multi-carousel to v2.8.5
• Update dependency natural to v6.12.0
• Update dependency @testing-library/jest-dom to v6
• Update mantine monorepo to v7 (major) (@mantine/core, @mantine/hooks)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Switch to createRoot instead of ReactDOM.render which is no longer supported in React 18

Right now membership is not renewable.

This is not correct business logic, as membership should be renewed each year.

after logging in user should see their name plus a logout button but it stopped working for some reason