You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs_build/dev/PROJECT_INSTRUCTIONS.md
+39Lines changed: 39 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,45 @@ Future guidance:
132
132
- implementation, runtime, and tool work should now take priority over additional governance expansion unless a real gap is discovered
133
133
- governance additions should solve demonstrated operational problems rather than hypothetical future issues
134
134
135
+
## NAVIGATION, LIST, AND TOOLBOX MODEL GOVERNANCE
136
+
137
+
Navigation menus, submenus, nested submenus, and user-facing lists must be alphabetically sorted when they are presented as browseable choices.
138
+
139
+
Allowed intentional-order exceptions:
140
+
- workflow paths
141
+
- Build Path
142
+
- dependency paths
143
+
- Project Progress
144
+
- Publishing Progress
145
+
- guided creator steps
146
+
147
+
Every intentional-order exception must be documented in the PR report that introduces or preserves it.
148
+
149
+
Toolbox status values are:
150
+
- Ready
151
+
- Wireframe
152
+
- Under Construction
153
+
- Planned
154
+
- Hidden
155
+
- Deprecated
156
+
157
+
Toolbox progress foundation fields are:
158
+
-`requiredForTestable`
159
+
-`requiredForPublish`
160
+
-`requires`
161
+
-`status`
162
+
-`progressChecklist`
163
+
164
+
Progress and Build Path views remain wireframe-only until a later implementation PR explicitly introduces a declared registry/data source and runtime behavior.
165
+
166
+
Project Workspace is the next first real Toolbox rebuild target. Its contract owns:
167
+
- Project Identity
168
+
- Project Status
169
+
- Project Progress
170
+
- Publishing Progress
171
+
172
+
Do not implement Project Workspace runtime behavior, persistence, database behavior, authentication, or save/load flows before the rebuild PR explicitly scopes those capabilities.
Added governance requiring navigation menus, submenus, nested submenus, and browseable user-facing lists to sort alphabetically.
6
+
7
+
Normalized safe active surfaces:
8
+
- Header top-level navigation.
9
+
- Header Games submenu.
10
+
- Header Toolbox group order.
11
+
- Header Toolbox nested tool submenus.
12
+
- Footer link lists inside each footer group.
13
+
- Toolbox grouped view rendering.
14
+
- Learn hub cards.
15
+
- Learn hub tool links.
16
+
17
+
## Sorting Exceptions
18
+
19
+
Documented intentional-order exceptions:
20
+
- Build Path remains dependency ordered: Project Workspace, Game Design, Game Configuration, Required Tool Path, Build Game, Game Testing, Publish.
21
+
- Project Progress and Publishing Progress remain progress/workflow ordered.
22
+
- Individual Learn tool page section order remains a guided documentation sequence: Overview, Quick Start, Common Tasks, Related Documentation, Related Videos, Examples.
23
+
- Header action buttons remain CTA ordered, not treated as navigation menus.
24
+
25
+
Footer group columns keep the existing product information architecture grouping, while each footer link list inside a group is alphabetically sorted.
26
+
27
+
## Manual Test Notes
28
+
29
+
- Toolbox renders with Order, Group, Progress, and Build Path controls visible.
30
+
- Group mode shows groups alphabetically: Account, Build, Content, Create, Media, Share, Test.
31
+
- Toolbox nested submenu items sort alphabetically inside each group.
32
+
- Account, Admin, and Games menus sort alphabetically.
33
+
- Learn hub browse cards and tool links sort alphabetically.
Added the static progress foundation fields used by Toolbox wireframe views:
6
+
-`requiredForTestable`
7
+
-`requiredForPublish`
8
+
-`requires`
9
+
-`status`
10
+
-`progressChecklist`
11
+
12
+
Progress and Build Path remain wireframe-only.
13
+
14
+
## Implementation Notes
15
+
16
+
- Added `requires` support to Toolbox Progress view cards.
17
+
- Added static dependency requirements for the core flow:
18
+
- Game Design requires Project Workspace.
19
+
- Game Configuration requires Game Design.
20
+
- Build Game requires Game Configuration.
21
+
- Game Testing requires Build Game.
22
+
- Publish requires Game Testing.
23
+
- Marketplace, Community, Languages, and Cloud require Publish.
24
+
- Added `requires` fields to `toolbox/toolRegistry.js`.
25
+
- Kept the existing `tools-page-accordions.js` renderer in place.
26
+
- Did not add DB, auth, persistence, or runtime save/load behavior.
27
+
28
+
## Intentional Ordering
29
+
30
+
Build Path is intentionally dependency ordered rather than alphabetically sorted. This is allowed by the navigation/list governance exception for workflow paths, Build Path, and dependency paths.
31
+
32
+
Project Progress and Publishing Progress are intentionally progress ordered rather than alphabetically sorted.
33
+
34
+
## Manual Test Notes
35
+
36
+
- Progress view cards show `requiredForTestable`, `requiredForPublish`, and `requires`.
37
+
- Build Path still uses existing tool tiles and existing grouped path sections.
38
+
- Progress and Build Path are not represented as tool cards or extra accordion/card sections.
0 commit comments