jdsteinbach

$global_store: ()

= override($args:(), $is_child:true)
  @if $is_child
    $global_store: () !global
  $global_store: map-merge($global_store, $args) !global

= default($key_or_map, $value:null)
  @if $value
    +store-default($key_or_map, $value)

koistya

Single-page Application Project Structure

..with .NET / F# (or Node.js / Express), AngularJS (or Facebook React + RxJS), TypeScript, Gulp.js (or Grunt), NuGet...

Goals

• Project structure should reflect application's logic (as opposed to regular MVC apps which all look the same)
• Group assets by feature rather than by type (including views, scripts, documentation, tests etc.)
• Allow developers to edit client-side and server-side code independently from each other

nathancrank

// ----
// Sass (v3.3.0.rc.1)
// Compass (v0.13.alpha.10)
// ----

$E:     2.718281828459045;
$PI:    3.141592653589793;
$LN2:   0.6931471805599453;
$SQRT2: 1.4142135623730951;

lancejpollard

What is your folder-structure preference for a large-scale Node.js project?

0: Starting from Rails

This is the reference point. All the other options are based off this.

|-- app
|   |-- controllers
|   |   |-- admin

parrfolio

body {
 background: #444;
}

h2 {
font-size:68px;
color:#f1f1f1;
position:relative;
z-index:1;
font-family:helvetica, arial, sans-serif;