Have a theme folder for templates, snippets and assets

[gagarine]

I think everything related to front-end of the website should be in a theme folder. Somethings like that.

• site
  • blueprint
  • config
  • theme
    • templates
    • assets
    • snippets

[lukasbestle]

We had a discussion around this a while ago, but unfortunately I don't remember where.

The conclusion was: As Kirby sites are mostly custom-built, the use-cases for theme bundling are limited. It's not like with other CMS where themes can be swapped in and out.

So a theme folder is likely not going to become the default for Kirby sites. An option could work, but it would make the CMS code more complex and I currently don't see that this will be used by many users.

But you can implement the feature yourself in a plugin: Plugins can register all types of extensions, so you can loop over all files and register them in your plugin. Please note that the performance will be slightly lower, but that would also be the case if we added support for this in the core.

[gagarine]

The conclusion was: As Kirby sites are mostly custom-built, the use-cases for theme bundling are limited. It's not like with other CMS where themes can be swapped in and out.

I understand this is not the same than other CMS. But still, I think it would be helpful to organize everything front-end related in a folder. One could use it to put npm package used to build the theme for example. Also if you do a migration from one theme to another, you could then quickly change between one or another. It would make concept such as "snippets" self-explanatory.

[bvdputte]

You already can do this if you want:

• via custom folder setup: https://getkirby.com/docs/guide/configuration#custom-folder-setup
• via a plugin: https://getkirby.com/docs/guide/plugins/plugin-types