Emil Stenström

I think I agree with you here, that things can be simplified quite a bit. I'm a little weary of the autoload feature, because then as a reading of someone...

@hanifbirgani Would you be open to working at this? :)

Sounds like a great structure! The only thing I tried to argue above was that I think that the my-component.py-file should have a reference to my-component.css/html/css in them somewhere, so...

Great points. I agree about encouraging encapsulation and not referencing files outside of the component directory. Let's try another angle. What about encouraging people to split their CSS and JS...

@hanifbirgani Did you have any time to think more about this? I really like these kind of simplifying PRs that slowly chip away at the boilerplate needed. Feels like we...

Fully understand. Yes, that’s what I think we need to do. 1) add a default directory for components, and figure out backwards compatibility. 2) add a CLI command to generate...

Yes, I was thinking about automatically looking in a subdirectory with the same name as the component you registered when resolving the paths to component CSS and JS. So instead...

@simkimsia Almost! The only thing missing now is a management command that generates the structure from the README! Will simplify setup even more.

@alexanderjulmer That is a great idea. Something that is surely[ missing in block tags too](https://stackoverflow.com/questions/2035385/test-for-existence-of-template-block-in-a-template). Would you be open to writing up a PR for adding support like you suggest?

@danjac This wouldn't be a replacement for the CSS/JS that you need for the rest of the site. More a request-local optimization, to avoid sending 50 external files if the...