At Savas Labs, we are a forward-looking bunch, much like our neighbors around the corner from our Durham office, The Republik, who wear that badge a little more… overtly:
Though future-focused-first, we also recognize the importance of history and the value of a little reflection. After all, we must learn from our mistakes to truly thrive.
Know from whence you came. If you know whence you came, there are absolutely no limitations to where you can go. - James Baldwin
Aside: I can’t recommend the award-winning documentary about James Baldwin’s legacy I am not your negro strongly enough. See it.
From whence we came…
Savas Labs matured substantially in 2016, refining processes and adding new team members who brought complementary skills. It’s both intriguing and humbling to reflect on just how much we learned in the past year. It wasn’t all puppy dogs and ice cream, but the successes and the challenges helped us carve out our place in the world. We worked with consultants, analyzed and soul-searched to elicit what it is we love doing and are really good at as a growing team. One manifestation of these pursuits was the establishment of our core values. They help hold us and future Savasians (coining the demonym Savasian - another thing we did in 2016) accountable to an agreed upon set of principles which drive how we treat one another and our partners.
In addition to internal analysis, we studied our best projects to see what characteristics in partners and their challenges for which we are best fit. We uncovered that what we enjoy most and truly excel at are projects with strategic and complex needs that lean heavily on our deep Drupal expertise usually requiring inter-departmental engagement within organizations.
Ergo: our positioning statement that appears front-and-center on our homepage:
We craft elegant Drupal web systems that propel organizations
Why the redesign
You know, the typical reason, because we wanted to . In truth, we were due for a redesign as the last time we did this was over two years ago. Additionally, given our growth, we felt our website did not reflect the quality of work we’ve been doing. As we updated our message, we recognized copy updates alone would be insufficient to demonstrate our capabilities. In the process, we took advantage of the artistic skillset of one of our 2016 additions to the team, Oksana Cyrwus, to create a vision of our team’s identity.
Although we’re usually building client websites in Drupal, we chose to continue with the static site generator Jekyll which we’ve written about before as our platform. We believe firmly in using the right tool for the job and use a multitude of technologies, frameworks and programming languages in any given
Be aware that other tools exist and that they may be better suited for certain tasks.
Ultimately, for us, the benefits outweighed the drawbacks:
- No database back-end, meaning reduced security threats and reduced hosting complexity. We’re able to host for free on GitHub Pages.
- A highly-performant framework.
- Ease of deployment.
- Efficient for our workflow as it is developer oriented.
- Requires Ruby ecosystem competency which often presents the need to acquire new skills for Drupalers.
- Requires developer-level skills to update.
- Not as robust of an ecosystem as Drupal for example.
- Example: When we were dissatisfied with our comment options, we built our own server on guess what, a different framework. This took us time and is less feature-rich than what we’d get with Drupal out of the box.
These drawbacks, though not without their costs, are also opportunities for us to be a part of the broader web ecosystem and learn. The more exposure to best-practices and other frameworks, the more we can borrow from and employ them in our work, though it is an investment to develop the expertise.
Jekyll works for us since the team of savvy Savasians is comfortable rapidly learning a new workflow to publish updates to our website. Additionally our website needs are relatively simple, certainly compared to the needs of many of our partners. Our partners often have personnel with a wide range of technical training and often require sophisticated content models, granular authentication and permissions, advanced content publishing workflows among many other common needs for which a modular ecosystem of plugins like Drupal’s would be better suited.
Alongside Jekyll, we used Hologram developed by Trulia for our style guide. It proved to be a great workflow for our designer, front-end developer and myself to interact efficiently and see updated results in the browser rapidly.
And today… Today we celebrate our independ… no - we celebrate our redesigned website launch and the Drupalcon Baltimore kickoff simultaneously! Coincidence? Of course not! However, I would like to give a shoutout to my entire team for making this happen on a tight schedule and an extra big-ups to Anne and Oksana who put in extra hours in the weeks leading up to make today possible. It was fun to be a part of the building process again; I found myself feverishly reloading the site every time new code was pushed up, which was often many, many times a day.
Related Blog Posts
Gender Inclusivity Is More Than an “Other” Option
Conversations around gender inclusivity often focus on gender fields in forms. The conversation is bigger than that, though. Is gender data even necessary? How does a user change their name? How does this all tie into user experience?