{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/1b32fae892ca31c0f0c46eb7c7cc3964?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1b32fae892ca31c0f0c46eb7c7cc3964","url":"https://api.github.com/users/eKoeS","login":"eKoeS","id":170682},"milestone":null,"assignee":null,"labels":[{"name":"suggestion","color":"7ecef1","url":"https://api.github.com/repos/symphonycms/symphony-2/labels/suggestion"}],"updated_at":"2011-10-29T12:34:32Z","comments":3,"closed_at":null,"url":"https://api.github.com/repos/symphonycms/symphony-2/issues/868","body":"In my [`template_files`](https://github.com/eKoeS/symphony-2/compare/integration...template_files) branch I've started changing some template names for better readability. This is what I've done:\r\n\r\n```\r\ndatasource.tpl              => blueprints.datasource.tpl\r\nevent.tpl                   => blueprints.event.tpl\r\npage.xsl                    => blueprints.page.xsl\r\n[new entry]                 => blueprints.utility.xsl\r\n\r\nerrorhandler.tpl            => fatalerror.generic.tpl\r\nfatalerror.tpl              => fatalerror.database.tpl\r\n\r\ntpl.error.php               => usererror.generic.php\r\ntpl.xslt-error.php          => usererror.xslt.php\r\ntpl.database-error.php      => usererror.database.php\r\n\r\nnotification.tpl            => email.entrycreated.tpl\r\n```\r\n\r\n<del>Note that in my `localisation_namespace` branch I've [added two more files](https://github.com/symphonycms/symphony-2/issues/667#issuecomment-2534460), as a solution for issue #667:</del>\r\n\r\nIt would be a good idea in my opinion to move `transliterations.php` and `datetime.php` from `LANG` to `TEMPLATE` and rename them:\r\n\r\n```\r\nlang.transliterations.php\r\nlang.datetime.php\r\n```\r\n\r\nThey would fit quite nicely.\r\n\r\nWell, not that much to say. Like it or hate it?","html_url":"https://github.com/symphonycms/symphony-2/issues/868","number":868,"title":"Templates' naming conventions","id":2060858,"created_at":"2011-10-26T19:50:01Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/1b32fae892ca31c0f0c46eb7c7cc3964?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1b32fae892ca31c0f0c46eb7c7cc3964","url":"https://api.github.com/users/eKoeS","login":"eKoeS","id":170682},"updated_at":"2011-10-29T12:34:32Z","url":"https://api.github.com/repos/symphonycms/symphony-2/issues/comments/2564692","body":"Some thoughts:\r\n\r\n* `blueprints.page.xsl` and `blueprints.utility.xsl` are not real templates. The contents of these files are used as default values for textareas (the same thing is true for `lang.transliterations.php` and `lang.datetime.php`)\r\n* `usererror.*.php` are not real templates. They are pages that display errors that are not fatal.\r\n\r\nBased on the above considerations, I'd like to change the folder's name from `template` to `includes` which sounds more generic. This can be done without breaking compatibility, all we need to do is updating the value of the `TEMPLATE` constant.","id":2564692,"created_at":"2011-10-29T12:34:32Z"}}