Skip to content

Docs: clarify Web packaging requirements in developer-setup vs supported-platforms #711

Description

@Jastman

Forum Post: https://community.cesium.com/t/adding-webgl-specific-packaging-requirements-to-developer-setup-md/46720
Category: Cesium for Unity
Reported by: @hv_nico (community forum)
Cesium/Unity versions mentioned: Unity 6+ for Web, current docs still recommend Unity 2022.3 for developer setup

Problem

Documentation~/developer-setup.md currently reads as a general prerequisite list and still recommends Unity 2022.3 LTS, while Web support requires Unity 6+ and additional Web-specific setup documented elsewhere. This creates confusion for users trying to package for Web.

The forum report also points out that WebGL native build configuration uses -G Ninja in Source/Editor/CompileCesiumForUnityNative.cs, so tooling expectations are not obvious from contributor docs.

Proposed docs updates

  1. In developer-setup.md, explicitly scope Unity 2022.3 guidance to general contributor/editor workflows.
  2. Add a “Web packaging prerequisites” subsection that links to supported-platforms.md#web.
  3. Explicitly call out Unity 6+ for Web target builds.
  4. Add a note about Web build tooling expectations (including Ninja-related behavior and where to troubleshoot).
  5. Add cross-links between developer-setup.md and supported-platforms.md#web to avoid drift.

Source references

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

    documentationImprovements or additions to documentation

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions