Would Love More Directory Structure Examples

[GuyPaddock]

The current directory structure guidelines are on the right track, but painfully vague. I'd love a lot more examples in that section. For example, we aren't sure where best to put UI-related stuff in the folder structure prescribed. We're thinking likely Core/UI.

As another example, where should input actions go? We don't want to put them in a folder called Core/InputActions/ because section 2.6 indicates that you should not create folders specific to the type of an asset. I considered Core/Input/ so that all input-related content can go there (e.g., binding contexts, etc.) but I'd also expect that the input actions and binding contexts that go with a particular UI context would go with that context. So, perhaps, Core/UI/<Name of Screen> would be better?

[detilium]

I disagree with the proposal of placing user interface elements within the Core folder. As stated in section 2.5, this section should only be relevant to engineers, and non-engineers shouldn't have a reason to enter the folder:

"This creates a very clear "don't touch these" message for other team members. Non-engineers should have very little reason to enter the Core folder."

Considering the existing example project content structure, I propose a new subfolder within the GenericShooter project folder, simply called UserInterface. This would contain all assets types as defined in section 1.2.11. In my opinion, UI related functionality does not contain in any of the existing folders.

Example

|-- Content
    |-- GenericShooter
        |-- UserInterface

I have not thought about potential subfolders.

[detilium]

On second though, maybe the following structure would make sense:

|-- Content
    |-- GenericShooter
        |-- UserInterface
            |-- Fonts
            |-- HUD
            |-- Menus