Final answer:
Working outside the webroot during deployment adds a layer of security, provides better separation of application code from public content, and aligns with modern development practices. It also guides easier environment setup and version control.
Step-by-step explanation:
Working outside the webroot, also known as the document root, during deployment is often considered easier and more secure for several reasons. First, any sensitive configuration files or scripts that are kept outside of the webroot are not directly accessible via a URL, which adds an extra layer of security against unauthorized access or potential attacks. Secondly, it provides a cleaner separation between the application code and publicly accessible content, which makes maintenance and updates more manageable. Additionally, it is easier to set up different environments, such as development, testing, and production when the application is structured this way because it allows for a more controlled promotion of the code through the different stages.
Finally, many deployment tools and version control systems are designed to facilitate deployments that are structured with the webroot as just one component of the entire application. This aligns with modern best practices in application development and deployment strategies.