Remove it as its only used to show errors which the end user doesn't care (they should be displayed in the console instead)

OR

Make something better out of it, (annoying bug currently: the popup is shown behind modals on the z axis)

Make animated textures animated in the browser using their MCMETA

Use the old script from dokucraft team for mcmeta animation

• Keep the MCMETA with the texture when fetching it from the JAR
• Display it in the council/textures page
• Allow council members to edit it (use JSON Text area from mantine)

To avoid dropping the database each time a table is deeply modified aha

People (or only admins?) can create teams of people (eg. f32.me team) that can be selected as co-authors (or author if you're part of the team) when submitting a contribution

First idea

This should be a follow up of #2 where REJECT AND BAN buttons should ask for a reason and end date (optional) before banning the user, the reason + time left are therefore displayed in the users dashboard and on the user settings page (not accessible by banned people but still accessible by admins)

• Create a table for bans
• Update the user role when banned (to BANNED)
• Add a new card in the settings/me page to show past bans (hide it if no previous bans)
• Display the reason somewhere? Maybe make the settings/me page accessible to banned people
  • If so, remove the banned badge on the navbar

New

Add a report tab in the /user page where users can reports other users for specific reason;

• Rename /settings/me to /user/me
• Force redirect to /user/me when /user/:id is the ID of the logged in user
• Create a report table to keep a trace of all reports, each report should:
  • Reference a "report reason"
  • A user to be reported
  • The report author
  • Additional context
• Create a report reasons table
  • name
  • description
• Admins accessing others users pages can accept/dismiss reports
• Admins can ban/pardon users from this tab
• User can only see pending & accepted reports

Related to #1, but each resolution must have its own repository

Old:

Instead of storing default textures to public/files/default, push them to the default-textures repo;

The repository should work like so:

• main branch for prod
• dev/{github_username} for developers (which can be deleted at anytime)

The main branch should only be pushed by a dedicated github account.
The devs branches should be pushed by local dev git config.

• Add user github credentials to .env (bot for prod, personnal for dev)
• Add branch name to be pushed to .env config

Update:

Instead of trying to sync local repositories with github's ones, just do regular backup (once a day)

• Use GitHub's actions to trigger a workflow that push all changes to their repositories (as planned previously), need #15 first though

Requirements

• #10

Because sometimes custome block/item models can help with higher resolutions

Those contributions always comes with a textures (to avoid mismatch between a model and current contribution), thus it allows the reviewer to see the changes directly in the browser

Use ThreeJS for models

Needs to find a solution to determine what textures are used on the model, maybe use the JSON model ?

1. Emit a webhook each time :

• Default textures are added
• Contributions are added, see #2
• A user is banned, see #17

2. Prerequisities

• Add support for multiple URLs per endpoint (each scenario above)
• Should support Discord Embeds format

Export (daily/weekly?) modpack/mods resource pack to curseforge?

Might be related to :

• #1
• #3

Requirements:

• #2

Description:
Textures can have multiple names across multiple mods, some mods may not use the "right" way/convention to name their textures which can lead to contributors not finding their textures when selecting the texture to their contribution.

To do:

• keep a name field, set when the texture is first added to the database
• add an aliases field (string[]), where the texture already exist in the database but uploaded again (only add the name in the aliases array iff : different from name and not already in aliases
• update contribution draft modal to allow aliases search.
• remove hash from texture name in database, filepath already have it

• Contribute page

  • Accessible for all non-banned users
  • Link in the navbar (disabled for banned people)
  • A drag and drop zone to import contributions with resolution settings & co-authors multi select
  • Once dragged-and-dropped, create draft contributions
    • For which the author as to select to which texture it originally correspond in a modal, then the author can submit the submission for review (status goes from DRAFT to PENDING)
    • After selecting the texture, the user can look for others contributions of that texture and their up/down votes count.
    • The author can also edit co-authors & resolution on the draft modal.
  • A zone that shows all PENDING / ACCEPTED / REJECTED contributions, the author can still edit the contribution authors but nothing else. Making so switch the contribution status back to PENDING. reported
  • A zone that shows all contributions where the user is mentionned as a co-author; he (the user) can decide to be removed from the co-authors of each contribution

• Council page for reviewing contributions (and for other stuff later?)

  • A zone showing which contributions the counselor has to vote for.
  • A zone showing which contributions the counselor has voted but their voting period isn't finished.
  • A report button for each contribution to report abuse reported

• Remove conventional commits mention and mention how commits should be written instead
• Add info about prisma migration process, see #10
• Add .env settings related to #1

They were made in this order:

Moon (when light, to announce dark after)
Sun (when dark to announce light after)

But it doesn't work as the auto theme is placed in between those two

/public/ dir is "updated" only when the app is built, which means uploading textures there would need a rebuild of the website (which is not something desirable)