The tech stack behind Close.io's sales communication platform (YC W11)

blog.close.io

39 points·anemitz··12 comments

This is the "big picture" view of our tech stack. We plan on writing more technical posts about how we work with ElasticSearch, Backbone.js, etc. in the future. Let us know if there are any particular areas you'd like to hear more about.

Would love to learn more about your phone/calling integration.

It's built on pjsip, greenj, and Plivo.com (YC). What would you like to know?

Thank you, this is very useful. I'm more interested in how you managed to use flask for such a big application.

Do you have any conventions for keeping your Backbone code sane?

I'll write more about it soon. But overall using RequireJS modules. Generally one "class" (Model, Collection, or View) per .js file - though helper classes end up in the same file.

Have a different environment for dev vs. production to make dev easy and production fast. In dev handlebars templates are fetched/parsed on the fly. On production they are precompiled.

Overall I like most of what's found here: https://github.com/tbranyen/backbone-boilerplate

Also using a few base classes and plugins to keep things DRY.

I knew I recognized that theme: http://wrapbootstrap.com/preview/WB0D95984

yep we started from that for our blog/landing page. so what?

I really like that one - was considering purchasing it for a project. Granted, you guys modified it quite a bit. I'm also looking into close.io for my sales. : )

Heads-up: Design is a little bit broken (content column not centered, dot in front of headline) in FF19.0.2 on Win7.

thanks, too much webkit-only testing. will fix.

Great, it's fixed now.

Reply on news.ycombinator.com