Closed trevordmiller closed 9 years ago
This all sounds good. I updated your comment so I can treat it as a todo list.
One issue I'm running into is that LiveReload tries to inject new CSS instead of doing a browser refresh (https://github.com/gruntjs/grunt-contrib-watch/issues/359). It looks like BrowserSync may work in a similar fashion. Injecting styles like that doesn't seem to make HTML Imports and Polymer happy so I may need to come up with a workaround.
@robdodson Sweet. I've been building a lot with the Polymer Yeoman generator and subgenerators the past few days and I really like it. I'm excited for these updates as well.
Another thought: In my opinion, it would make sense to have the elements
directory structured the same way as all of the core
and paper
element repos/folders that are pulled down with Bower (see screenshot). For example...
app
> elements
> my-element.html
app
> elements
> my-element
> my-element.html / my-element.css / my-element.js / my-element.scss
The el
sub-generator could produce files like this instead of all clumped together in a single .html
file. This seems to me to be the most logical way to separate Sass files from CSS and separate code types out (this would help with linting problems as well) while still keeping everything in a modular setup (not requiring a global Sass file or something). Just an idea. Thoughts?
Yep I agree. I've already started adding that behavior over in the sass branch. It makes the grunt stuff a bit easier to manage too.
@robdodson :)
It's so awesome to see this work started.
One of the things on our roadmap for Polymer + Web Starter Kit is to create a new GitHub repo on the Google org which (like WSK) is git clone friendly and doesn't strictly require Yeoman to use it.
We see that also having a few nice bells and whistles like a Paper element populated version of the style guide and more layouts. Perhaps there would be an opportunity for code sharing when we start that? On 28 Jul 2014 15:57, "Trevor D. Miller" notifications@github.com wrote:
@robdodson https://github.com/robdodson :)
— Reply to this email directly or view it on GitHub https://github.com/yeoman/generator-polymer/issues/52#issuecomment-50349569 .
@addyosmani I'm interested in, When you getting started?
Yeah for sure!
We'll probably get started on an official Polymer WSK in September. It'll take a little while to get approval from Google for the GitHub repo (polymer-web-starter-kit or polymer-starter-kit) but I think it'll be awesome to look at how we can prescribe an end-to-end tooling workflow for Polymer users right out of the box.
@addyosmani Awesome! Can't wait.
@addyosmani Fantastic! I'm already expecting it.
Assigning to 0.7.0 milestone. Not sure if the living style guide will make the cut, but I definitely want to get BrowserSync in there
:+1:
I feel like everything on the list is checked off except for the living style guide. Moving that to its own issue: https://github.com/yeoman/generator-polymer/issues/138
From Rob Dodson's request to create a ticket on a recent Twitter conversation:
To match/sync with the setup of Google's Web Starter Kit and with what Addy Osmani has been talking about (creating a "flavor" of the Web Starter Kit with Polymer/Web Components baked in), I would love to see/help with a few changes with this generator:
Recommended updates to generator-polymer
element-name.html
file generated withyo polymer:el element-name
?.jshintrc
,.editorconfig
etc.P.S.
I just want to let the Polymer team know that you are amazing! Me and a few other developers at my company are working hard to adopt and push Web Components and Polymer to our fellow developers; all of your trainings/talks, hard work, updates, tools, and kindness is much appreciated. You are doing amazing work that is changing the development world.
Please let me know if you need my help with anything. I don't mean to just bring up issues here, but would like to contribute and evangelize Polymer and Web Components with my fellow developers ;)