Download and install
https://www.cocos.com/creator, download Dashboard and install it.
After completing the Dashboard installation, register an account and log in, click on the Editor interface, select the required Cocos Creator version, download and unzip it, and then you can call it through the dashboard.
You can quickly access recently opened projects through the Project tab. When you click on a specific project entry, you can open the project.
Create Hello Word project
Click New in the lower right corner to create a hello word project.
Running the project
In this way, we have created a simple project.
Project structure
Assets folder (assets)
is used to place all local resources, scripts and third-party library files in the game. Only the content in the assets directory can be displayed in the resource manager. Each file in assets will generate a .meta file with the same name after being imported into the project, which is used to store the corresponding resource configuration and index information. The .meta file needs to be submitted to the version control system. For details, see Resource Management Notes - Meta File.
Project or design source files generated by some third-party tools, such as TexturePacker's .tps files or Photoshop's .psd files, can be managed outside assets.
Build target (build)
After using Project -> Build Release in the editor's main menu to publish the project using the default release path, the editor will create a build directory under the project path and store the build projects for all target platforms.
The library
is generated after importing the resources in assets. Here, the structure of the files and the format of the resources will be processed into the form required for the final game release.
When the library is lost or damaged, just delete the entire library folder and open the project again, and the resource library will be regenerated.
Local settings (local)
The local folder contains configuration information on the project's local machine, including editor panel layout, window size, location and other information. Developers don't need to care about the content here.
Editor configuration (profiles)
The profiles folder contains editor configuration information, including build configuration information, scene configuration information, etc. for each target platform.
Extensions folder (extensions)
The extensions folder is used to place custom extensions for this project. If you need to manually install the extension, you can create this folder manually. If you need to uninstall the extension, just delete the corresponding folder in extensions.
Project settings (settings)
Save settings related to specific projects, such as related configuration information in the project settings panel, etc. If you need to synchronize project settings between different developers, please add the settings directory to version control.
Temporary folder (temp)
temp is a temporary folder used to cache some local temporary files of Cocos Creator. This folder can be deleted manually after closing Cocos Creator, and developers do not need to care about the contents.
package.json
The package.json file and the assets folder together serve as a sign to verify the legitimacy of the Cocos Creator project. Only the folder containing these two contents can be opened as a Cocos Creator project. Developers don't need to care about the content inside.
Version control
Cocos Creator will automatically generate a .gitignore file when creating a new project to exclude files that should not be submitted to the git repository. If developers use other version control systems, or need to submit projects elsewhere, they should note that they only need to submit assets, extensions, settings, package.json, or other manually added associated files.
language switch
Dashboard
Cocos Creator
