Launched an early landing page for JAM CI
https://jamci.co/
Hi there folks,
I just launched an early landing page for JAM CI to collect emails from people interested on it and help validate the idea: https://jamci.co/
I know it's very rough, but the idea is just to check how much interest will it get. With that in mind, I'd love to hear some feedback on the content.
Do you understand what it's about? Did it interest you in any way? Why?
Thanks in advance :D
Sounds pretty cool, and I could see myself using it. What sort of price point would it be to use the service?
Hey @soluxos, great to hear you might be interested. But tbh, I haven't thought much about that yet.
A very high level guess is that it'd start on the $50/month for some sites and would scale up with how many sites and parallel builds you need.
How many sites do you manage?
Do you think that's a reasonable price?
For me personally $50 would be out of my price range, but I have literally just one small website, with new posts 2x a week. But it probably means I'm just not your target audience.
I guess I would have very low usage (again 2 times a week) so I'd expect $5-10 per month. But again, I haven't a clue the costs behind the scene.
It's a total valid use case, though. Don't exclude yourself out of the target audience yet, since even I don't know who is that yet hahaha
I'm still on the validation process and everything might change :)
Most of the client sites I do now are static sites and require builds when content changes. What makes this platform different than Netlify or Now?
I think I'd need to learn more in your landing page before I'd give you my email.
JAM stack all the way and good luck with it!
It's so good to hear this. Thank you so much for the feedback!
I'll explain it to you here, but will definitely update the site soon.
If your content comes from a CMS, there are three things we intend to do:
Give you a library/plugin that you can use to fetch your CMS data. For example: on Gatsby it would replace the "graphql" tag you use on templates or "useStaticQuery", depending on what you use. On Next.js, it would replace anything you use to make REST or GraphQL calls. Ideally, you would just replace the library and not change how you use it. That allow us to cache the data on the first build.
Give you a plugin or connect directly to your CMS, so we can receive updates when your content changes. That allows us to know exactly what changed, so we can trigger a rebuild for only those things that have changed and not for the rest of your content, enabling really fast builds and site updates.
We don't plan to also be a host. So we can then deploy to your host of choice, be it Netlify, Now, Surge...
What do you think of the experience? Would you use something like that?
Do your sites use CMS for content or other form of data?