Industry Insight

About the Author

javascript hook
Rachael, a white woman with curly, shoulder-length hair, smiles at the camera. She wears a mauve top and a brick building is reflected in the window behind her.
Rachael Penfil

Rachael is UX Manager and co-leads the accessibility team. Rachael advocates for users while keeping client needs in the forefront of her mind.

javascript hook
Tom Jacobs

Tom, President, uses his keen strategic eye to help clients create groundbreaking creative campaigns. And he's been a thought leader appearing on Bloomberg, WGN, NBC, CMO.com, and Wall Street Journal.  

javascript hook
Devin Owsley-Aquilia: light-skinned non-binary person smiling, with dark blonde hair pulled back, wearing a black turtleneck against a grey wall
Devin Owsley-Aquilia

Devin is Scrum Master, Agile Master Certified, co-leads the accessibility team and leads complex, enterprise web development for a diverse set of higher ed, consumer, and B2B clients.

javascript hook
Anne Lentino
Anne Lentino

Anne, as a Product Owner, enjoys the opportunity to learn about her clients' diverse fields of expertise. She consistently advocates to make the best products to support each client's growing business, while keeping workflow efficiency and creativity top of mind.

javascript hook
Laura Chaparro
Laura Chaparro

As Sandstorm's Senior Account Director, Laura helps clients grow their businesses. She has worked at both big and small agencies, with small local and global brands garnering extensive experience in B2B, B2C, and retail marketing.

javascript hook
Amanda Heberg
Amanda Heberg

As the VP, Business Development, Amanda leads new business development, sales, partnerships and marketing strategy across Sandstorm. Amanda collaborates closely with new clients to build strong, long-lasting partnerships while aligning Sandstorm's capabilities to solve client business problems.

javascript hook
Eric Savage
Eric Savage

Eric Savage is a JavaScript Developer with expert knowledge and extensive experience in front-end development.

javascript hook
Jeff Umbricht
Jeff Umbricht

Jeff is an Illinois native with a passion for web development. Making code into great things drives him every day. He’s often busy building awesome experiences for Sandstorm clients, and there’s a high probability that he’s rocking out to metal while he codes.

javascript hook
Nick Meshes
Nick Meshes

Nick is Sandstorm’s Director of Technology & Analytics. He’s boosting our quantitative focus. He’s busy increasing our capabilities in web analytics, website optimization testing, SEO, SEM, display advertising, business intelligence, and personalization.

javascript hook
Emily Kodner
Emily Kodner

Emily is our Senior Director of Client Delivery. She consults with clients, leads projects and works alongside our team of creatives and developers to provide solutions to complex business challenges.

javascript hook
Nathan Haas
Nathan Haas

Nathan is a User Interface Art Director at Sandstorm. He is a proud alum of The University of Tennessee. His main focus was print design, but he soon realized the potential of pixels. This combination of print and interactive gives him a unique view of design possibilities.

javascript hook
Andy Cullen
Andy Cullen

Someday I'll need a real bio, but for now I'm busy creating awesomeness for our clients!

javascript hook
Janna Fiester
Janna Fiester

Sandstorm's VP of UX & Brand Innovation, Janna, is a design-thinker. Showcased in several design publications and exhibited at the Art Institute of Chicago, she is talented in taking nuggets of good ideas and nurturing them into solutions that are always strategic, engaging and visually delightful.

javascript hook
Alma Meshes
Alma Meshes

Alma likes to help get things done at Sandstorm. She's worn many hats in her many years here and knows a little bit about everything.

javascript hook
Sandy Marsico, Founder & CEO
Sandy Marsico

Sandy Marsico is the founder & CEO of Sandstorm®, a digital brand experience agency that turns consumer insights into engaging user experiences through our unique blend of data science, brand strategy, UX and enterprise-level technology.

Industry Insight

Consider your options when comparing Content Management Systems

[This is second post of a series on choosing a CMS. Check out Part 1, and learn about the importance of your goals and requirements in the process]

Now that you have a solid set of requirements for your content management system (CMS), you can start to explore some different options. To narrow the conversation, it's sometimes helpful to consider them as a balance between simplicity versus flexibility.

5 approaches from simple to flexible

1: No development needed

Starting on one side, you'll find the most simple subscription-based solutions that require no development and minimal setup. As an example, think of a blogging site for which you just need to create an account. The options are limited. It doesn't give you much more than a running list of posts that you can create and edit. Google Blogger and Tumblr are examples. While some border on being social media more than CMS, they are in fact services that allow you to manage your content.

2: Simple and customizable

Moving up from there, you have simple frameworks that provide a medium amount of customization. This can be anything from services like SquareSpace to platforms like Ghost and Wordpress. These are designed to get you up and running quickly, but also allow you to heavily customize your site.

At this level, you can sometimes add basic online stores. You can create a unique look and feel. With something like Wordpress, you can even add some custom functionality. Eventually when dealing with options in this category you'll find that you're trying to do things for which the framework just wasn't built, so you'll move closer to flexibility.

3: Scalable and flexible solutions

The next level up are the more scalable and flexible solutions. Options like Drupal, SiteCore or AdobeCQ are in this category. While they are very different frameworks, they all have some basic preconceived notions about how content should be managed and structured. These are solutions that get you quickly up and going, but they are also intended for heavy customization. Advanced custom functionality can be added on top of them. Some can even be extended to the point where they are more than just a website and terms like "web application" start to emerge.

They are meant to be fast to deploy because much of the structure of how to manage your content has already been determined. However, this ease of deployment and development can sometimes come with the penalty of rigidity. Once you start to stray outside of their assumptions about how content should be managed, things can start to get messy. It's like strapping a howitzer on a sports car. Sure, we can get it to mostly work, but it just wasn't designed to do that.

4: Frameworks for fully custom sites

At the far extreme you find frameworks for custom-built applications that allow for advanced integrations, workflows, relationships and functionality. These are true development frameworks that allow you to build your own CMS or web application. Laravel and Django are two examples that fit in this category. They make sense when basic management of content is a secondary requirement, trumped by custom functionality. Or perhaps the structure of the content is unique enough that trying to get it to fit into some of the options in the previous category would not be ideal.

The primary benefit is that your application is faster because it was built to do exactly what you want. The primary downside is that it may cost more to build because you have more custom code and less community-tested extensions that effortlessly drop into your new site.

5: From the ground up

Of course out at the furthest edge you'll find the "from the ground up" option. This would be to pick a language and build a completely custom solution, without taking advantage of any frameworks. There are reasons that you'd do this, but if you're looking for a CMS, you're probably better off considering one of the many frameworks that exist today.

Proprietary versus Open Source

One of the key decisions is to consider when choosing a CMS whether you want to go with one that is proprietary software versus one that is open-source.

Proprietary

Proprietary software brings licensing fees and/or ongoing hosting fees. These fees are often in addition to the work required to design, configure, customize and host your site. Solutions like SquareSpace, SiteCore, AdobeCQ and others are businesses that provide a service in order to make money.

For some of these, the costs can get quite high (the average AdobeCQ license can run into hundreds of thousands of dollars). This can be fine if the CMS fits your needs. After all, part of what you're theoretically purchasing is the peace-of mind that if something goes wrong, that vendor will be there to help.

Open Source

In contrast, open-source software is free to download and use. Solutions like Wordpress, Drupal, Django and Laravel are all built by a community of developers and released under open licenses. Generally you want to look for a knowledgeable partner who you feel confident can properly build your CMS solution using one of these frameworks.

Final considerations

Budget

A final step is to consider your budget. You can make strategic decisions to create a CMS-based site with a small budget or invest heavily in some items to ensure your site covers the full extent of your needs.

Maintaining your site after launch

A final cost consideration is ongoing maintenance and support. If you are considering a proprietary solution, be sure to budget for the ongoing licensing fees. You should also double check that these fees cover ongoing upgrades and security fixes.

If you are considering an open source solution, be sure to set aside some of your budget to have your developer perform security updates and proactive maintenance. In either case, consider also setting aside some budget for support requests – minor feature requests and other changes to how the site functions. Properly considering your ongoing maintenance and support costs will help you to finalize the amount you have to build your CMS.

Making your final CMS decision

With the term CMS covering such a wide range of digital platforms, it's no wonder that many feel overwhelmed when choosing one. Defining your goals and requirements can help you to navigate your options. We've found that walking through these steps is a great way to reduce apprehension, provide clarity and deliver a solid final product. We hope you find them useful also.

[If you enjoyed this post, read Part 1: Goals and Requirements]

This blog was posted by on July 30.
Sean Fuller

About the Author

Sean Fuller

As Technology Director, Sean is a hands-on developer and technical lead on projects. He works with design and strategist teams from kick off through launch to plan, design and execute technical solutions for client projects. 

How to Compare Content Management Systems - Goals and Requirements

Deciding which Content Management System (CMS) to use can be a daunting task. It can be difficult to sort through the plethora of irrelevant recommendations and confusing information to find the best solution. Many of our clients come to us with a rough sense of what they want, but need help making the final recommendation.

How to compare CMS?

Comparing Content Management Systems is challenging because it means different things to different people. The phrase has evolved to cover a range of web frameworks and applications. It is a broad term that covers any program which facilitates content creation and updates (usually on the web). On top of that, many popular CMS options are highly customizable – two sites built on the same framework can look very different. 

Going beyond the simple editing of an organization's "About Us" page, modern websites demand a great flexibility in how they handle content. They often need different types of content, each one requiring specific workflows or relationships aimed at solving various goals. For example, consider the differences between a blog post, an event listing, and a product detail page. Each one has unique data associated with it. Each one is organized in different ways. Being able to handle unique types of content while still providing a consistent interface is an important part of any CMS.

A CMS often has other advanced functionality. They pull content in from other systems. Some integrate with different authentication systems. Some have an online stores. Others allow a community of users to login and participate in some way. Still others might pull in raw data from one source to display it to users in a completely new way. These are all managing different kinds of content at some level. 

Create Goals

Not every site needs every possible option. So, what does it your site need? It's good to get back to your goals and requirements. Your website has needs that are just as unique as your organization. A needs-based assessment can help to focus your requirements and narrow down the search.

Start by defining your goals. Create a list of what you want to achieve with this new CMS. Starting with your goals will help to focus your efforts.

  • What problems are you looking to solve? 
  • Are you looking to increase your brand perception as part of this project? 
  • Is increased membership or sales a primary goal? 
  • If you have a current website, what is it not doing well? 
  • How will your CMS need to support your organization? 

Identify and prioritize your requirements

Once you have a good list, start writing a list of requirements. Some will just require a quick rephrase of a stated goal. Others will lead to a whole new list of items. For example, if your goal is to publish your events calendar online, but your events are currently managed in a different system, integration with that system is a potential requirement. 

Next start to prioritize these requirements. Rank your requirements from must-haves to nice-to-haves. This exercise helps you make the most informed decisions as you start to build your budget. Some items might need to come in a second phase after the first version of the site launches. 

Eliminate some options from the start

Understanding your organization's technical requirements can also help to eliminate some options. For example, if your IT infrastructure requires you to use .Net, then a Ruby, Python or PHP-based solution (like Drupal) may not be possible. More and more these restrictions are no longer a problem with modern hosting options, but it's one of the first questions to ask.

[Continue to Part 2: Consider Your Options]

This blog was posted by on July 24.
Sean Fuller

About the Author

Sean Fuller

As Technology Director, Sean is a hands-on developer and technical lead on projects. He works with design and strategist teams from kick off through launch to plan, design and execute technical solutions for client projects. 

Sandstorm develops a responsive website for Urban Innovations

Our relationship with Urban Innovations began way back in 2007 when we originally designed their website. So by the time 2015 rolled around, we were all in agreement that it was time to give the site a fresh, new look with a user experience design that would attract new tenants and investors alike.

In addition to the Drupal website development project, we took this opportunity to reflect upon the evolution of the Urban Innovations brand. We worked closely with Urban Innovations to develop their new brand positioning and value proposition to ensure that the web content clearly and directly communicates what visitors want and need to know, all while optimizing the content for search engines.

The end result: an easily updatable, responsive website that communicates the Urban Innovations difference. The tablet and mobile menus make the site easily accessible on any device, and the parallax on the homepage draws visitors into the experience. The commercial and affordable property sections allow Urban Innovations to show off their real estate portfolio while also providing users with pertinent information about amenities and neighborhood details.

Check out the new urbaninnovations.com, and you’ll see why we’re so excited about it!

This blog was posted by on April 22.
Amanda Tacker

About the Author

Amanda Tacker

Amanda is a Digital Strategist with several years of experience on both the agency and client sides, with both B2B and B2C clients.

Hamburgers Menus: A Matter of Taste (April Fools!)

[This is Sandstorm's 2015 April Fool's Day post. Enjoy!]

Anyone involved in mobile usability or mobile user interface design is familiar with the hamburger menu icon. 

But where did this icon come from? Why is it called a "hamburger"? Today we uncover it's interesting origins and how you can change how you use it on your sites to be more user friendly. 

Hamburgers and Navigation are Linked Historically

The connection between hamburgers and navigation has a long history. Hamburg the city from which the sandwich derives its name, was once known as one of the busiest port cities in all of Europe. Located on the Elbe, it has easy access to the North Sea and ultimately the Atlantic Ocean. As a hub for shipping commerce for centuries, Hamburg became well known for the production of accurate maps, compasses, and astrolabes.

Thus, the best way to get from one port to the next was, in effect, to use “Hamburger Navigation.” In fact, it is believed that the beloved sandwich came to the U.S. as the Hamburg steak served to passengers on the Hamburg-America Line steamships.

Its "Iconic" Origin

The history of the hamburger menu icon is quite unclear. While conducting our research, we encountered the earliest depiction of three parallel lines being clicked. Below you will be this example from Egyptian hieroglyphics. We are unsure whether actually touching these would have triggered a secret passage or simply were used as a guide for readers, i.e. “you are going in the right direction.”

At the time of hieroglyphics, hamburgers didn’t exist (nor did Hamburg the city). How did these Egyptian and German roots “stack up” to be the icon we know today?

One hypothesis is that while most Egyptian tombs were being excavated in the early 20th century, the popularity of the hamburger as a sandwich was rising. The more likely hypothesis is that that three horizontal parallel lines looks like a hamburger, albeit a minimalist one. (Taken literally, it looks much more like a grilled cheese or a filet-o-fish.) Or so we thought.

Finding the hamburger menu online

We did some Internet excavation of our own using the Wayback Machine. We reviewed a number of websites related to fast food burger joints. Here we encountered a revelation, the first McDonald’s website and what did we find? A hamburger menu.

While this icon directed users to the restaurant menu to order food, it’s clear that this is the first, and most literal use of this now beloved means of getting from page to page on a website. This visual cue being paired with with the historical aspect of “Hamburger Navigation,” is quite possibly the result of a happy accident.

Even today, Five Guys Burgers and Fries uses a hamburger icon for all iterations of their responsive websites.

How can we make these icons more appealing to users?

You may also be aware of some of the research related to the position of the hamburger menu and whether or not including a label with the word ‘menu’ above or below the icon increases users understanding of the icon (it does).

While we’ve adopted the practice of including labels with icons to improve user understanding and reduce the cognitive load, we’ve been experimenting with a variety of designs for the hamburger menu icon. In particular we wanted to answer the question, can a more realistic hamburger icon affect the site’s user experience? If so, what factors contribute to a better experience? Below are some of the icons we tested along with their results.


Hamburger

Result: Users experienced minimal usability issues but felt the overall site experience was missing something.
Recommendation: Consider toppings to improve visual appeal. Remember, users navigate with their eyes!

Cheeseburger

Result: Very few usability issues uncovered. 85% of users tested found this to be the most satisfying version.
Recommendation: Your go-to icon for most audiences. Consider adding a fried egg and bacon to enhance the experience.

Double Cheeseburger

Result: Users anticipated a longer menu due to the additional layers. Some users felt tired after navigating. 
Recommendation: A/B test to determine the appetite for site pages from your users.

Triple Cheeseburger

Result: Inconclusive, very few users were able to complete all tasks in the study. Caused confusion among international audiences.
Recommendation: Less is more. May be useful when you need to increase the size of your user base.

Hot Dog

Result: Tested well with children.
Recommendation: Avoid the use of ketchup.

Chicken Sandwich

Result: Great usability but the experience came across as dry.
Recommendation: Consider toast as possibility instead of a kaiser roll or spice it up with some hot sauce!

Veggie Burger

Result: No usability issues uncovered but users were generally dissatisfied with the experience.
Recommendation: Not suitable for the main menu. Save this for the side navigation on the desktop version.

Conclusion

The more delicious the user perceives the hamburger to be, the better the user experience. Get to know your users, preferences vary depending on the use case.


Sources:

Hieroglyphics - https://4815162342execute.wordpress.com/lost-themes/hieroglyphs/
Grilled Cheese: http://monosnap.com/file/omYgQ6PlveSIeEXUPezbKMEZdLc21e

If you haven’t realized yet, this post is a complete joke. Happy April Fool’s. Here’s the real history of the hamburger icon.

This blog was posted by on April 1.
Michael Hartman

About the Author

Michael Hartman

As Sandstorm's Technology and Usability Director, Michael leads our developers and usability researchers in creating web sites and applications—both desktop and mobile—that embody our favorite blend: intuitive user experience and dynamic Drupal development.

THIS FILE WAS POSTED UNDER: 
this file was posted under: 
Chicago Web Development Firm Attends Drupal MidCamp

Sandstorm is proud to once again be involved in Drupal MidCamp. MidCamp (also known as the Midwest Drupal Camp) is an annual event held in Chicago that brings together people who use, develop, design, and support Drupal. This year’s MidCamp will be March 19-22, 2015 at the UIC Student Center East.

Sandstorm is a bronze sponsor this year, and we’ve got web developers, strategists, and web designers attending. Last year, I had the pleasure of speaking about user research techniques, which was a blast. This year I'm looking forward to mingling with regional Drupal developers and attending sessions on Drupal 8, "headless" Drupal, and automated testing.We're also on the look out for another solid Front End Developer here at Sandstorm. If that's you, get in touch.

You don't have to be a developer to get something out of MidCamp. There are plenty of promising sessions for people new to Drupal and project managers working with the CMS. We hope to see you there, and have some fun!

This blog was posted by on March 13, 2015.
Michael Hartman

About the Author

Michael Hartman

As Sandstorm's Technology and Usability Director, Michael leads our developers and usability researchers in creating web sites and applications—both desktop and mobile—that embody our favorite blend: intuitive user experience and dynamic Drupal development.

Why do you need a website maintenance plan for your Drupal website?

Congratulations on launching your new Drupal website. You can now rest assured that you never have to think about it again. It will automatically generate revenue and keep itself running for decades to come. Pat yourself on the back and have a drink. Your website is complete.

Well... this might not be entirely true.

In reality your website is never really finished. Just like with a car or home, things degrade over time. Your website is no different and you need to have a website maintenance plan.

What is website maintenance?

It is the process of keeping your website up to date and running smoothly. It involves applying security patches, monitoring web server performance, and maintaining your code base. This is on top of maintaining your content, products and/or users. You gotta do that, too. Major reasons to have a maintenance plan include security, performance, backups, and other considerations.

Security

Hackers are always looking for ways to compromise websites through new techniques or insecure code. It’s critical your website remains as secure as possible. This often involves applying security patches or software upgrades both at the code and server levels. One advantage to open source software like Drupal, is the community of developers finding security holes and contributing patches.

This is also a double edged sword. Once hackers identify a security hole, they can exploit it by targeting unmaintained sites. You are running a huge risk if you’re running a Drupal site and not keeping up with Drupal core and module security upgrades.

Performance

Performance affects the amount of time it takes for your website to load for a user on their device. This includes time to complete transactions like adding a product to a cart or submitting a form. Good website performance is good usability. Users will abandon a poorly performing website never to return. It’s also good for search engine optimization (SEO).

We include performance testing and tweaking as part of the launch process. Yet, performance can degrade over time as code, content, or the server environment changes. Perhaps your site’s traffic has increased and now requires more resources to meet user needs. Wouldn’t that be great? It is great if you’re monitoring your traffic, server performance, and page load times so you can ramp up to meet the demand.

Backups

Another component of a good website maintenance strategy is a solid backup and restore plan. Most web hosts keep some level of back ups and will either restore your site as part of your hosting package or for a fee.

While this provides a safety net, they usually only keep a short window of backups. You may need to restore your site to an earlier point than your host has kept. Or you may need to restore to a point since your host’s last backup. A defined backup strategy allows you to quickly bring your site back online whatever the case may be.

Other considerations

Broken Links
Each website page links to internal pages and external websites. These links can change over time as content expires and changes or as sites get redesigned. Keeping an eye on broken links and updating or adding redirects when urls change should be part of your maintenance plan. Broken links are detrimental to your SEO.

Web forms
It’s a good practice to test and confirm that each of your web forms are working as expected, this may include contact us, event registration, and newsletter signup forms. Hopefully you’re seeing regular submissions, but it’s possible another update affected these forms. We like to confirm everything is still working after applying other updates to a site.

Development and staging environments
When implementing development updates, you should avoid deploying new code and patches to your live website. It’s important to have a separate deveopment environment for developing and testing new features and security updates. You use a staging environment to review and confirm these updates before releasing them on your live website.

The value of maintenance

The cost of website maintenance outweighs the cost of fixing problems caused by a lack of maintenance. A website maintenance plan is an added level of insurance against security and server-related issues that can cause grief and lost revenue. At the end of the day, a well-maintained site is another component of a great user experience.

Need help with Drupal website maintenance? Get in touch.

This blog was posted by on February 20.
Michael Hartman

About the Author

Michael Hartman

As Sandstorm's Technology and Usability Director, Michael leads our developers and usability researchers in creating web sites and applications—both desktop and mobile—that embody our favorite blend: intuitive user experience and dynamic Drupal development.

Sandstorm designed and developed a responsive website that helps child health

The American Academy of Pediatrics came to us with a great goal. They were planning a project in conjunction with the National Center for Medical Home Implementation (NCMHI). It would be a fun, educational microsite specifically built for the pediatrics community. Excited about the possibility of creating a healthcare microsite with a twist, we came on board.

The microsite’s mission is to educate users about a concept known as a “medical home.” The term refers not to a place, but to a system of proven best-practices for providing healthcare to kids. If we do our job well, the microsite will help clinics put these practices into action. The impact on children’s lives will be phenomenal.

Creating the site was a collaborative process. We worked closely with NCMHI to determine a user experience design that everyone from government policymakers to parents to pediatricians would find to be a useful, intuitive tool. We were able to give it a look that’s playful while still giving context to the information the site delivers. From there, we built the site using responsive web development so it would function smoothly for users on any device.

The microsite recently launched and we couldn’t be happier with the results. If you’re interested in seeing the final product, check out NCMHI's responsive website

This blog was posted by on January 30.
Kellye Blosser

About the Author

Kellye Blosser

Kellye’s unique approach involves a delicate balance of left and right-brained thinking. She most recently hailed from the corporate video world. Here at Sandstorm, she’s excited to bring strategic, innovative thinking to every project.

Cache clearing menu

At Sandstorm, we do a lot of website maintenance. That can mean many different types of things like development of new site components, updating old content or creating new content. With each of these different types of work there is a popular issue that can cause panic: he or she forgets to clear his or her caches after making the updates.

Nothing changed. Is the site broken?

If you’ve ever maintained a website, or maybe just updated content on one, you may have come across a situation where it looks as though your edits didn’t save. This ultimately leads into what seems like a broken website, but turns out (after consulting a developer) that you just need to “clear your cache”.

What is “cache”?

Like most people, myself included, when this first happens you are probably wondering what in the world is a “cache”. Google will tell you that it is “a collection of items of the same type stored in a hidden or inaccessible place,” but that makes me even more confused. In layman’s terms, cache is a save file that allows web pages to load faster.  

When you arrive at a website, your browser takes elements of that page and saves them locally into “cache”. This way, the next time you decide to visit that specific page, your browser is going to remember how it looked the last time and, instead of downloading those pieces again, it will use what is stored in the cache to build the page. This results in a great performance boost. Unfortunately, it can, at least appear to, be a nightmare for content editors who don’t understand why their changes are not showing up on the live site.

It’s an easy issue to address

Even with this knowledge, I still come by this simple issue every so often (so don’t feel bad if you do, too). What you should remember is to clear your browser’s cache, refresh the page and see if your edits are now in place (this is particularly easy on a Drupal site). If your changes are not there after that, then you can run frantically to your local developer or IT department. Assure them that you did clear your cache, and this may actually be a real bug.

This blog was posted by on December 31.
Kyle Lamble

About the Author

Kyle Lamble

Kyle is your stereotypical bluehat hacker, by day, who wants you to upgrade your browser to support his love for cutting edge web development techniques. By night, he is a curator and publisher of art. Co-founder of Loosey Goosey Art, Kyle spends much of his off time helping artists find their inner potential.

Web Developer Ventures to DrupalCon 2014

Each year we pick two team members (either ux designers or Drupal web developers), who haven’t had the chance to go to DrupalCon, and send them off to soak up the latest trends and developments within the community. This year I was lucky enough to be sent off to Austin, TX for DrupalCon 2014. Besides the wonderful food and the nice break from a cold Chicago, we were able to bring home enough valuable knowledge to influence Sandstorm’s development practices quite a bit.

One of the biggest lessons we were able to pick up was the importance of automation in web development. We have since begun implementing powerful tools such as Git, Grunt, and Bower to continuously integrate updates to the websites we have worked on. Coincidentally, these tools are essential when working with multiple developers on a single project, and this year we have expanded our development team by quite a bit.

Overall, DrupalCon has always been a great influence on the company as a whole. Not just for development, but as well with design and content strategy. The Drupal community is a very welcoming environment, as you would expect from an open source platform, which reflects our core values “learning and sharing” and is why we continue to go year after year.

This blog was posted by on December 23.
Kyle Lamble

About the Author

Kyle Lamble

Kyle is your stereotypical bluehat hacker, by day, who wants you to upgrade your browser to support his love for cutting edge web development techniques. By night, he is a curator and publisher of art. Co-founder of Loosey Goosey Art, Kyle spends much of his off time helping artists find their inner potential.

THIS FILE WAS POSTED UNDER: 
this file was posted under: 
Learning and Sharing Drupal

I am quite proud (and excited) about our constant opportunities for employee learning and sharing here at Sandstorm. It’s even one of our core values. Having worked at other companies, learning and sharing are things that are in the “whenever we have time” category, which often translates into, well, NEVER.

In the past year, my Drupal expertise has grown exponentially thanks to AndyAndrew, and Will. I already considered myself Drupal-savvy, but I was introduced to new ways to author complex code when the editor “fixes” things that aren’t broken. Drew recently introduced me to posting a new and different kind of content, Events, and how it’s subtly different from other kinds of content that I’ve worked on before.

In addition to Drupal web development and administrative skills, we regularly have meetings where Sandy herself shares with us company overview information, such as how we’re doing year over year (spoiler, we’re doing awesome!) as well as new business or new client wins. For other companies this sort of information would be considered “unnecessary” for everyone outside the C-suite, but at Sandstorm there is a sense of trust, openness, and responsibility. It’s helpful and instructive to know where the ship is headed, not just that I’ve been rowing as fast as a I can. Understanding the work that’s happening outside of my tasks may not be directly applicable to my day to day, but it often makes things clearer and easier to understand, especially when things change.

This blog was posted by on December 22, 2014.
Jason Dabrowski

About the Author

Jason Dabrowski

Jason is one of Sandstorm’s designers and also helps keep the office running smoothly. As a veteran of the theatre—from acting to directing, lighting to set design—he knows the value of hard work and a positive attitude. Look for his unique voice on the blog.

THIS FILE WAS POSTED UNDER: 
this file was posted under: 

Pages