MonoGame/docs.monogame.github.io

Article needed for debugging the content pipeline

Open

#41 opened on Aug 6, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (85 forks)auto 404
help wanted

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

The content pipeline, while powerful can lead to frustration when trying to debug:

  • Content import errors
  • Testing new content importers
  • Testing new content processors
  • Loading content.

A separate article is needed in the new document series to clearly outline the steps needed for all supported platforms for how to best work with the content pipeline and step through code to validate projects/implementations.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.