{"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":54,"created_at":"2015-02-23T21:17:02Z","updated_at":"2015-03-02T09:47:22Z","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/76683449","html_url":"https://github.com/zencart/zc-v1-series/issues/304#issuecomment-76683449","issue_url":"https://api.github.com/repos/zencart/zc-v1-series/issues/304","id":76683449,"user":{"login":"Spike00","id":1826038,"avatar_url":"https://avatars.githubusercontent.com/u/1826038?v=3","gravatar_id":"","url":"https://api.github.com/users/Spike00","html_url":"https://github.com/Spike00","followers_url":"https://api.github.com/users/Spike00/followers","following_url":"https://api.github.com/users/Spike00/following{/other_user}","gists_url":"https://api.github.com/users/Spike00/gists{/gist_id}","starred_url":"https://api.github.com/users/Spike00/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Spike00/subscriptions","organizations_url":"https://api.github.com/users/Spike00/orgs","repos_url":"https://api.github.com/users/Spike00/repos","events_url":"https://api.github.com/users/Spike00/events{/privacy}","received_events_url":"https://api.github.com/users/Spike00/received_events","type":"User","site_admin":false},"created_at":"2015-03-02T09:47:22Z","updated_at":"2015-03-02T09:47:22Z","body":"@DivaVocals  I'm sorry. English is not my language so I probably did not explain correctly what I meant. It's not a matter of what I read or not (I read all the comments), I meant that issues in github it's (Imho of course) not the best way to discuss a so broad topic. You opened this issue with the title as broad as possible about the template. Good, but to me this discussion requires to cover aspects (Now I'm not referring to whitepapers, those are the medium) that you believe are offtopic. If I open a new issue, how should I call it? Since for me it would cover many arguments that would be discussed here, so it would be a (partial) duplicate, so everyone would need to read two collections of comments, maybe partially overlying. It seems to me highly inefficient.\r\nComing back to whitepaper, again I fear my distance from english language betrayed me, so I think I did not succeed in explaining what I mean with whitepaper. Nothing really more than what everyone who contributes already write, just with a canvas to follow to be sure that who proposes something, takes the time to explore if someone already proposed similar feature and to search all the informations useful to evaluate her proposal (hope the word proposal can be used in this context :p).\r\nI believe that this is a right approach to software collaboration, otherwise why don't use github in it's main feature, fork and pull? This said I understand you request about the way to discuss and I'll open a new issue.\r\n\r\nLast thing, you wrote:\r\nIf contributors to this repo want to go with the whitepaper approach, and the admins are okay with this approach, then who am I to question it... I just don't have time to write one, and I personally will continue to use this current medium to continue a dialogue on this topic with anyone who wishes to continue to use this medium for that purpose..\r\n\r\nI don't think this is a good approach in a collaboration environment. Personally, if admins think that using issues on github to discuss this topic is the right way, I'll try to make my best to contribute using this medium. I wouldn't go on my way just because I think different."}}