Kevin Hougasian

It’s been a few years, several great people, an awesome company, and a cool thing we made 😀 Once upon a time, we had a mixed bag of frameworks powering our web properties. Bootstrap, Semantic UI, ...

One of the perks being with Ritter, and on the dev team, is you can choose the hardware that makes you happy and productive! Team members have the option of Windows or Mac, with refreshes every 3-4...

This is an updated post of the original here. Whether you’re new to the frontend at RIMdev or looking for more about our Frontend team, here’s a quick overview of our team, tools, and culture! ...

If you’re not familiar with Platform UI, it’s a utility rich CSS framework we created. As we look to migrate all of our apps and static sites to Platform UI, we realized that one of the core CSS i...

For a long time, we were dependent on the CSS frameworks of others – and we were quite happy. 😀 As our needs grew, we needed a framework that suited all of them. So we created Platform UI, our cus...

URLs are the bridges that connect our little island of a website to the bigger continent known as the Internet. Preserving URL integrity is the utmost importance for providing an excellent experien...

We’ve moved around CSS frameworks in the past few years, Semantic UI for our application layer, and Bootstrap for our static sites. As our needs and applications continue to grow, we’re placing mor...

This post is getting old! See an updated version here New to the frontend at RIMdev, or looking for more about our Frontend team? Here’s a quick overview of our team, tools, and culture! As a...

We’ve accomplished so much this year thanks to @VueJS that we wanted to give back to the Vue community in some way. Ritter IM is sponsoring a happy hour in Tampa during VueConf 2019. Come join us ...

If you’re not familiar, or just haven’t used Sass maps, here’s your chance to dive in. Our latest static site was built on Jekyll using Bootstrap. Sass maps helped us extend Bootstrap to include b...

Setting up a local server comes in many flavours today. My goto was the Apache vhost.conf/hosts combo, now to load something quickly - Gulp. Setup We’re going to assume you have node and npm up a...

If you CSS, you’re familiar with the browser -prefix. Chrome and Safari have -webkit, -moz for Firefox/Mozilla, and -ms for Edge. As browsers iterate, prefixes drop off, so packages have stepped in...

We decided not to use Material Design (#reasons) while re-developing our core application suite, although i really miss MD’s micro-interactions that happen in forms. Semantic UI, while it’s feature...

One of my early challenges at RIMdev was to create a RIMdev logo. Something that worked with the existing RitterIM knight, but also let us stand out as the development department. Something that ou...

World Wide Web, that’s what the “www” stands for in www.rimdev.io - a show of hands for those who knew that? Why do we perpetuate a marker that has outstayed it’s welcome? It’s a relic from the d...

Our APIs expose data to Ritter’s quote engines based on product, marketplace, and url. As a leading FMO (Field Marketing Organization), our agents use these products and urls to service their clien...

Most of our web properties run on jekyll, ebrokersoftware.com, theagentsurvivalguide.com, and more slated for the coming year. The RIMdev blog lets up both document and play with what may, or may ...

So you may have noticed a new look for the RIMdev blog ;) Our blog will always be a work in progress and a chance to try new things. Version 2 showcases semantic-ui 2.2 while being powered by jekyl...

eBroker Software’s, Ritter’s Affordable Care Act (ACA) Marketplace Quote Engine, login portion was slated for a UI refresh. One of the challenges we faced was an agent that is legally blind. The ag...

So much work has gone into rimdev.io, and we like to keep content fresh, or at least let you know you may be reading an old or outdated article. Enter the freshness scale. Leading every article on...

Our initial blog had some nice features, but really didn’t do anything to place our content first. Was it really important that our logo be prominently placed? Not really, we’re developing products...

We wanted to create a tool that allowed non-GitHub user’s access to our GitHub releases with the hope that they would be more informed about the progress our team is making in squashing bugs, addin...