Who writes and reviews PortalMine guides

Our technical content uses a transparent organizational byline rather than an invented individual author.

PortalMine Operations & Documentation Team

This byline covers contributors who maintain the PortalMine product, document dashboard workflows, review support patterns, and update server-owner guidance. Because responsibility is shared and contributor availability can change, the site does not present a fictional named expert.

Each guide states its last review date and links to the editorial policy. When a page includes a workflow diagram, it is labelled as a diagram rather than a live screenshot. When PortalMine has not run a controlled benchmark, the article does not claim benchmark results.

Review scope

  • Product steps are checked against the current public interface and documentation.
  • Technical guidance is edited for edition, version, and server-software context.
  • Repeated boilerplate is removed so each page has a distinct purpose.
  • Security-sensitive values such as credentials, tokens, and private endpoints are never published.
  • Material corrections are reflected in the page review date.

Contact and corrections

Readers can report unclear steps, outdated version information, or factual errors to support@portalmine.com. Include the page URL and the exact paragraph that needs review. General support requests should use the contact page.

Roles in the documentation workflow

Operations reviewer

Checks that PortalMine labels, server states, settings, limitations, and support steps match the current interface.

Technical source reviewer

Checks software-specific statements against official Minecraft, PaperMC, Fabric, Forge, or Microsoft documentation.

Content editor

Removes duplicate boilerplate, clarifies assumptions, adds examples, and verifies that internal links lead to useful next steps.

Correction owner

Receives reports at support@portalmine.com, reproduces the issue when possible, and records meaningful corrections.

Disclosure

PortalMine publishes documentation about its own hosting service. Calls to action are identified by context, and technical pages should not present unmeasured claims as independent benchmarks. External projects remain responsible for their own software and documentation.