Design direction is great, but CSS seems to be broken — http://i.imgur.com/ITbIVhI.png Maybe is should look like http://i.imgur.com/GdovVOF.png

Btw, they use bem-like css approach and rem units (bravo!) and horrible float blocks (dunno if it's some super duper css grid, hard to figure out)

My styleguide very similar to @mdo http://markdotto.com/2014/07/23/githubs-css/ Of course, with Sass. CSS architecture is based on BEM and OOCSS — it works well on projects of any size.

Awesome Buy button http://i.imgur.com/sRXW3gA.png

Of course, I understand that. Just wanted to show what user gets as a result. — it's some kind of reminder about the fact that articles are made to be read, not filled with shiny share buttons and giant advertising blocks. I just press one button to strip it all away, so in my case all that design done seems to be just wasted time and money.

it's because everyone wants to become a great designer without doing dirty work

If you code yourself, Middleman (for static sites) and Livereload are useful tools. I open browsers in iOS simulator, Android virtual device and desktop, and every code change causes a page refresh everywhere.

I don't think refusing from bootstrap classes is great idea for everyone. When you work on front-end code alone, it's okay. But if there's a team of developers (not too familiar with css and sass) you work with, naming elements with custom classes causes a development slow-down — Bootstrap (as any other popular framework) is some kinda language that everyone understand.

I usually name elements like .container.welcome-block-background — use bootstrap classes and my own classes that extend and redefine element appearance. Bootstrap-sass is built with !default flags, so redefining its styles is not a problem.

I try to get working in code as soon as possible, so prototyping doesn't take much time in my process.

I spend three or four hours on first drafts to get time estimates and find out application complexity — this helps to define project budget range.

After that wireframing takes from one day to about a week (depending on project complexity). Further thinking and refining are made in a working prototype (or an app) already. When using agile and scrum it doesn't become a problem.

I've posted an article about my wireframing process here about a month ago, maybe it'll be interesting for you.

Thanks, this case is really great! I though about implementing a transition to nested elements with back button.

Great idea. Maybe it'd be better to take projects data from Watsi (via API or by parsing necessary pages — with their permission, of course)?