Carlos Matallín matallo

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

Design Hacking — Mi chapa del UX Spain 2015

Hola, mundo

Soy Ale Muñoz. Nací en Sevilla, aunque ahora vivo con mi mujer y mi hija en Madrid, donde trabajo para una empresa holandesa, con un equipo repartido por toda Europa, haciendo software que se usa en todos los rincones del mundo.

Me gusta diseñar, cocinar, y sentarme plácidamente a poner la mente en blanco sin hacer absolutamente nada.

Llevo muchos años ayudando a diseñadores y diseñadoras a trabajar menos, fabricando herramientas para automatizar tareas, definiendo procesos de trabajo, o gestionando proyectos de diseño. Si alguna vez habéis trabajado conmigo es posible que os haya contado algún truco para hacer algo más rápido

In your Vagrant:

cd workspace/cartodb && vagrant up && vagrant ssh cd /vagrant

Create a new user:

bundle exec rake cartodb:db:setup SUBDOMAIN=xatpy EMAIL=xatpy@gmail.com PASSWORD=xatpy SUBDOMAIN=xatpy

Create the new organization (using the new user):

bundle exec rake cartodb:db:create_new_organization_with_owner ORGANIZATION_NAME=theteam ORGANIZATION_SEATS=5 ORGANIZATION_QUOTA=100000000 USERNAME=xatpy

Edit /etc/hosts, adding:

192.168.33.10 theteam.localhost.lan

Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets

Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

	/*
	FILE ARCHIVED ON 3:09:27 feb 10, 2005 AND RETRIEVED FROM THE
	INTERNET ARCHIVE ON 19:57:07 abr 24, 2016.
	JAVASCRIPT APPENDED BY WAYBACK MACHINE, COPYRIGHT INTERNET ARCHIVE.

	ALL OTHER CONTENT MAY ALSO BE PROTECTED BY COPYRIGHT (17 U.S.C.
	SECTION 108(a)(3)).
	*/
	// Copyright 2005 Google
	function ci(vg, Pf, yh) {

	console.log('Loading event');
	var AWS = require('aws-sdk');
	var dynamodb = new AWS.DynamoDB();

	exports.handler = function(event, context) {
	console.log("Request received:\n", JSON.stringify(event));
	console.log("Context received:\n", JSON.stringify(context));

	var tableName = "OurBlogDemo";
	var datetime = new Date().getTime().toString();

	{
	"version": "0.0.1",
	"name": "namedmap_tutorial_14",
	"auth": {
	"method": "open"
	},
	"layergroup": {
	"layers": [{
	"type": "torque",
	"options": {

	require_relative "test_helper"

	require "open-uri"
	require "net/http"

	class EmojiTest < Blog::Test
	def test_no_emoji
	posts.each do \|post\|
	content = File.read(post)
	refute_match /:[a-zA-Z0-9_]+:/, content,

	#!/bin/bash

	# Configuration #############################################

	# For Slack tokens go to https://api.slack.com/#auth
	SLACK_TOKEN=""
	# In seconds
	AWAY_AFTER=120
	CHECK_EVERY=10

	import os
	import urllib
	import urllib2
	import base64
	import json
	import sys
	import argparse
	try:
	import requests
	except ImportError: