Top Five Tips for Mastering Trongate

Trongate's architecture lets developers build modules that are entirely self-contained – including PHP, CSS, JavaScript, images, and even nested modules.

A common mistake is spreading a feature across multiple modules instead of encapsulating it within one. This makes reusability difficult. The solution: keep modules self-contained and take time to understand nested modules. This approach pays dividends.

The engine directory contains Trongate's core files and handles routing, controllers, rendering, and security. Don't modify it. Changes can break updates, compromise stability, and make your app incompatible with community modules.

Trongate is designed to be extended through custom modules and the normal application structure, not altered at its core.

One exception: During development, you can temporarily set $debug = true in Model.php to inspect SQL queries. Just remember to set it back to false before production.

Trongate integrates smoothly with third-party libraries and resources like Packagist, CSS frameworks, and JavaScript libraries.

The framework's strength is that it doesn't depend on anything beyond PHP itself. This keeps it stable and lightweight – you choose your own dependencies.

If something's unclear, ask. The discussion forums are free and staffed by friendly developers.

There's no such thing as a stupid question. Your questions also help the community understand what documentation needs improvement.

Teaching is one of the best ways to master a skill. Share what you know – a blog post, YouTube video, tweet thread, or course.

Don't wait until you feel "ready." Start where you are. Your perspective, especially if you're new to Trongate, helps others learn.

Interested in contributing to the YouTube channel or elsewhere? Get in touch.

If something in the docs is confusing, unclear, or could be explained better, your feedback matters. Please contact us directly.

Your voice helps improve the docs for everyone.