{"action":"created","issue":{"url":"https://api.github.com/repos/yahoo/pure/issues/414","labels_url":"https://api.github.com/repos/yahoo/pure/issues/414/labels{/name}","comments_url":"https://api.github.com/repos/yahoo/pure/issues/414/comments","events_url":"https://api.github.com/repos/yahoo/pure/issues/414/events","html_url":"https://github.com/yahoo/pure/issues/414","id":52682789,"number":414,"title":"Pure Roadmap 2015","user":{"login":"jamesalley","id":824331,"avatar_url":"https://avatars.githubusercontent.com/u/824331?v=3","gravatar_id":"","url":"https://api.github.com/users/jamesalley","html_url":"https://github.com/jamesalley","followers_url":"https://api.github.com/users/jamesalley/followers","following_url":"https://api.github.com/users/jamesalley/following{/other_user}","gists_url":"https://api.github.com/users/jamesalley/gists{/gist_id}","starred_url":"https://api.github.com/users/jamesalley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamesalley/subscriptions","organizations_url":"https://api.github.com/users/jamesalley/orgs","repos_url":"https://api.github.com/users/jamesalley/repos","events_url":"https://api.github.com/users/jamesalley/events{/privacy}","received_events_url":"https://api.github.com/users/jamesalley/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":28,"created_at":"2014-12-22T19:57:51Z","updated_at":"2015-05-05T19:18:43Z","closed_at":null,"body":"[James Alley – Welcome to Pure!](http://blog.purecss.io/post/105884870851/welcoming-james-to-pure)\r\n\r\n# Pure Roadmap 2015\r\n\r\nDuring the latter part of 2014, Pure has cruised along. Pull requests have come in, people have filed issues, and in some cases we've taken the time to integrate the changes or comment. Meanwhile, we have focused on some exciting new efforts, quite separate from Pure, which will bear fruit in the coming year. But it's time to dive back into Pure, and to share with everyone our roadmap for Pure in 2015.\r\n\r\n## The Scope and Vision for Pure\r\n\r\nWe still intend to keep Pure small, focused, and useful to any web project. We intend to refine and maintain Pure, rather than radically expand its scope. Pointedly, Pure will not expand to become a library of drop-in UI components. Rather, it will remain a foundation with a \"ridiculously tiny\" footprint that developers use as a starting point for writing their own CSS.\r\n\r\nThere has been some discussion on whether Pure should expand to become a component library, replete with segmented controls, drop-downs, tab-views, etc. We perhaps contributed to this perception by including a paginator component. Why do so, if Pure is more about smoothing the foundation than creating components? \r\n\r\nFor inclusion in Pure, a construct must meet the following criteria:\r\n\r\n  * Common (useful to the vast majority of websites, ~80%+)\r\n  * Non-trivial\r\n\r\nIn other words, we're looking for stuff that everyone needs and yet finds difficult to implement with the proper semantics, accessibility (including keyboard access), and browser support. In fact, for these reasons, in the upcoming 0.6 release, we're removing the Paginator component. Pagination is not common enough, many sites use infinite scrolling, and it's trivial to implement yourself using inlined button-styled anchors. But this can be a gray area. We don't scientifically evaluate the 80% rule; difficulty and triviality are obviously subjective. So we welcome suggestions and the discussions they will spark.\r\n\r\n### About Those Pull Requests...\r\nIncidentally, we cannot merge some very good PRs due to a lack of a CLA (license) on file for the contributor. Please don't let this discourage you! To take care of the CLA, simply follow the link to sign electronically. (https://yahoocla.herokuapp.com) \r\n\r\n## The Road to 1.0\r\n\r\nThe community has battle-tested Pure and provided feedback. In addition to incorporating bug fixes into Pure, we wish to focus on five areas of refinement before we declare Pure ready for a 1.0 stamp, whereby we begin to guarantee backwards compatibility through all subsequent 1.x releases.\r\n\r\n  1. **New Pure Menus.** The 0.6 release will include a new Menus component developed by Pure contributor Tilo Mitra to be more responsive and more easily customizable.\r\n\r\n  1. **Removal of Paginator.** Paginator doesn't meet the 80% bar, and is trivial to implement as inlined button-styled anchors. Removed in 0.6.\r\n\r\n  1. **Revamped Forms which leverage Grids.** Currently, Forms has some utility classes to aid with layout, but we plan to remove them in favor of letting users leverage Grids instead.\r\n\r\n  1. **Refinements to Grids.** At the very least, we want to bring more browsers onboard to Grids' flexbox-based implementation. Some users have noted the font-family: sans-serif dependency as an annoyance, so that is worth re-examining. There may be takeaways from other grid constructs that we can apply.\r\n\r\n  1. **Removal of vendor-prefixing from source.** While this does not affect end users of Pure, we plan to remove vendor-prefixing from the source code in favor of inserting them via post-processing in the build. You'll still see them in the finished CSS on the CDN.\r\n\r\nOf course, our backlog of issues and PRs may also surface important changes we'll want to incorporate into Pure as well. As the outline below illustrates, even without an ambitious expansion of Pure, plenty of tasks lay ahead 2015. Without further ado, then, here's our plan, organized into three-month quarters.\r\n\r\n### **Q1.** Pure 0.6\r\n  1. Merge new-pure-menu PR\r\n  1. Refactor pure-site accordingly\r\n  1. Release Pure 0.6 and pure-site\r\n  1. Address open PRs and issues\r\n\r\n### **Q2.** Servicing feature requests\r\n  1. Complete the review and absorption of all outstanding pull requests\r\n  1. Clean up pure-form to remove functionality duplicated by pure-grid\r\n  1. Update Pure-site accordingly\r\n  1. Release 0.7\r\n  1. Revise Pure so that vendor prefixing can be accomplished with configurable post processing.\r\n  1. Investigate supporting a CSS-driven approach (and possible Sass integration) for using Pure along with the current HTML-driven approach (annotating HTML with class names).\r\n\r\n### Q3. Pure 1.0 Release, and Components\r\n  1. Fix bugs surfaced by the 0.7 release.\r\n  1. Release 1.0.\r\n\r\n### Q4. Post 1.0\r\n  Per semantic versioning, 1.0 will be our signal to the world that backwards compatibility will be assured in future 1.x versions. Should the need arise to break backwards compatibility with 1.0, we will increment to 2.x releases.\r\n\r\nAnd that's it! We hope you have found Pure to be useful and unobtrusive, and that you look forward to Pure's continued improvement. To provide feedback, please comment on this GitHub issue, or file a new issue to have it tracked as a separate thread.\r\n\r\n– [James Alley](http://blog.purecss.io/post/105884870851/welcoming-james-to-pure) and the Yahoo Presentation Technologies team"},"comment":{"url":"https://api.github.com/repos/yahoo/pure/issues/comments/99189987","html_url":"https://github.com/yahoo/pure/issues/414#issuecomment-99189987","issue_url":"https://api.github.com/repos/yahoo/pure/issues/414","id":99189987,"user":{"login":"sitegoals","id":976467,"avatar_url":"https://avatars.githubusercontent.com/u/976467?v=3","gravatar_id":"","url":"https://api.github.com/users/sitegoals","html_url":"https://github.com/sitegoals","followers_url":"https://api.github.com/users/sitegoals/followers","following_url":"https://api.github.com/users/sitegoals/following{/other_user}","gists_url":"https://api.github.com/users/sitegoals/gists{/gist_id}","starred_url":"https://api.github.com/users/sitegoals/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sitegoals/subscriptions","organizations_url":"https://api.github.com/users/sitegoals/orgs","repos_url":"https://api.github.com/users/sitegoals/repos","events_url":"https://api.github.com/users/sitegoals/events{/privacy}","received_events_url":"https://api.github.com/users/sitegoals/received_events","type":"User","site_admin":false},"created_at":"2015-05-05T19:18:43Z","updated_at":"2015-05-05T19:18:43Z","body":"I use it."}}