According to the guidelines, there is no intermediate folder below the source root (here: no src/app/xy, but src/xy directly). Also note that in all examples, app.(js|css) and index.html are all on the same level (you currently have them in two different folders).

If you look at the first and the second example, the sampleapp (this generator's src folder) lives at the same level as e2e-tests, and directly includes app.js, index.html and all that stuff. Also, components is a first-level child.
The third ("more complex") example has the index.html on the same level as app.js, as well as the components folder and the other module folders.
The fourth example ("public phonegap") additionally shows an additional data-only directory outside of app.

So in my opinion, you should merge the current app folder up into src, not components down into app. To be clear, here's the layout I have in mind:

<root>/
 ├─ e2e/
 ├─ gulp/
 |
 └─ src/
     ├─ assets/
     |   └─ images/
     |       └─ ...
     ├─ components/
     |   ├─ navbar/
     |   |   └─ ...
     |   └─ ...
     ├─ main/
     |   └─ ...
     ├─ index.js
     ├─ index.css
     ├─ index.html
     ├─ vendor.css
     └─ 404.html

(Note that assets does not comply with the guidelines (neither today nor with the PR), instead the guideline says to put them into either components or a seperate directory on the root level. Personally I don't mind keeping it like it is right now.)

Now, I don't see how this structure would impede @intellix in spotting "where to look for the code" (the modules are still in their own folder, even a level higher up). Can you maybe elaborate?

App Folder Structure #272

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions