When starting a new project and utilizing Yeoman, the process becomes tailored to the specific tool being used. With Yeoman, one must create a directory, navigate into it, and execute yo ember. Additionally, running npm install -g generator-ember (a one-time installation of a node package globally) is necessary to install the generators for Ember that are required by Yeoman to run commands such as yo ember via the command line in conjunction with Ember.
If opting for a tool like ember-cli from , the process of creating a new project varies slightly with two options available. The first involves simply executing ember new <appname> in the command line, resulting in the creation of a new folder bearing the specified 'appname'. The second method mirrors Yeoman's approach, necessitating the creation of a new directory, navigation into said directory, and running ember init via the command line.
Both Yeoman and ember-cli take care of file installation and establish a structured folder format. These files and folders are commonly referred to as boilerplate components, serving essential functions within the project framework. While inspecting a Rails project may reveal an abundance of boilerplate elements, each serves a purpose in supporting tasks such as build solutions, dependency installations, testing procedures, and CSS compilation. Despite variances in underlying mechanisms and functionalities, both Ember-cli and Yeoman ultimately aim to streamline tooling for constructing client-side applications.
For simple app creations, following resources like can be sufficient. However, as the application expands, adopting a well-defined file structure and organizational layout proves advantageous.
May this information prove beneficial to your endeavors, and may your journey with learning ember be enjoyable. Best of luck!