Skip to content

Instantly share code, notes, and snippets.

View pixelite's full-sized avatar

Suzanne Dergacheva pixelite

View GitHub Profile
@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 / 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