When starting a new project, what is a good practice to ensure all resources are associated with its filename?

Saving the project is a crucial step in ensuring that all resources are associated with its filename. When you save the project, it creates a file that contains all the settings, configurations, and associated resources within that file structure. This ensures that if you need to access the project later, you have everything neatly packaged together under the specified filename.

Additionally, by saving the project regularly, you minimize the risk of losing any changes or resources you have linked, as it commits all current work to the saved file. This practice is especially important in larger projects where multiple resources and components may be involved, as it helps maintain the integrity and accessibility of your data.

Documentation of the resources and compiling the project are important steps in the workflow but do not directly ensure that all resources are associated with the filename in the way that saving does. Closing and reopening the project does not inherently associate resources either; it is the saving process that concretely links the resources to the project file.