search

firecups / ispconfig-firecups-theme

9 stars 1 forks source link

To use or not to use own templates, that's the question #15

Open thompol opened 3 years ago

thompol commented 3 years ago

Maybe it's not a good idea to use custom .htm templates for every module. This makes maintaining a secondary theme a lot of work. A lot. Keeping up with the minimal changes to the default theme is one thing, but having custom templates for every module can result in missing functions because they are not added to the template of this theme and broken functions that are removed from the panel but exist in the template of this theme.

So, I don't think it's a good idea to use custom templates for every module. If the decision is to do this anyway, make sure to check EVERY commit to the project on the themes folder and .htm templates of every module to keep up (but only push this changes to this theme when the new release is out, so you can have in between versions of this theme without breaking anything)

firecups commented 3 years ago

The problem is, the exists templates of ispconfig are very inflexible and limited. so at the moment i see no other way to create a custom and "modern" design based on the exists system.

At the moment i work on the templates based on the last release (version 3.2) of ispconfig. Sure, with the next stable release or bugfixes, i must compare the changes and add or remove this on the theme.