Skip to content

Instantly share code, notes, and snippets.

View pixelite's full-sized avatar

Suzanne Dergacheva pixelite

20 followers · 1 following
View GitHub Profile
@pixelite
pixelite / Vagrant-sphinx-pdflatex.md
Last active March 14, 2018 15:11
Creating a Vagrant vm with sphinx and pdflatex

First create a Vagrantfile:

vagrant init precise64

Then add the following to the new Vagrantfile:

config.vm.provision :shell, :inline => <<-EOT
@pixelite
pixelite / eventbrite.html
Last active March 7, 2017 14:38
<div style="width:100%; text-align:left;"><iframe src="//eventbrite.ca/tickets-external?eid=20483772515&ref=etckt" frameborder="0" height="563" width="100%" vspace="0" hspace="0" marginheight="5" marginwidth="5" scrolling="auto" allowtransparency="true"></iframe><div style="font-family:Helvetica, Arial; font-size:12px; padding:10px 0 5px; margin:2px; width:100%; text-align:left;" ><a class="powered-by-eb" style="color: #ADB0B6; text-decoration: none;" target="_blank" href="http://www.eventbrite.ca/">Powered by Eventbrite</a></div></div>
@pixelite
pixelite / redcrow.libraries.yml
Last active June 1, 2016 22:07
open-sans:
remote: https://www.google.com/fonts/specimen/Open+Sans
license:
name: Apache License, Version 2.0
url: http://www.apache.org/licenses/LICENSE-2.0.html
gpl-compatible: true
css:
theme:
https://fonts.googleapis.com/css?family=Open+Sans: { type: external }
font-awesome:
@pixelite
pixelite / suzanne-tools.md
Last active April 1, 2016 17:37 — forked from dergachev/alex-tools.md
The tools I use.

Tools we use for PM for project management and communication

  • LaTeX for company proposals, converted via custom script to google docs
  • git for code and structured docs
  • dropbox for screenshots and file sharing
  • markdown (in github) and textile (in redmine)
  • markdown for blog posts and presentations
  • Vim for code and text editing

Communication:

@pixelite
pixelite / zen-grids.md
Last active February 25, 2016 19:26

#Demo: Creating a Zen Sub-theme and Using Zen Grids

##Add and enable Zen

drush dl zen
drush en zen
drush cc all
@pixelite
pixelite / my-modules.md
Last active December 24, 2015 08:19
Here's a list of modules I would suggest using when you're getting started with Drupal.
@pixelite
pixelite / responsive-training-sep27-snippet1.css
Last active December 24, 2015 02:49
#navigation #main-menu li {
-webkit-border-radius: 7px
-moz-border-radius: 7px;
border-radius: 7px;
background: green;
box-sizing: border-box;
width: 45%;
float: left;
margin: 5px;
padding: 10px 0;
@pixelite
pixelite / fixing-virtualbox-vagrant-error.md
Last active December 19, 2015 14:39

Error message 1

Running vagrant up after upgrading Virtualbox to 4.24 (or something) now gives this error:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'precise64-customized-sk' could not be found.
@pixelite
pixelite / mailfish.install
Created March 27, 2013 19:49
<?php
/******************************************************************************
* Exercise: Creating The mailfish.install File
*****************************************************************************/
/**
* @file
* Defines and manages the MailFish schema.
*/
@pixelite
pixelite / sass.md
Last active November 27, 2015 16:17 — forked from jorgediazgutierrez/sass.md
How SASS and Bourbon Neat Can Save Non-Mobile Websites

How SASS and Bourbon Neat Can Save Non-Mobile Websites

It's 2015, we are already in the "Mobile Era" and we all love how our modern sites fit and adapt to any screen. It's amazing how a website can stretch to the 52 inches of a Samsung TV and also look good on your mobile phone. But you know what? There are 20 years of "non-mobile" websites out there screaming to be upgraded. And the first word that comes to mind is "redesign".

Redesign means Higher Cost

Mobile OS manufacturers tend to improve their browsers to allow resizing, double tap zooming and dragging around, so we can use these non-mobile websites on mobile. But this is just a usability workaround, and only fixes half of the "browser + site = UX" equation. If the businesses behind old sites want to upgrade their "non adaptive" websites, they will need to pay for it. If they have a good budget, they will have a lot of options, but what if they don't?

Instead of leaving websites to "die" because they were made more than 4 years ago, why do