{"action":"opened","issue":{"url":"https://api.github.com/repos/Polymer/vulcanize/issues/268","labels_url":"https://api.github.com/repos/Polymer/vulcanize/issues/268/labels{/name}","comments_url":"https://api.github.com/repos/Polymer/vulcanize/issues/268/comments","events_url":"https://api.github.com/repos/Polymer/vulcanize/issues/268/events","html_url":"https://github.com/Polymer/vulcanize/issues/268","id":113035626,"number":268,"title":"Vulcanize fork concept, for buffers","user":{"login":"HyphnKnight","id":3604882,"avatar_url":"https://avatars.githubusercontent.com/u/3604882?v=3","gravatar_id":"","url":"https://api.github.com/users/HyphnKnight","html_url":"https://github.com/HyphnKnight","followers_url":"https://api.github.com/users/HyphnKnight/followers","following_url":"https://api.github.com/users/HyphnKnight/following{/other_user}","gists_url":"https://api.github.com/users/HyphnKnight/gists{/gist_id}","starred_url":"https://api.github.com/users/HyphnKnight/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HyphnKnight/subscriptions","organizations_url":"https://api.github.com/users/HyphnKnight/orgs","repos_url":"https://api.github.com/users/HyphnKnight/repos","events_url":"https://api.github.com/users/HyphnKnight/events{/privacy}","received_events_url":"https://api.github.com/users/HyphnKnight/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-23T14:52:40Z","updated_at":"2015-10-23T14:52:40Z","closed_at":null,"body":"I would like to fork the current vulcanize repo in an effort to add a new feature. The idea is to allow a new option be specified called something along the lines of `buffers` which accepts an array of strings. The new functionality would parse through the strings until it finds the `id` attribute. Vulcanize would then replace the equivalent html import with the buffer.\r\n\r\n**Use Case**  : This is useful for any kind of generated html, whether its jade or any other template engine. I personally would like to use this to code modules in jade.\r\n```jade\r\ndom-module#x-custom\r\n  template\r\n    style.\r\n      :host {\r\n        display: block;\r\n        border: 1px solid red;\r\n      }\r\n      #child-element {\r\n        background: yellow;\r\n      }\r\n      /* styling elements distributed to content (via ::content) requires */\r\n      /* selecting the parent of the <content> element for compatibility with */\r\n      /* shady DOM . This can be :host or a wrapper element. */\r\n      .content-wrapper > ::content .special {\r\n        background: orange;\r\n      }\r\n    | Hello World from <span id=\"name\"></span>!\r\n\r\n  script.\r\n    Polymer({\r\n\r\n      is: 'x-custom',\r\n\r\n      ready: function() {\r\n        this.$.name.textContent = this.name;\r\n      }\r\n\r\n    });\r\n```\r\nIn addition it allows for the chained processing of files. For examples if you wanted to break up the `<template>` `<style>` and `<script>` into separate files in a structure like,\r\n* `moduleName`\r\n    * `template.html` || `template.jade`\r\n    * `style.css` || `style.scss` || `style.sass`\r\n    * `script.js`\r\n\r\nThen assemble them afterward in a build process that would be impossible *(as far as I know)* to do with having to create/delete temp files. \r\n\r\nI believe the buffer property would open up new opportunities for the development of polymer applications using `vulcanize`. If you agree with me, or have an alternative existing functionality route I could take, please let me know so I can either start working on this feature or integrate the existing functionality into my build path.\r\n\r\nThank you in advance,\r\nRafe Lepre"}}