New Category Request

Abierto
  • ¿Algo no está bien?
#8,117 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
frontend, web-dev

Línea de trabajo

Start by reading the repository’s website entry points and how existing project categories, filters, and project pages are implemented. The issue proposes a new category with upload, discovery filters, compatibility details, and installation instructions, but does not identify files or define the scope for those pieces. Done would require an agreed design and a working category flow across the website.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Please confirm the following.
What parts of Modrinth is your feature request related too?

Modrinth.com website

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

Currently, there is no dedicated category for sharing plugin configurations. Server owners and developers often need to search through different websites, forums, or Discord communities to find useful configurations for their plugins.

Having a centralized place to share and discover configurations would make it easier for users to find what they need, save time, and learn from other members of the community.

Describe the solution you'd like

I would like to suggest adding an eighth category called Plugin Configs to the website, alongside the existing categories: Mods, Resource Packs, Data Packs, Shaders, Modpacks, Plugins, and Servers.

This category would allow users to upload, share, and download configurations for various plugins, making it easier for server owners and developers to customize and manage their servers.

To improve discoverability, I suggest adding filters for:

Game Version — Supported Minecraft versions.
Server Software — Paper, Spigot, Purpur, and other supported software.
Plugin — The specific plugin the configuration is designed for.
Color — Color schemes or themes, where applicable.
Language — The language used in the configuration.
Other relevant filters — Additional options to help users find compatible configurations.

Ideally, each configuration could have its own page with a description, compatibility information, and installation instructions.

Describe alternatives you've considered

One alternative would be to share plugin configurations under the existing Plugins category. However, plugin downloads and plugin configurations serve different purposes, and combining them could make it harder for users to find what they are looking for.

Another option would be to continue sharing configurations through external websites, forums, or Discord servers, but this would leave the content scattered across multiple platforms.

A dedicated Plugin Configs category would provide a more organized and convenient solution.

Additional context

This feature could benefit both new and experienced Minecraft server owners by making it easier to discover useful configurations, share custom setups, and learn from the community.

It could also encourage more community contributions by giving creators a dedicated place to publish their configurations and help others improve their servers.

Overall, I believe this would be a useful addition to the website and a natural extension of the existing Plugins category.

Lenguaje dominante
Rust
Estrellas
2.5k
Forks
663
Merge medio
2 d 11 h
PR fusionados (30 d)
122

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modrinth/code

Todos los issues de modrinth/code

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.