Addition of ColdBox HMVC Framework

[lmajano]

Reasons for making this change:

Adding support for the ColdBox HMVC Framework for ColdFusion (CFML)

Links to documentation supporting these rule changes:

https://coldbox.ortusbooks.com/

If this is a new template:

• Link to application or project’s homepage:

• https://www.coldbox.org

• https://github.com/coldbox/coldbox-platform

• https://community.ortussolutions.com

• https://coldbox.ortusbooks.com/

[github-actions]

This PR is stale because there have been no updates in 90 days. It will close after 180 days of inactivity. Leave a comment if you want to keep it open 😄

[lmajano]

It's stale, because the code reviewers don't review! It has ONLY been four years.

[wirecat]

We typically don't house gitignore templates for frameworks in our root directory.
How would you feel about moving this to community/Coldfusion/ColdBox.gitignore?

[wirecat]

Could you please remove this OS specific line? We encourage people to instead use global gitignore configs and have a collection of them that can be used. Please see our Global/README for more information and Global/macOS.gitignore for an example.

[lmajano]

Thanks so much for the feedback @wirecat . I updated the ignores to the latest versions.

How would you feel about moving this to community/Coldfusion/ColdBox.gitignore?
ColdBox is an MVC framework for two languages: BoxLang (www.boxlang.io) and CFML. So it would have to be for both?

With that said, you have already 36 frameworks in the root?

1. Angular - JavaScript frontend framework
2. CakePHP - PHP web framework
3. CodeIgniter - PHP web framework
4. Concrete5 - PHP CMS/framework
5. CFWheels - ColdFusion web framework
6. Drupal - PHP CMS/framework
7. ExpressionEngine - PHP CMS/framework
8. ExtJs - JavaScript framework
9. FuelPHP - PHP web framework
10. Grails - Groovy web framework
11. Jekyll - Static site generator/framework
12. Joomla - PHP CMS/framework
13. Kohana - PHP web framework
14. Laravel - PHP web framework
15. LemonStand - PHP e-commerce framework
16. Lithium - PHP web framework
17. Magento - PHP e-commerce framework
18. Nanoc - Ruby static site generator
19. Next.js - React-based web framework
20. OpenCart - PHP e-commerce framework
21. Phalcon - PHP web framework
22. PlayFramework - Scala web framework
23. Plone - Python CMS/framework
24. Prestashop - PHP e-commerce framework
25. Qooxdoo - JavaScript framework
26. Rails - Ruby web framework
27. SeamGen - Java web framework
28. SugarCRM - PHP CRM framework
29. Symfony - PHP web framework
30. SymphonyCMS - PHP CMS/framework
31. Textpattern - PHP CMS/framework
32. TurboGears2 - Python web framework
33. Typo3 - PHP CMS/framework
34. WordPress - PHP CMS/framework
35. Yii - PHP web framework
36. ZendFramework - PHP web framework

[wirecat]

@lmajano we haven't always got it right, but we're trying to uphold the standards passed down to us from previous maintainers.

In some of the examples you've provided, those frameworks definitely don't feel like the right fit in root to me now, but someone made that call back in the day. Rails and WordPress feel like good examples that I would commit to root, as they are extremely common frameworks in the industry.

If you feel ColdBox should be placed in root, we need good justification on why. Does it have a large userbase? Lots of forks? etc. I see it being used, but it hasn't quite reached the level of widespread use that would make me pull it into root.

It's unfortunately rather subjective, but it's the best we can do to prevent root from being flooded with templates.

[lmajano]

Thanks so much for the thoughtful response, @wirecat — I really appreciate the stewardship you're providing for the project and your desire to avoid bloat in the root. It sounds like you’re trying to maintain a high bar for inclusion, which I completely respect.

It seems like the concern is whether ColdBox has the kind of adoption and ecosystem to justify root placement — is that fair to say?

ColdBox has been the de facto standard MVC framework for the CFML language for more than 20 years and, as of 2024, it also supports BoxLang, a modern JVM dynamic language designed for multi-runtime environments. It's been around for nearly two decades, with a rich ecosystem of libraries, tooling, and educational resources. It has become central to how many developers build web apps and APIs in the CFML and JVM spaces.

What’s the best way forward from your point of view?