In the latest update support was added for custom templates in Drupal. That's an amazingly powerful feature and it's gotten me all exited :)
I think however that a few improvements are needed.
- The templates like "post" make very little sense. Ususally Drupal ships with "basic page" and "article" content types (entity bundles). I think it would make more sense if the Themler template names correspond with those.
- When creating custom templates, you have to assign them to a URL. That too, makes little sense. It's a good feature to have, but basically a template should be attached to a content type (entity bundle). In Drupal it's very common to have your specific content types for each site, and they would pretty much always require a uniform layout. So if you have a content type called "fruit" it would make sense to be able to create a custom template in Themler, and assign it to all content of the type "fruit", not a URL.
- Currently it's only possible to configure how the templates are used if the theme is exported to include the themler module. That isn't desirable, for production sites one would not want the Themler module to be installed.
Furthermore, the problem with working with a URL is that if even if you specify a url logic so that all fruit content has http://.../fruit/[some-title], and configure the template to be show on fruit/*, it would only work on that clean URL but not on it's native url, node/xxx.
In the latest update support was added for custom templates in Drupal. That's an amazingly powerful feature and it's gotten me all exited :) I think however that a few improvements are needed. 1. The templates like "post" make very little sense. Ususally Drupal ships with "basic page" and "article" content types (entity bundles). I think it would make more sense if the Themler template names correspond with those. 2. When creating custom templates, you have to assign them to a URL. That too, makes little sense. It's a good feature to have, but basically a template should be attached to a content type (entity bundle). In Drupal it's very common to have your specific content types for each site, and they would pretty much always require a uniform layout. So if you have a content type called "fruit" it would make sense to be able to create a custom template in Themler, and assign it to all content of the type "fruit", not a URL. 3. Currently it's only possible to configure how the templates are used if the theme is exported to include the themler module. That isn't desirable, for production sites one would not want the Themler module to be installed. Furthermore, the problem with working with a URL is that if even if you specify a url logic so that all fruit content has http://.../fruit/[some-title], and configure the template to be show on fruit/*, it would only work on that clean URL but not on it's native url, node/xxx.










