{"action":"created","issue":{"url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304","labels_url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304/labels{/name}","comments_url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304/comments","events_url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304/events","html_url":"https://github.com/zencart/zc-v1-series/issues/304","id":58649729,"number":304,"title":"The future of the Default Template & ClassicTemplate in v1.6.0.. (consistency, mobile design/resposiveness, overall look & feel)","user":{"login":"DivaVocals","id":338734,"avatar_url":"https://avatars.githubusercontent.com/u/338734?v=3","gravatar_id":"","url":"https://api.github.com/users/DivaVocals","html_url":"https://github.com/DivaVocals","followers_url":"https://api.github.com/users/DivaVocals/followers","following_url":"https://api.github.com/users/DivaVocals/following{/other_user}","gists_url":"https://api.github.com/users/DivaVocals/gists{/gist_id}","starred_url":"https://api.github.com/users/DivaVocals/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DivaVocals/subscriptions","organizations_url":"https://api.github.com/users/DivaVocals/orgs","repos_url":"https://api.github.com/users/DivaVocals/repos","events_url":"https://api.github.com/users/DivaVocals/events{/privacy}","received_events_url":"https://api.github.com/users/DivaVocals/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-02-23T21:17:02Z","updated_at":"2015-02-24T17:19:23Z","closed_at":null,"body":"Templates.. Surprised there's been very little to NO discussion here with regards to the current template system.. However, templates are worthy of a serious looksee as they are the thing unfortunately that leads folks to \"judge a book by it's cover\" with regards to how Zen Cart is evaluated by novice store owners and even technical folks. No matter if this is a fair or unfair evaluation factor, the fact is that it IS an evaluation factor, and there's no reason to NOT improve things in this respect.\r\n\r\nSo let me start with the proverbial elephant in the room :laughing:\r\n**Classic Template -** I don't think anyone would disagree that the Classic template is a LOT overdue for a MAKEOVER.. The Classic template that comes with Zen Cart out the box doesn't do a very good job of representing the product IMHO. Now I realize that for years, the emphasis has been on security, and functionality.. and no doubt these are important considerations, but WHY NOT make moves to make Zen Cart LOOK attractive as well.. I typically replace ALL of the Classic template folders and files with the Barbones template's folders and files because while Barebones is PLAIN, it's a LOT nicer looking than Classic.. Is there ANY opposition to a pull request to make Classic at least a LITTLE more visually appealing or has one just not been submitted??\r\n\r\n**Lack of Consistency in the Default Template -** Typically when I build a Zen Cart template there's a LOT of overrides I find that I need to include with my template to \"fix\" (address) what are either missing IDs and classes within the default template or to add a level of consistency to classes and IDs that IMHO is missing in the current default template. Perhaps now is the time to start to examine the entire default template.\r\n\r\n**Responsive/Mobile Capabilities -** I haven't seen any movement on this front, and wonder if the plan is to include any kind of foundation for responsive/mobile elements in the default or Classic templates or will the direction of Responsive/Mobile templates continue to be a function of free template contributors??"},"comment":{"url":"https://api.github.com/repos/zencart/zc-v1-series/issues/comments/75800601","html_url":"https://github.com/zencart/zc-v1-series/issues/304#issuecomment-75800601","issue_url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304","id":75800601,"user":{"login":"IronLady","id":1428276,"avatar_url":"https://avatars.githubusercontent.com/u/1428276?v=3","gravatar_id":"","url":"https://api.github.com/users/IronLady","html_url":"https://github.com/IronLady","followers_url":"https://api.github.com/users/IronLady/followers","following_url":"https://api.github.com/users/IronLady/following{/other_user}","gists_url":"https://api.github.com/users/IronLady/gists{/gist_id}","starred_url":"https://api.github.com/users/IronLady/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/IronLady/subscriptions","organizations_url":"https://api.github.com/users/IronLady/orgs","repos_url":"https://api.github.com/users/IronLady/repos","events_url":"https://api.github.com/users/IronLady/events{/privacy}","received_events_url":"https://api.github.com/users/IronLady/received_events","type":"User","site_admin":false},"created_at":"2015-02-24T17:19:23Z","updated_at":"2015-02-24T17:19:23Z","body":"Agree with @DivaVocals about the lack of consistency.\r\nWhy don't we create a list of difficulties we are facing when creating a template (Maybe mention it on your comment). So the core team can create something like a checklist or milestone based on that list or maybe we can help them too."}}