Christo Christo44

## eslint-package-json.js
	"prettier": {
		"useTabs": true,
		"semi": false,
		"singleQuote": false,
		"bracketSpacing": true,
		"trailingComma": "es5",
		"printWidth": 160
	},
	"eslintConfig": {
		"parserOptions": {

## addtogcal.php
<?php
 /**
  * Create a Google Calendar "add to calendar" link.
  *
  * This function is convienient because it does not require an API connection.
  * Note that this only allows for adding a single event.
  * The data does not have to exist already on any Google Calendar anywhere.
  * This just adds your event data to the end-users GCal one item at a time.
  * See https://stackoverflow.com/a/19867654/947370 for a full explaination of
  * the Google Calendar URL structure.

## package.json
{
  "name": "project-name",
  "description": "Template for static sites",
  "version": "1.0.0",
  "homepage": "http://www.project-name.com",
  "author": {
    "name": "Adam Reis",
    "url": "http://adam.reis.nz"
  },
  "license": "UNLICENSED",

## gist:d75101d9bdf764c890ef
# first:
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom | while read f; do  sudo rm /usr/local/${f}; done
sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

# go to /usr/local/lib and delete any node and node_modules
cd /usr/local/lib
sudo rm -rf node*

## controllers--contact.php
<?php

return function($site, $pages, $page) {

  $alert = null;

  if(get('submit')) {

    $data = array(
      'name'  => get('name'),

## fix-homebrew-npm.md

      
              1 file
            
          
              177 forks
            
          
              361 comments
            
          
              1614 stars
            
          
                DanHerbert
                / fix-homebrew-npm.md
            
            
              Last active
              June 4, 2024 04:16
            
              
                Instructions on how to fix npm if you've installed Node through Homebrew on Mac OS X or Linuxbrew
              
          
    OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

  
## gulpfile.js
var gulp        = require('gulp'),
    gutil       = require('gulp-util'),
    sass        = require('gulp-sass'),
    csso        = require('gulp-csso'),
    uglify      = require('gulp-uglify'),
    jade        = require('gulp-jade'),
    concat      = require('gulp-concat'),
    livereload  = require('gulp-livereload'), // Livereload plugin needed: https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei
    tinylr      = require('tiny-lr'),
    express     = require('express'),

## SCSS.md

      
              1 file
            
          
              264 forks
            
          
              90 comments
            
          
              1745 stars
            
          
                jareware
                / SCSS.md
            
            
              Last active
              May 19, 2024 14:03
            
              
                Advanced SCSS, or, 16 cool things you may not have known your stylesheets could do
              
          
    ⇐ back to the gist-blog at jrw.fi
Advanced SCSS

Or, 16 cool things you may not have known your stylesheets could do.  I'd rather have kept it to a nice round number like 10, but they just kept coming.  Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein).  It really helped many of us through the darkest cross-browser crap.  Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger.  SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso

  
## html-head-boilerplate.html
<!doctype html>
<html>
  <head>
    <!-- Priority tags. These must come first. -->
    <meta charset="utf-8">
    <meta http-equiv="x-ua-compatible" content="ie=edge; chrome=1"> <!-- Render Chrome if available or using latest version of Internet Explorer (Recommended). -->
    <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no">
    <!-- Document Title -->
    <title>Page Title</title>
    <!-- Allows control over where resources are loaded from. Place as early in the document as possible, only applies to content below this tag. -->
	"prettier": {
	"useTabs": true,
	"semi": false,
	"singleQuote": false,
	"bracketSpacing": true,
	"trailingComma": "es5",
	"printWidth": 160
	},
	"eslintConfig": {
	"parserOptions": {
	<?php
	/**
	* Create a Google Calendar "add to calendar" link.
	*
	* This function is convienient because it does not require an API connection.
	* Note that this only allows for adding a single event.
	* The data does not have to exist already on any Google Calendar anywhere.
	* This just adds your event data to the end-users GCal one item at a time.
	* See https://stackoverflow.com/a/19867654/947370 for a full explaination of
	* the Google Calendar URL structure.
	{
	"name": "project-name",
	"description": "Template for static sites",
	"version": "1.0.0",
	"homepage": "http://www.project-name.com",
	"author": {
	"name": "Adam Reis",
	"url": "http://adam.reis.nz"
	},
	"license": "UNLICENSED",
	# first:
	lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom \| while read f; do sudo rm /usr/local/${f}; done
	sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

	# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

	# go to /usr/local/lib and delete any node and node_modules
	cd /usr/local/lib
	sudo rm -rf node*
	<?php

	return function($site, $pages, $page) {

	$alert = null;

	if(get('submit')) {

	$data = array(
	'name' => get('name'),
	var gulp = require('gulp'),
	gutil = require('gulp-util'),
	sass = require('gulp-sass'),
	csso = require('gulp-csso'),
	uglify = require('gulp-uglify'),
	jade = require('gulp-jade'),
	concat = require('gulp-concat'),
	livereload = require('gulp-livereload'), // Livereload plugin needed: https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei
	tinylr = require('tiny-lr'),
	express = require('express'),
	<!doctype html>
	<html>
	<head>
	<!-- Priority tags. These must come first. -->
	<meta charset="utf-8">
	<meta http-equiv="x-ua-compatible" content="ie=edge; chrome=1"> <!-- Render Chrome if available or using latest version of Internet Explorer (Recommended). -->
	<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no">
	<!-- Document Title -->
	<title>Page Title</title>
	<!-- Allows control over where resources are loaded from. Place as early in the document as possible, only applies to content below this tag. -->