stride3d / stride3d/stride

Distribute sample templates as separate NuGet packages

Open
#240 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-GameStudio area-Samples enhancement
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

This task is part of #12

  • Build: Turn each sample into NuGet package (incl. shared packages)
  • Assets: Decide what to do with Package.Templates
  • GameStudio: list and download templates asynchronously from a NuGet source

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how samples are currently packaged and how GameStudio discovers and downloads templates from a NuGet source. Review the Package.Templates asset and the shared package layout. Done means each sample and shared package is distributed, the Package.Templates handling is decided, and GameStudio lists and downloads templates asynchronously.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
build-system, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.