| Hi HN! I'm Adam and I'm on a mission is to simplify Shopify's Liquid markup language. My new product is called Dropkiq and you can find it at https://www.dropkiq.com/. I'm so excited to be here right now! Two weeks ago, I had an amazing job (making lots of ) at a corporate job, and I just left to do a solo venture after about 10 months of going back and fourth if this was the right thing to do or not.. I won't lie, it's scary! I have some savings and I've done a lot of side projects the last 10 years, but this is the first one that I'm going all-in on! At my corporate day job, I spent the last two years building a no-code Workflow tool where users could design logic flows and user interfaces all through the UI. We used Liquid, which is an open source library built by Shopify (https://bit.ly/2qrs6ve), to expose dynamic data so that users can choose what and how to display data. Much of my time was spent trying to teach users how to use the software that we created, and what I learned was that Liquid was the toughest part of teaching people. Even for people who we considered experts (that had used Liquid for years), there was a TON of guesswork and trial and error to arrive at a working solution... There had to be a better way... The last two weeks, we created an MVP web application. This application was designed for Shopify designers and RoR applications who use the Liquid gem as a way to improve their process as they write Liquid. Dropkiq uses test data to give you instant feedback as you write Liquid, so that you know right away what data is going to be displayed to your users. No more guesswork or long iteration cycles to test what you've written! Additionally, we show you what data you have available to you so you can choose the data you need from a menu, rather than needing to rely on your memory (which is typical in my experience for quick-moving enterprise Ruby on Rails applications). I would love your thoughts, feedback, ideas, etc.. Thanks! |