picnic

I fell in love with SCSS on first sight and it has greatly helped me improve my front-end programming. From time to time I think of features that could make it even better. However, when I went to propose them I found that they are already proposed, like optional imports [1] and importing .css files (besides .scss) [2]. Some are closed, even though they are still planned for some point in the future. While I understand that it's a large project and it should be not easy to manage it, the date is from 2011 and 2013. Further investigation[3] shows that from 2007-2011, the top contributor Natalie Weizenbaum (nex3) was really active (~4k commits) in the site but now she seems to work for Google[4] on Dart. The 2nd biggest contributor made ~494 commits, or 10%. Third one made 40 or 1%. As a SCSS developer myself [5] I am interested in seeing S

That's the whole Picnic CSS library, including the tab plugin. The plugin itself is 97 lines of SCSS (including spaces). The odd part, and I'm the author I think is that sometimes the html get a bit overcomplicated and not flexible. You can see the source here: https://github.com/picnicss/picnic/blob/dev/plugins/tabs/_ta...

I am the developer of Picnic CSS and I found several deficiencies in the current model I'm using [1]. I know now what works best for me, but I am also interested in what works best for you to make it easier. So, how do you prefer including external front-end libraries? 1. Use a CDN to include the external minimized file. 2. Use bower or other front-end package manager to integrate the developer files (SASS). If it's other, which one? 3. Download the static, minimized file and include it manually (either in your build system or just as another stylesheet). 4. Clone the repository to make sure that you're always up to date (I think this was common before front-end package managers appeared). 5. Other. Which one? How? And why? For me the 1. works best for small and fast projects and 2. works best when heavy personalization is needed. So, whi