Your project . The Gizra Way

About Us

Gizra is a boutique development shop in Tel Aviv, established in 2009 and employing 17 developers.

Gizra's work focuses on Open Source technologies: We've created and maintain key Drupal modules such as RESTful, Organic Groups, Message and Entity Reference, and take part in maintaining Drupal core, as well as state of the art technologies like Node.js, D3, Angular, Jekyll and others.

At Gizra we've developed an approach we call The Gizra Way, a radically transparent way of working, but technologically and project management-wise. Every Gizra project is tracked in GitHub with all code and tasks open to all stakeholders from day one. Every piece of code is peer-reviewed and covered by automatic tests. Stakeholders are encouraged to communicate directly with developers working on their code via GitHub Issues.

Gizra developers set aside an hour each day for community contributions: fixing bugs on open source projects, blogging about new code and method we developed and working on public-benefit software projects. We make a point of taking part in the developer community, presenting in Open Source camps and conventions worldwide.

See The Team

Work

From e-Commerce to community sites.

Commerce Kickstart

A collaboration with Commerce Guys, Commerce Kickstart is built on top of Drupal Commerce making it easier to admin and faster while adding multiple features.

Imanimo

Maternity fashion catalog and eCommerce website

Drupal Commons

We collaborated with Acquia Inc to create this social community focused Drupal distribution, complete with a user friendly interface and built in groups / activity streams support.

OpenScholar

Drupal distribution designed for higher education, allowing academic institutions to run all their staff, department and project websites on a single installation. Developed by Harvard in collaboration with Gizra, used at Princeton, Berkeley, Virginia Tech and more.

Our code

At work

Our code contribution has reached over 100K sites.

Blog

14 Jul 2014

In our last example we showed how to create node using an angular form served from Drupal itself. This time we are taking one big step further and create the node from a completely decoupled web app.
And if that's not enough for the readers excited by the idea of a decoupled Drupal, we've also added inline editing to the example!

Enjoy the live demo

If you know Form API's pains, you should be excited now
10 Jul 2014

When we started working on a mobile web site for Casa del Lector's exhibition, we decided early on it would be a backend-free app, mainly for reasons of stability and performance:

App is faster than 96% of other websites

The data was entered by the client on a 3rd party desktop tool which exported it to XML. We used a bunch of open source tools to massage it a bit and prepare it for the App. Since the project is open sourced you can check out the actual code.

The App in action
09 Jul 2014
  • Form API is great, but Form API is hard when you try to do fancier stuff - like wizards and other things that clients often want.
  • Angular forms are great, but Angular forms are hard too - you need to write your own custom endpoints and server side validation.

But now that RESTful integrates with Entity Validator, I would change the equation and simply say something rarely heard in the Drupal community: Forms are Fun!

This form is not Form API, it's angular!

Go ahead, try it yourself on simplyTest.me

01 Jul 2014

Treat your custom CSS as contrib

Getting your Drupal to be pixel perfect is hard. In fact, it's probably four times faster to write the logic of a page, in comparison to the time it takes to get it's markup right. Not to talk about making it responsive.

If you've seen my presentation about The Gizra Way you noticed we take pixel perfect very seriously.

One of the tools that helps us getting the markup fast, correct and in a way that would allow us to communicate with the client is Jekyll - the static site generator. Here's the idea in a nutshell:

  • Using Jekyll we can concentrate on a clean markup
  • Using Grunt we compile the SASS, and are able to push the the HTML into Github pages - where the client can easily see and interact with the final markup
  • The CSS produced by Jekyll is treated by our Drupal application as contrib. This means we have zero custom CSS in our theme. Seriously, absolutely no custom CSS in your Drupal theme!
  • Any change to the CSS can be done only in a single place, which is Jekyll

Contact Us

5 Brenner St., Tel-Aviv, Israel
+972-3-3731222