Skip to content

3.8.5.1 Content Pipeline: Fix Unclear Categorization & Verbiage #302

Description

@Bamboy
Image

The guide categorization needs to be changed such that the old MGCB system is clearly separated and differentiated from the new system to avoid compatibility confusion.

Similar verbiage between old and new such as...

  • Content Pipeline
  • Content Builder
  • Content Builder Project
  • Monogame Content Builder (MGCB)
  • Content X

...should be changed for the same reasons, to differentiate the old and new systems so that confusion is avoided.

Personally I would pick a synonym like "Asset" instead of "Content" for this new content system.
I realize that to fully change the verbiage would require public-facing codebase refactors. But if that were to be done, doing it before 3.8.6 would be ideal.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions