As of today we have a new 9elements website. Whereas the old one was quickly put together to deliver an impression of our company culture, we put a lot more effort in developing this site. We now have a decent place where people see the cool projects we’ve worked on and also get an insight on how we work. But not only the content is fresh – with the release of our new website, we revamped our complete production toolchain.
ZOMG – It’s coffee all over the place!
So where do we go now?
When we developed the website we’ve realized that there is a lot of redundancy in the code. As example I’ll take the project model. So how do I get it to the client?
- You’ll write it in Rails, tweaking the as_json method since you’ll have to incorporate all images into the JSON hash.
- You’ll write a model for Backbone.js
- You’ll write a collection for Backbone.js
- You’ll create a view…
- …and a template where the data will be finally rendered.
If you repeat that steps for the other models you’ll get the feeling, that the web development is terribly broken at the moment. There must be a more DRY approach on realizing this. I’m thinking of switching from Rails to Node.js and implementing models that can be used on the server and on the client. But this is another step, for now we just established a very cool toolchain for views and templates.