Browse Source

Update projects.md

Stephen Tramer 3 years ago
parent
commit
0f72f76090
1 changed files with 3 additions and 1 deletions
  1. 3 1
      projects.md

+ 3 - 1
projects.md

@@ -25,4 +25,6 @@ Some notes:
 | **Project Name** | **Proposer** | **Description** | **In progress** | **Approved** | **Owner** |
 |--|--|--|--|--|--|
 | Example | @sptramer | Just an example. | :x: | :x: | :x: |
-| Lua API Reference | @FiniteStateGit | Topic: Proposed project - Lua Documentation.  Determine what steps are required to generate online documentation of the Lua API.  Determine if o3de\Assets\Editor\Translation\scriptcanvas_en_us.ts is sufficient to generate an API.  If generating API documentation is technically feasible, proceed with documenting the API on the docs site.  Scope of proposed documentation: Reflected class_name, method_name, method_parameters, parameter_type. | ✅ | :white_check_mark: | @FiniteStateGit |
+| Lua API Reference | @FiniteStateGit | Proposed project - Lua Documentation.  Determine what steps are required to generate online documentation of the Lua API.  Determine if o3de\Assets\Editor\Translation\scriptcanvas_en_us.ts is sufficient to generate an API.  If generating API documentation is technically feasible, proceed with documenting the API on the docs site.  Scope of proposed documentation: Reflected class_name, method_name, method_parameters, parameter_type. | ❌ | ✅ | @FiniteStateGit |
+| Programmer Guide reorganization | @chanmosq | We have a discoverability issue on the documentation website: Information for core developers (and others) is scattered in locations where it can be difficult to find, especially with the website search not working well. We'd like to discuss finding a good way to reorganize the content and get people interested in content architecture working together. | :x: | :x: | :x: |
+| Minimum viable documentation | @sptramer | Right now there is no amount of documentation required for a feature for O3DE to be considered "DONE". This project will work to define reasonable docs-related requirements (including requirements on API reference) that we feel feature engineers _must_ meet in order to submit a feature. | :x: | :x: | :x: |