Refactored app.blade.php to use class_exists instead of View::exists for checking if a class exists and config values for enabling/disabling certain components.

[thejmitchener]

Refactors the app.blade.php file to improve the way we check for the existence of classes and manage component visibility based on configuration values.

Motivation for Changes

The previous implementation relied on View::exists to determine if certain components should be included. However, this approach is less efficient and less clear than directly checking if a class exists using class_exists. By using class_exists, we ensure that we are only attempting to include components that are actually available in the application, which can prevent potential errors and improve performance.

Additionally, the refactor standardizes the configuration keys used to enable or disable components, aligning them under the layouts-wrapper configuration namespace. This enhances the organization of configuration settings and makes it easier for developers to manage component visibility.

Improvements to the Project

1. Performance: By directly checking for class existence, we reduce unnecessary overhead and improve the efficiency of the view rendering process.
2. Clarity: The new checks make it clearer what components are being conditionally included based on their availability, improving code readability.
3. Consistency: Standardizing the configuration keys ensures that all related settings are grouped together, making it easier to understand and modify component behavior.

Overall, this refactor enhances the robustness of our layout file and improves maintainability, ultimately contributing to a more reliable application.