Closed jkremser closed 6 years ago
I think this fixes #132 @laCour could you check this and get it merged?
I guess, he doesn't want to merge my PRs, because he uses scss for generating these css files. If it's the case, I have no idea why the css files are in the repo (master) itself, because it's pretty confusing for the potential contributors.
@laCour you can for instance let the travis CI to process your SASS assets and push the generated CSS to a branch called dist
or something similar.
@Jiri-Kremser That would be why your PRs aren't merged. In hindsight, using CI would be preferred, but now the CSS is relied on and expected to be in master. Perhaps I can leave the existing styles in master for a bit and have a CI service build to a new branch. Thanks for bringing this up.
That said, there is a contribution guide detailing how contributions can and should be made. See #167 for these fixes.
before: https://i.imgur.com/2gjA3VG.png after: https://i.imgur.com/HcqsqQl.png