Skip to content

Suggestions for Improving Documentation Structure and Content #394

Open
@DaHuangGoldGOOD

Description

@DaHuangGoldGOOD

Hi Stride team,

As an indie developer transitioning from Unity to Stride, I'd like to share some documentation improvement suggestions based on my onboarding experience. These adjustments could help future newcomers.

  1. Reorganize the "Distribute a Game" Section
    Current Location: Files and Folders → Distribute a Game
    Proposed Change: Move it under Get Started.
    Reason: The logical progression for new users should be:
    Install Engine → Create Project → Learn Basics → Build First Game → Test → Distribute
    The current placement under "Files and Folders" might be less intuitive for developers expecting a streamlined workflow.

  2. Missing Android Platform Documentation
    Issue: The "Platforms" section lacks dedicated guidance for Android. This is critical for mobile developers.
    Possible Solutions:
    Add an "Android" subsection under Platforms. If the documentation exists elsewhere, please move it to Platforms.

  3. Request for a "Q&A" Section
    Purpose: Centralize solutions to common issues (e.g., build errors, dependency setup). If there's new issues form Discord or other platforms, the document administrator can update the content in the Q&A section in a timely manner。

Attached is a sample Q&A document (Q&A ver0.0.1.docx) demonstrating how solutions could be formatted.

  1. Submission of an Android Build Tutorial
    Background: Many developers (especially those migrating from Unity) may not anticipate Stride's Android build prerequisites.

Attached File: [Android Tutorial.docx]Provides a step-by-step guide from environment setup to APK generation.
AND I WANT TO KEEP "FINAL WORDS", I REALLY DO! PLEASE KEEP!!

Note: Some screenshots are in Chinese. You may have to replace them with English screenshots if needed.

Finally, wish you a smooth development

Q&A ver0.0.1.docx
Android Tutorial.docx

Metadata

Metadata

Assignees

No one assigned

    Labels

    manualRelated to manual documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions