A way to generate a page without a module, and link it to the relative module.

I had my hands on Ionic CLI today, and I usually build my apps with Angular CLI. I heard Ionic CLI integrates well with the Angular CLI (or to be more accurate, using angular CLI) so I thought why not give it a try.

Usually, when I start an app, I structure it like so (in a nutshell):

- App folder contains all of the modules
- Each module (that is not a Core/Shared Module) has pages and dummy components.

I read that there's an option to generate a `page`, which is simply a component, with a `Page` suffix instead of `Component` suffix, and it generates along the way a module for the page, and lastly, it links the generated module to the app routing.

IMO (and people are free to argue about it), the `generate page` does much more than just creating a new page, and that limits me to build my app with my own structure. I might have 1 module with multiple pages (e.g AuthModule with login, register, and a profile page).

So my alternative is to use the traditional way by creating a new `component` and not a `page`. But then, to keep the style guide of Ionic, I would like to have a `Page` suffix and not a `Component` suffix. Plus, I would like to link the generated component (which would be a page) to the relative module (e.g AuthModule) and not the AppModule, since I've already linked my AuthModule to AppModule.

Start by comparing the described `generate page` and `generate component` commands in the Angular/Ionic CLI workflow, focusing on how each creates a page and associates it with a module. Done means a page can use the requested `Page` suffix and be linked to a relative existing module rather than automatically targeting `AppModule`.

索引モデルが issue の本文から書いたものです。