As a Developer who is picking up OpenPF2 for the first time, I'd like it if the way files were organized in the plugin and playground projects was more logical and consistent so that I don't get confused about where to find things and I can pick up concepts and subsystems more quickly.
Conditions of Acceptance
Content in the playground project that is generic enough to be reusable should get moved into the plugin project (likely, under "Optional" content since core mechanics would already be in the plugin under "Core").
Content should not be grouped by its type but rather its subsystem and function (e.g., rather than putting all widget blueprints for encounter screens in a folder called WidgetBlueprints or UI, an enclosing folder like UI/Encounters might make a lot more sense.
As a Developer who is picking up OpenPF2 for the first time, I'd like it if the way files were organized in the plugin and playground projects was more logical and consistent so that I don't get confused about where to find things and I can pick up concepts and subsystems more quickly.
Conditions of Acceptance
WidgetBlueprintsorUI, an enclosing folder likeUI/Encountersmight make a lot more sense.