{"action":"created","issue":{"url":"https://api.github.com/repos/plone/mockup/issues/467","labels_url":"https://api.github.com/repos/plone/mockup/issues/467/labels{/name}","comments_url":"https://api.github.com/repos/plone/mockup/issues/467/comments","events_url":"https://api.github.com/repos/plone/mockup/issues/467/events","html_url":"https://github.com/plone/mockup/pull/467","id":60254562,"number":467,"title":"split into mockup and plone.mockup","user":{"login":"thet","id":170891,"avatar_url":"https://avatars.githubusercontent.com/u/170891?v=3","gravatar_id":"","url":"https://api.github.com/users/thet","html_url":"https://github.com/thet","followers_url":"https://api.github.com/users/thet/followers","following_url":"https://api.github.com/users/thet/following{/other_user}","gists_url":"https://api.github.com/users/thet/gists{/gist_id}","starred_url":"https://api.github.com/users/thet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thet/subscriptions","organizations_url":"https://api.github.com/users/thet/orgs","repos_url":"https://api.github.com/users/thet/repos","events_url":"https://api.github.com/users/thet/events{/privacy}","received_events_url":"https://api.github.com/users/thet/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-08T12:29:17Z","updated_at":"2015-03-10T17:06:40Z","closed_at":"2015-03-08T12:31:43Z","pull_request":{"url":"https://api.github.com/repos/plone/mockup/pulls/467","html_url":"https://github.com/plone/mockup/pull/467","diff_url":"https://github.com/plone/mockup/pull/467.diff","patch_url":"https://github.com/plone/mockup/pull/467.patch"},"body":"Split out the Python package into ``plone.mockup`` and make ``mockup`` installable via ``bower`` again."},"comment":{"url":"https://api.github.com/repos/plone/mockup/issues/comments/78099624","html_url":"https://github.com/plone/mockup/pull/467#issuecomment-78099624","issue_url":"https://api.github.com/repos/plone/mockup/issues/467","id":78099624,"user":{"login":"jcbrand","id":683911,"avatar_url":"https://avatars.githubusercontent.com/u/683911?v=3","gravatar_id":"","url":"https://api.github.com/users/jcbrand","html_url":"https://github.com/jcbrand","followers_url":"https://api.github.com/users/jcbrand/followers","following_url":"https://api.github.com/users/jcbrand/following{/other_user}","gists_url":"https://api.github.com/users/jcbrand/gists{/gist_id}","starred_url":"https://api.github.com/users/jcbrand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcbrand/subscriptions","organizations_url":"https://api.github.com/users/jcbrand/orgs","repos_url":"https://api.github.com/users/jcbrand/repos","events_url":"https://api.github.com/users/jcbrand/events{/privacy}","received_events_url":"https://api.github.com/users/jcbrand/received_events","type":"User","site_admin":false},"created_at":"2015-03-10T17:06:40Z","updated_at":"2015-03-10T17:06:40Z","body":"Interesting that you bring up \"development process\".  This is perhaps something that needs to be clarified.\r\n\r\nPatternslib was inspired by a  \"design first\" methodology whereby a static, patterns-enhanced prototype (or Diazo theme if you like) is initially designed, approved by the customer (or community) and then integrated into the website. This is an iterative, rapid-prototyping process whereby the client gets to see what the site will look like even before any Plone development has been done.\r\n\r\nPatternslib is primarily meant to make designer's lives easier, not developers. It also helps people selling Plone sites to show clients how things will look and behave without having to first write the backend functionality.\r\n\r\nThe is the methodology we are currently following with Plone Intranet so it's something that more and more people are becoming acquainted with.\r\n\r\nI'm not saying this is the holy grail of development methodologies, just that this is the main point of patterns, and that patterns lose a lot of their power when not used with such a \"design first\" approach.\r\n\r\nThis is apparently not the approach that was taken with mockup and I get the impression that many mockup devs are not aware of this \"design first\" philosophy that is the inspiration behind patterns.\r\n\r\nOne consequence of the \"design first\" approach is that it's possible to do the majority of pattern development completely outside of Plone. For example, we're currently having the Plone Intranet sprint where the bulk of the patterns work is done in the standalone patterns with just the Node development stack. No Plone involved.\r\n\r\nThe designer(s) then uses these patterns to create the prototype which then gets applied to the site via Diazo.\r\n\r\nIMHO, this should be the same with mockup. It should be possible to work on mockup patterns completely independently of Plone. Yes, it will still be required to test whether the patterns work in Plone, or with the Plone backend, but that's not where the main development would then happen.\r\n\r\nSo, IMHO, if you need to have a full Plone site to do pure mockup pattern development, then you're doing it wrong."}}