Include Editor API

Open
#2 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

No files or tests are named. Start by reviewing the documentation structure and identifying where the Editor API reference belongs, then determine which API material is available to document. Done means the relevant Editor API is included in the documentation and the affected pages build successfully.

Written by the indexing model from the issue text.

Description

API content p4

Until recently, the code for the editor was closed source. Now that a everything is under MIT, the editor API should be included in the documentation.

Dominant language
PowerShell
Stars
39
Forks
74
Avg merge
3h 36m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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.

More from stride3d/stride-docs

All issues in stride3d/stride-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.