# sass Published articles for sass. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CSS and TailwindCSS Approaches to Styling Websites in 2024 DevFeed: [CSS and TailwindCSS Approaches to Styling Websites in 2024]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2023-12-27T16:00:42Z Content type: opinion Language: en Sources: [Front-End Focus]() Topics: [CSS](), [Front end](), [Tailwind CSS](), [Web Development](), [Sass](), [Less](), [browsers](), [Design system]() Tags: [2017](), [browsers](), [css](), [design-system](), [flexbox](), [front-end](), [less](), [sass](), [tailwind]() ### AI overview This opinion article examines approaches to styling websites in 2024. It argues that vanilla CSS has become more capable through features such as custom properties, CSS Grid, and CSS nesting, while TailwindCSS remains popular for reducing style conflicts and discouraging arbitrary values. The article also emphasizes that TailwindCSS still requires knowledge of underlying CSS concepts such as Flexbox, Grid, and the box model. ### Source excerpt Hi again! ## Building a Bootstrap App with Rails 7 and SCSS Files DevFeed: [Building a Bootstrap App with Rails 7 and SCSS Files]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-22T06:12:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Bootstrap](), [Front end](), [Web Development](), [CSS]() Tags: [app](), [bootstrap](), [front-end](), [rails](), [sass](), [scss]() ### AI overview A walkthrough of setting up a Rails 7 application with Bootstrap and SCSS files, including generating the app, adding sassc-rails, copying stylesheets, and managing import order for asset compilation. ### Source excerpt As is too often the case, I find that the initial aspect of getting a modern app (Bootstrap, Tailwind, React) initially setup to be the most frustrating aspect of Rails. Given that I like to spin up new apps pretty regularly, well, I spend a lot of time being frustrated with an old man's grumbling of: It didn't used to be this hard. No it wasn't this hard. And while I still don't really understand asset compilation, I did recently put together a new app where I pulled in SCSS files using variables from a different app and I can start to see it. This blog post walks through a Rails 7 app using .scss files. Step 1: Rails New Here's your Rails 7 new command to generate a new app with Bootstrap: rails new scss_test1 --css bootstrap Yep. That's it. Whoa!!! There are also options to use Tailwind. I found this technique in the Saeloun article linked below and I will be forever grateful; seriously - thank you. Step 2: Add the Sassc-Rails Gem I believe this Gem is needed as sassc support is officially deprecated. But I might be wrong about this; front end stuff changes with every Rails release so if I'm wrong, well, sigh. gem "sassc-rails" NOTE: Please see the last section "That Mysterious Error"; you may not want this in your Gemfile or: Step 3: Copy In Your SCSS Files If you are pulling in SCSS files then you need to copy them into your: app/assets/stylesheets directory. They can exist elsewhere but that directory is for stylesheets so differing on this point confuses me. Modify Your Include Directives This is the tricky bit and where you simply have to experiment. The thing to understand is that asset compilation is just that - compilation.If you're old school enough that you understand the analogy of your stylesheet files becoming akin to a make file with all the dark magic that entails, perhaps that helps. In your stylesheets directory there will be an initial stylesheet file, for me, it was application_bootstrap.scss and then I had copied in a number of other styleshee ## Tackling Hugo Integration of Asciidoctor DevFeed: [Tackling Hugo Integration of Asciidoctor]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2020-04-23T21:59:50Z Content type: tutorial Language: en Sources: [The Coffee Workshop]() Topics: [Hugo](), [CSS](), [Sass](), [Code]() Tags: [code](), [css](), [hugo](), [sass](), [script]() ### AI overview This tutorial describes integrating Asciidoctor with Hugo and addressing rendering, syntax highlighting, CSS conflicts, Sass or SCSS overrides, and Font Awesome compatibility issues. ### Source excerpt Integrate Asciidoctor as everyone should expect While Hugo comes with Asciidoctor support, they are in reality several issues to account for at this time: While basic rendering of asciidoc files works, we soon encounter problems ; the very first ## Migrating Right-to-Left CSS Generation from Sass to RTLCSS DevFeed: [Migrating Right-to-Left CSS Generation from Sass to RTLCSS]() Original publisher: [Read original article]() Author: Christoph Reinartz Follow Published: 2017-07-07T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [CSS](), [migration](), [PostCSS](), [Sass](), [Automation]() Tags: [automation](), [configuration](), [css](), [frontend](), [migration](), [sass]() ### AI overview The article explains trivago's migration of right-to-left CSS generation from Sass mixins and variables to RTLCSS post-processing. It describes the motivations, including reducing source complexity, avoiding manual authoring errors, and removing shared RTL configuration requirements, along with the move to a Node-based PostCSS build stack. ### Source excerpt Our first [right-to-left platform](https://www.trivago.co.il/) was released in 2014. We had developed a solution to generate right-to-left CSS with Sass mixins and variables as we have [described](https://tech.trivago.com/2015/04/27/right-to-left/) in a blog article. We used this approach for nearly 3 years but recently migrated the right-to-left CSS generation from pre-processing to post-processing with [RTLCSS](http://rtlcss.com/). With this article I would like to share the reasons for the migration as well as our experiences and lessons learned. ## React and Redux, Webpack 2 boilerplate DevFeed: [React and Redux, Webpack 2 boilerplate]() Original publisher: [Read original article]() Author: Stanko Published: 2016-11-24T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Boilerplate](), [React](), [Webpack](), [Redux](), [Babel](), [React Router](), [Sass](), [file](), [npm]() Tags: [babel](), [boilerplate](), [dev-tools](), [development](), [npm](), [react](), [react-router](), [redux](), [sass](), [webpack]() ### AI overview The article introduces a minimal React application boilerplate built with Redux and Webpack 2. It explains that the author extracted the boilerplate from a pet project after finding Webpack 1.x difficult to configure, and lists implemented, planned, and possible future features. ### Source excerpt Currently, I'm working on a relatively small pet project. While setting it up, I decided to extract a webpack boilerplate from it. As whole JS community is moving really fast, I found very hard to set everything up using Webpack 1.x. One package would ask to update the other, that would break the third one, then that one... and so on. Luckily, I was able to set everything up using Webpack 2. It is still in beta, but I had no problems so far. You can find the boilerplate on GitHub. Implemented Features # React React router Redux Redux Thunk Immutable reducer data Webpack 2 (development and production config) Hot Module Replacement Babel - static props, decorators SASS with autoprefixing Webpack dashboard Linting Included es6-promise and isomorphic-fetch File imports relative to the app root Planned features # Redux Dev Tools Generating icon font from SVGs Preview production build Git hooks - lint before commit (or push) Future features # Universal may be added at some point. Universal rendering Server async data About # This boilerplate is a complete, but minimal React application. It includes reducers (redux), actions (sync and async), routing, SASS... My goal was to be ready immediately after cloning the repo (and running npm i). My plan is to reuse this as much as possible. It will updated so make sure you follow the documentation on GitHub. ## Implementing PhotoShop font sizes and tracking in CSS, points to pixels conversion DevFeed: [Implementing PhotoShop font sizes and tracking in CSS, points to pixels conversion]() Original publisher: [Read original article]() Author: Stanko Published: 2016-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [CSS](), [Sass](), [modern web development]() Tags: [conversion](), [css](), [function](), [mixins](), [photoshop](), [pixels](), [points](), [sass](), [scss](), [tracking]() ### AI overview A tutorial on converting Photoshop font sizes from points to CSS pixels and translating Photoshop tracking into CSS letter spacing using Sass functions and mixins. It explains when to use each construct and provides example Sass and generated CSS. ### Source excerpt We've all been there - trying to get right font sizes from PhotoShop to CSS. Designers usually work with points, which are used in the print, but not common on the web. They also use term tracking a lot, which is actually only a letter spacing with different units. You can recalculate everything by hand and try to keep track of it. But we can use the goodies of SCSS to make that process a bit easier. Point to pixel ratio is 1pt = 1.333333px. We'll create SASS function to do conversion for us. And PhotoShop tracking works relative to the font size. One point of tracking is 1/1000 of the font size. For this one we'll create a mixin. // Converts pt to px @function pt-to-px($size-in-points){ @return #{ round($size-in-points * 1.333333) }px; } // Adds letter spacing to match photoshop tracking @mixin tracking($ps-tracking){ letter-spacing: #{ $ps-tracking / 1000 }em; } // Usage .Component { @include tracking(-5); font-size: pt-to-px(20); line-height: pt-to-px(30); } This will generate following CSS: .Component { letter-spacing: -.005em; font-size: 15px; line-height: 23px; } Note that function and mixin can do pretty much the same job. But it makes more sense to use mixins when including complete styles, and functions to return values. So conversion makes sense to be a function, as we can use it for font size, line height or anything else. Conversion of tracking to letter spacing is including a specific style, so keep it in a mixin. ## SASS random() and circle animation DevFeed: [SASS random() and circle animation]() Original publisher: [Read original article]() Author: Stanko Published: 2016-08-30T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Sass](), [CSS](), [modern web development](), [function]() Tags: [animation](), [css](), [js](), [sass]() ### AI overview A CSS-only circle animation uses JavaScript to create 50 elements and demonstrates Sass's random() function. The article explains its range behavior, examples using positive and negative offsets, and how generated values remain static in CSS until the next Sass compilation. ### Source excerpt I decided to move my CSS playground to the CodePen, and this is the first one I made. Idea came to me while I was riding on a bus, and I might use it on this blog, as a part of it's redesign. This is CSS only animation (I used JS to create 50 elements though). And you can see the usage of SASS random() function. random() will return random integer between 1 and n, where n is the number you pass to it. Default param is 100. Note that random does not return 0. To get different random ranges just add or subtract your base. This will return number between 11 and 20. $random-number: random(10) + 10; Same thing with negative numbers, this one covers the range between -10 and 10. $random-number: random(21) - 11; Something to have in mind, new random numbers will be generated on every SASS compilation. But once generated, CSS will stay static, until the next compilation. ## Setting up Webpack, Babel and React from scratch - Part 2 DevFeed: [Setting up Webpack, Babel and React from scratch - Part 2]() Original publisher: [Read original article]() Author: Stanko Published: 2016-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Webpack](), [Babel](), [Sass](), [React](), [es6](), [JavaScript](), [Web Development]() Tags: [babel](), [compiler](), [css](), [es6](), [javascript](), [react](), [sass](), [webpack]() ### AI overview Part two of a tutorial on setting up Webpack, Babel, and React covers adding SASS support, source maps, Autoprefixer, hot reloading, and additional ES6 features such as static class properties and decorators. ### Source excerpt Part two # Update: Part two is pretty much done. Part three will cover redux and production builds. Other parts: Part 1 - Webpack, Babel, React, Router, ESLint Part 2 - SASS, More ES6 goodness (Static props, decorators, deconstruction...) Part 3 - Where to go from here Adding SASS # We will use SASS loader for webpack, so let's install it together with node-sass compiler, css and style loaders npm install --save-dev style-loader css-loader sass-loader node-sass Create scss folder in the app folder, and main app.scss file in it. This file will include all of the other scss files. Now we need to add a loader to webpack config file. ... { test: /\.scss$/, loader: 'style!css!sass' } ... This will handle importing SCSS files in our JavaScript code. So we need to import app.scss manually in the JavaScript code. You'll need to add only one line to your app.js. import '../scss/app.scss'; This includes your styles by calling loaders we defined in the webpack config. Restart your webpack, and voala, now we have styles and hot reloading for them. Try changing your styles to check it. Source maps # To enable source maps, we'll pass the sourceMap option to the sass and the css loaders. Enable devtool, and update the loader ... devtool: 'inline-source-map', // or 'source-map' module: { loaders: [ ... { test: /\.scss$/, loader: 'style!css?sourceMap!sass?sourceMap', } ] } ... If you want to read more, here's link to the official documentation Autoprefixer # Always use autoprefixer - I can't stress this enough. We'll need postcss loader, precss and autoprefixer npm install --save-dev postcss-loader precss autoprefixer At the top of our webpack config, require precss and autoprefixer const precss = require('precss'); const autoprefixer = require('autoprefixer'); Update our sass loader config and and postcss config ... module: { loaders: [ ... { test: /\.scss$/, loader: 'style!css?sourceMap!postcss!sass?sourceMap', } ] }, postcss() { return [autoprefixer, precss]; }, ... Restart webpa ## Lessons Learned at IBM Design DevFeed: [Lessons Learned at IBM Design]() Original publisher: [Read original article]() Published: 2016-04-12T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [ibm](), [Front end](), [front-end-development](), [Testing](), [Sass](), [Git]() Tags: [engineering](), [front-end](), [front-end-development](), [git](), [ibm](), [sass](), [testing]() ### AI overview A retrospective on lessons learned during nearly two years at IBM Design, focusing on enthusiasm for collaboration, interdisciplinary rapport, and an iterative design process of building, testing, and refining solutions. ### Source excerpt I've learned so much during my time at IBM Design! This is a little wrap up post and an announcement about my next adventure. ## Jekyll and Gulp workflow DevFeed: [Jekyll and Gulp workflow]() Original publisher: [Read original article]() Author: Stanko Published: 2016-02-27T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Gulp](), [Jekyll](), [Sass](), [JavaScript](), [Development](), [es6]() Tags: [development](), [es6](), [gulp](), [javascript](), [jekyll](), [sass](), [workflow]() ### AI overview This tutorial describes a Jekyll development workflow that uses Gulp to compile and watch SASS and JavaScript, run a local Jekyll server, proxy it through BrowserSync, and reload the browser on changes. The author notes that the setup may be outdated because they no longer use Jekyll. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. Update, November 2017 # I don't use this setup anymore, it might be outdated, proceed with caution. Original post # As you probably know this blog is powered by Jekyll. It is a really nice platform, but it lacks a few things I'm used to during development. First one is live reload on file changes (and injecting CSS), using SASS, autoprefixer, ES6... I tried to find a boilerplate, but everything I found didn't match my needs. Usually people would run gulp tasks for SASS and JavaScript files, and on change run jekyll build, which is insanely slow. They would use BrowserSync to serve _site folder. So I did what programmers do - written my own. I quickly made usual gulp tasks: styles - to compile SASS and autoprefix it scripts - to transpile ES6 goodness, and concatenate JavaScript files serve - to start local server, watch for changes and auto reload First thing I did is that I was running jekyll serve in one terminal, and gulp serve with BrowserSync in the other. This was working decently, but I wanted to run only one command, and let the tasks do everything for me. That is where node child process comes in. import childProcess from 'child_process'; const spawn = childProcess.spawn; gulp.task('jekyll', function (){ const jekyll = spawn('jekyll', ['serve'], { stdio: 'inherit' }); }); This task spawns a child process from gulp. Nice thing is that we can start it, and gulp will kill it on exit. Now we have up and running Jekyll server, and proxy it to BrowserSync. But darn, injecting CSS files didn't really work. Server was expeting CSS file to come from /css/style.css, but browserSync.stream in gulp pipe would inject it from the _sass folder. I solved this by copying css file to the .tmp/css and adding .tmp to the serveStatic option of the BrowserSync. One thing I should mention, that I keep my SASS files in the _sass folder, and JavaScript in the _js one. Gulp watches changes on SASS/JS, and ## If You Know Sass, You Know ES2015 DevFeed: [If You Know Sass, You Know ES2015]() Original publisher: [Read original article]() Published: 2016-02-23T00:00:00Z Content type: comparison Language: en Sources: [Una Kravets]() Topics: [Sass](), [es6](), [JavaScript](), [Babel]() Tags: [babel](), [es2015](), [javascript](), [programming-language](), [sass]() ### AI overview This article compares Sass and ES2015, explaining how familiarity with Sass concepts can help developers understand modern JavaScript. It discusses language design similarities, string interpolation, and using Babel to transpile ES2015 for browser compatibility. ### Source excerpt If you know some Sass, you're probably a lot further than you think to understanding and diving into the world of modern JavaScript. This post showcases some of the similarities. ## Hello World DevFeed: [Hello World]() Original publisher: [Read original article]() Author: Stanko Published: 2016-02-21T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Development](), [JavaScript](), [CSS](), [Sass](), [Script]() Tags: [blog](), [css](), [development](), [javascript](), [plugin](), [sass](), [script]() ### AI overview The blog introduces a planned series of weekly small JavaScript or CSS (SASS) plugins and scripts, ranging from proof-of-concept experiments to production-ready work. ### Source excerpt Everything starts with a Hello World so does this blog. In the first couple of weeks, everything will be under heavy development, until I get it the way I want. As I really enjoy making stuff, I decided to try to make small JavaScript or CSS (SASS) plugin/script every week. Those are going to be both big and small, proof of concepts and production ready stuff. ## 2015 Year In Review & 2016 Resolutions DevFeed: [2015 Year In Review & 2016 Resolutions]() Original publisher: [Read original article]() Published: 2015-12-28T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [Development](), [Front end](), [Sass](), [Gulp](), [Web Development](), [Open Source](), [dev-tools]() Tags: [css](), [developer](), [development](), [github](), [guide](), [retrospective](), [sass](), [year-in-review]() ### AI overview A personal retrospective of 2015 projects, talks, writing, podcasts, and work at IBM, followed by resolutions for 2016. The article highlights web and front-end experiments, Sass and Gulp tools, CSS libraries, pattern libraries, prototypes, and community activities. ### Source excerpt It's time for my annual reflection and goal resetting! It's been a crazy year for sure. ## Why I'm Excited About Native CSS Variables DevFeed: [Why I'm Excited About Native CSS Variables]() Original publisher: [Read original article]() Published: 2015-12-06T20:43:53Z Content type: opinion Language: en Sources: [Philip Walton]() Topics: [CSS](), [Web platform](), [Chrome Canary](), [Sass](), [Chrome](), [Web Development]() Tags: [chrome-canary](), [css](), [experimental](), [feature](), [platform](), [sass](), [web](), [web-platform]() ### AI overview The article argues that native CSS Custom Properties are fundamentally different from Sass variables. It explains that Custom Properties are dynamic CSS properties scoped to the DOM, enabling capabilities and design patterns that preprocessors cannot provide, while suggesting that developers may use both approaches together. ### Source excerpt A few weeks ago CSS variables--more accurately known as CSS Custom Properties--shipped in Chrome Canary behind the Experimental Web Platform Features flag.[1] When Chrome engineer Addy Osmani first tweeted about the release, he was met with a surprising amount of negativity, hostility, and skepticism. At least, it was surprising to me, given how excited I am about this feature. ## Classy CSS: a Programmatic Approach to Sass Stylesheets DevFeed: [Classy CSS: a Programmatic Approach to Sass Stylesheets]() Original publisher: [Read original article]() Published: 2015-11-15T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [CSS](), [Sass](), [modern web development](), [Front end]() Tags: [architecture](), [components](), [css](), [libraries](), [modular](), [properties](), [sass](), [variables]() ### AI overview An opinionated article introduces Classy CSS, a programmatic, modular, scalable, and class-based architecture for Sass stylesheets. It explains the approach through a button example and discusses its relationship to BEM-like naming and Sass features. ### Source excerpt An opinionated Sass architecture system for writing modular and scalable libraries. Also, a case in defense of extends. ## Sass Pixel Art DevFeed: [Sass Pixel Art]() Original publisher: [Read original article]() Published: 2015-05-03T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [Sass](), [HTML5 and CSS3 tricks](), [pixel](), [Programming]() Tags: [blog-post](), [css3](), [how-to](), [pixel-art](), [sass]() ### AI overview This tutorial explains how Sass lists, matrices, maps, and list functions can generate pixel art using CSS3 multiple box shadows. It examines how individually positioned box shadows form pixels and how Sass data structures organize them. ### Source excerpt Pixel art is so much fun! This blog post walks through how to read a matrix-like list with Sass and generate Mario pixel art from box shadows. ## My favorite old webdev tools DevFeed: [My favorite old webdev tools]() Original publisher: [Read original article]() Published: 2015-04-09T00:00:00Z Content type: opinion Language: en Sources: [Adam Bard]() Topics: [Web Development](), [Flask](), [Django](), [static-site-generator](), [Sass](), [CSS Framework](), [Clojure]() Tags: [clojure](), [css](), [django](), [flask](), [frameworks](), [sass](), [static-site-generator](), [tools](), [webdev]() ### AI overview An opinionated roundup of older web development tools the author has used for years. It discusses Middleman for generating static sites, Skeleton for lightweight CSS prototyping, Flask for small sites, and Django for applications that benefit from an all-in-one framework; it also mentions Clojure for high-performance API servers. ### Source excerpt The way we make websites has changed a lot since I started doing it, and it's important to keep up-to-date on new tools and techniques. That said, I've been noticing that I've not spent as much time churning through new frameworks and whatnot as I used to - in fact, I've picked out a few tools that I've been using for years. ## 5 Great Uses for Sass Maps DevFeed: [5 Great Uses for Sass Maps]() Original publisher: [Read original article]() Published: 2015-03-17T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [Sass](), [Code]() Tags: [blog-post](), [sass]() ### AI overview A SitePoint blog post covering five uses for Sass maps, along with thoughts on code. ### Source excerpt Another blog post written for SitePoint about 5 great uses for Sass maps and other thoughts on code at the moment. ## Sass Director and Manifest Files DevFeed: [Sass Director and Manifest Files]() Original publisher: [Read original article]() Published: 2015-01-18T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [Sass](), [Command-line interface](), [Code]() Tags: [build](), [files](), [manifest](), [project](), [sass](), [shell-script](), [terminal]() ### AI overview This tutorial explains Sass manifest files, which bring partial Sass files together in a main file that compiles into a cumulative CSS output. It also introduces Sass Director, a tool that generates the directories and partial files for a Sass project from one manifest file. ### Source excerpt I created a tool that lets you architect your Sass project in a single location (your manifest file), and it will build all of the directories and partials for you! This blog explains what a Sass manifest file is, what it does, and why you should use one. ## Jekyll with Sass DevFeed: [Jekyll with Sass]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-01-09T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Jekyll](), [Sass](), [GitHub Pages]() Tags: [article](), [github-pages](), [jekyll](), [sass]() ### AI overview A blog post describes applying Sass to a Jekyll site to reduce four CSS requests totaling about 22K to one request of 12.8K. The author also reports that the approach works on GitHub Pages. ### Source excerpt I followed @mdo's recent article "Using Sass with Jekyll", and wanted to point out the results. ## 2015 Resolutions DevFeed: [2015 Resolutions]() Original publisher: [Read original article]() Published: 2014-12-31T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [JavaScript](), [Node.js](), [Sass](), [Gulp](), [Open Source](), [Angular](), [Command-line interface](), [Express](), [Meteor](), [Testing](), [Vim](), [WebGL]() Tags: [3d-graphics](), [angular](), [blog](), [command-line](), [express](), [github](), [javascript](), [make](), [node-js](), [open-source](), [personal](), [post](), [published](), [review](), [sass](), [testing](), [vim](), [webgl]() ### AI overview A personal review of 2014 and a set of goals for 2015. The author describes projects, travel, speaking, open-source contributions, and progress in JavaScript, Sass, Gulp, Meteor.js, Express.js, Angular, Node.js, testing, Vim, WebGL, and 3D graphics. ### Source excerpt This is a personal post about my 2014 in review (because a lot happened) and my goals for 2015. Happy New Year! ## ATX Sass DevFeed: [ATX Sass]() Original publisher: [Read original article]() Published: 2014-11-13T00:00:00Z Content type: release Language: en Sources: [Una Kravets]() Topics: [Sass](), [Website]() Tags: [meetup](), [sass](), [website]() ### AI overview The Austin's Sass Meetup has launched a new website. ### Source excerpt Our new website for Austin's Sass Meetup is live! ## Sass Bites #33: Una Kravets DevFeed: [Sass Bites #33: Una Kravets]() Original publisher: [Read original article]() Published: 2014-04-10T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [Sass]() Tags: [sass]() ### AI overview Una Kravets says she appeared on Sass Bites this week. ### Source excerpt I was on Sass Bites this week! ## Set up Flask with webassets DevFeed: [Set up Flask with webassets]() Original publisher: [Read original article]() Published: 2014-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Adam Bard]() Topics: [Flask](), [Python](), [Sass](), [jQuery](), [npm]() Tags: [css](), [flask](), [npm](), [python](), [sass]() ### AI overview A step-by-step tutorial for setting up a new Flask application with Python, Sass, CoffeeScript, Flask-Assets, webassets, Bower, and jQuery. It covers installation, project structure, asset bundles, preprocessing, and serving compiled static assets. ### Source excerpt Flask isn't new, but it's really great, and it's definitely my first choice when starting a new Python app. Today I want to give you a quick tour of the tools I use to set up a new Flask app. [Next page]()