Best practices for organizing content and templates in a growing MODX project

Support
1

Hi everyone,

I’m currently building a website with MODX and looking for advice on keeping the project maintainable as it grows.

One of the sites I’m working on is called GeometrryDash, and it’s starting to accumulate a larger number of templates, chunks, and content resources than I originally anticipated.

At the moment everything is functioning correctly, but I’m concerned about long-term maintainability and making it easier for future contributors to understand the structure.

A few questions for experienced MODX users:

  • How do you organize templates and chunks in larger projects?

  • Do you follow a specific naming convention for resources and template variables?

  • What strategies help keep content management simple for non-technical editors?

  • Are there any common mistakes to avoid when scaling a MODX site?

I’d appreciate hearing about workflows and project structures that have worked well for others.

Thanks!

2

For a little bump, and to ask how many templates the linked site has (it looks like it would only need 1 or 2. Or 3 at most) and how you’re categorizing everything? One of the biggest mistakes I make is to not describe the chunks and where they are used. Sometimes that makes it really hard for me to figure out what I have done years later. The internal search is useful so I have been using that a lot lately to find out what the heck I did years ago.

For sidewide updates however I’ve switched to and am going to make sure I use static files for chunks and templates going forward. And make good comments/descriptions, and always use categories.