Skip to content

proposal: documentation structure overhaul #231

@muhdfdeen

Description

@muhdfdeen

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Use case description

I'm opening this issue to propose a structural overhaul of the documentation. While reviewing the site, I noticed two main things:

  • A significant portion of the content was last updated over a year ago.
  • The scope is primarily tailored for Spigot/Paper and proxies (Velocity/BungeeCord), with no clear path for adding content for other platforms like Fabric.

Since this would be a significant change, I wanted to open this issue for discussion and feedback before starting any work on a pull request.

Looking forward to hearing your thoughts!

Proposed solution (optional)

To help bring the documentation up to date and make it more scalable for the future, I've planned out a new directory structure:

introduction/
getting-started/
installation/
server-customization/
administration-and-maintenance/
optimization/
troubleshooting/
advanced-topics/

The new server-customization/ section, for example, could be structured like so to create clear, parallel paths for different platforms:

+-- server-customization/
|   +-- index.md  # Explains the difference between plugins and mods
|   +-- bukkit-plugins/ # All Spigot/Paper plugin guides go here
|   +-- fabric-mods/ # A dedicated home for Fabric mod guides

The goals of this new structure are:

  • To create a more step-by-step flow for new/existing server admins.
  • To establish a clear path for adding guides for other platforms like Fabric.
  • To consolidate scattered information into more logical categories.

Sub-issues

Metadata

Metadata

Assignees

Labels

articleRequest for an article about a certain topic to be addedhelp wantedExtra attention is needed

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions