Hi BetaPage, My name is Adam, and I'm a software engineer in the Indianapolis, IN (USA) area. I just quit my corporate day job two weeks ago to go all-in on my new startup, Dropkiq (https://www.dropkiq.com/). What I've learned the past couple of years working on an enterprise Ruby on Rails application is that people struggle to understand and use Liquid, which is a crucial component to inserting dynamic data into templates, emails, etc for many Ruby on Rails applications (including Shopify who built Liquid originally). Currently, it is a TON of guesswork that results in hours of trial and error and frustration. Dropkiq's mission is to solve this problem by making it easier for Liquid designers to understand what data they have available for them to use while they're writing liquid. Additionally, we verify that the liquid writer doesn't make any typos or mistakes (everyone is human after all), and we render the liquid immediately to show you exactly how it will appear to endusers. I would love to hear any feedback, ideas, etc. Thanks so much for taking the time to read!