[ENHANCEMENT]: assets into media directory

hans2103 commented

2025-09-11 06:59:38 +00:00

Enhancement Details

Using the full strength of Joomla I would like to see the assets, like scss, css, js and images, to be moved from /components/[component]/assets/ to /media/[component]/. Doing to you embrace the Joomla 5 and 6 way of working with webassets. It will make it easier for others to override the assets too.
I notice the creation of the directory /media/[component]/css, /media/[component]/images and /media/[component]/js, but they keep empty.

Are there already plans of making this transition?

Which part of the extension will be affected by this enhancement?

Compilation of component, Admin View(admin_view), Admin Views(admin_views), Site View(admin_view), Site Views(admin_views)

Additional Context

No response

### Enhancement Details Using the full strength of Joomla I would like to see the assets, like scss, css, js and images, to be moved from `/components/[component]/assets/` to `/media/[component]/`. Doing to you embrace the Joomla 5 and 6 way of working with webassets. It will make it easier for others to override the assets too. I notice the creation of the directory `/media/[component]/css`, `/media/[component]/images` and `/media/[component]/js`, but they keep empty. Are there already plans of making this transition? ### Which part of the extension will be affected by this enhancement? Compilation of component, Admin View(admin_view), Admin Views(admin_views), Site View(admin_view), Site Views(admin_views) ### Additional Context _No response_

hans2103 added the enhancement label 2025-09-11 06:59:38 +00:00

Llewellyn commented

2025-09-11 13:35:52 +00:00

Owner

Thank you for raising this important enhancement request — we completely agree that moving assets (SCSS, CSS, JS, and images) to /media/[component]/ is the right direction and aligns with Joomla 5 and 6 best practices for web assets.

We have already begun this transition, especially for site views and custom admin views, but a significant part of JCB still references the legacy /components/[component]/assets/ structure. This is partly historical — we've moved code over in several waves, then paused to address higher-priority breaking changes. JCB has undergone thousands of lines of refactoring over the past few months, so we are definitely moving forward, but this particular migration hasn't been the top priority yet because the current approach still works.

That said, we absolutely intend to follow Joomla's approach fully, and we welcome contributions from anyone who wants to help accelerate this migration. Updating this means combing through templates, compiler code, and every reference to these paths — a huge task, given JCB is over 1.2 million lines of code and is maintained by just three core developers. (For context: Joomla itself is about 500k lines of code with hundreds of contributors!)

We are proud of the pace at which JCB continues to evolve, but we also want to make it clear that community participation is welcome and valuable. If you (or others) are interested in contributing to this effort, we can provide guidance and point you to the specific areas in the codebase that need updating.

Thank you for raising this important enhancement request — we completely agree that moving assets (SCSS, CSS, JS, and images) to /media/[component]/ is the right direction and aligns with Joomla 5 and 6 best practices for web assets. We have already begun this transition, especially for site views and custom admin views, but a significant part of JCB still references the legacy /components/[component]/assets/ structure. This is partly historical — we've moved code over in several waves, then paused to address higher-priority breaking changes. JCB has undergone thousands of lines of refactoring over the past few months, so we are definitely moving forward, but this particular migration hasn't been the top priority yet because the current approach still works. That said, we absolutely intend to follow Joomla's approach fully, and we welcome contributions from anyone who wants to help accelerate this migration. Updating this means combing through templates, compiler code, and every reference to these paths — a huge task, given JCB is over 1.2 million lines of code and is maintained by just three core developers. (For context: Joomla itself is about 500k lines of code with hundreds of contributors!) We are proud of the pace at which JCB continues to evolve, but we also want to make it clear that community participation is welcome and valuable. If you (or others) are interested in contributing to this effort, we can provide guidance and point you to the specific areas in the codebase that need updating.

👍 1

Tom van der Laan commented

2025-09-15 21:17:43 +00:00

Member

i'm interested. Let us know what we can do to speed this process up for you.

[ENHANCEMENT]: assets into media directory #1251

Enhancement Details

Which part of the extension will be affected by this enhancement?

Additional Context