traviskaufman

Hey all,

I built this because I missed the address shortcut tools you get at the big tech cos. I also wanted an excuse for a Rust project.

FAQ:

> Doesn't chrome already have this capability?

Chrome has a feature where you can configure custom search sites, but that implies that there's a query. Often, I just want to be able to type `m` and go to GMail, `c` and go to calendar, etc. Using Chromes functionality to do that feels clunky.

> Why not use JSON/YAML for the rules file?

I honestly just wanted something super simple, and I felt like using a txt file would limit my ability. Obviously I'm regretting this now because I want to do things like add "scripting" support where you could e.g. embed Dino and use that to execute JS that would run when you hit the shortcut, etc. etc.

That feedback paints a really clear picture in my head as to how you see us falling into the larger ecosystem; thank you!

I'd love to get more clarity into the "advantages" of each type of solution you mentioned above. When would you use a headless CMS vs. a static site generator with a custom template?

Great feedback regarding extensibility. I'm curious what caused you to build a bunch of validation sites like this? Similar scenario to us maybe?

Background: my co-founder and I built splashgen because we were building many simple landing pages to validate ideas quickly. We're both developers, and didn't want to use (or pay for) Unbounce or Carrd. We also didn't want to copy/paste HTML templates around; that felt too cumbersome. What we did want was to be able to programmatically describe a landing page and have it be generated for us. Hence splashgen.

Ask: *if you're a developer that needs to spin up a site to validate an idea quickly, why would/wouldn't you use this?* Your feedback will help us improve the product and decide if it's something we want to expand upon. Thanks!