You are totally right, but there might not even need for that. I’m porting a commercial theme (spotter) to meteor. It has been 3 painful months.
At first I bought it as soon as it came out. It had some Sass errors which fucked everything up. I had to learn SASS (1 wasted month), and then fix the CSS. At the beginning the author refused to admit there was any error in the Sass. One week after I fixed the CSS, he published a new version with fixed Sass. First flip table rage quit.
When I was sure CSS was working, I switched to port JS. Let’s take this example. There is one case if width is less than 979. Then another snippet does the same exact thing if width is greater that 979. But in a very convoluted way.
JS code is really messy, many things seems useless, it is poorly documented, and if you touch something then something else will break. For example mobile styles are loaded in desktop version, and vice versa. It’s a nightmare.
I’m studying line for line to understand what’s happening, how code interact with the rest, etc. I will definitely rewrite most of it, but I need to learn it first/.
Thanks that did it.
Thank you very much @jasoncchild . I’ve made several forks of the main repo with CSS working, because I want to play with the JS code. I missed that.
Anyhow I have another problem now: Some pages relies on body tags to correctly show CSS. Different pages have different body tags. If I put body tags outside of template, then they will be loaded by default.
How can I specify body tags on a per template basis?