Hi there, thanks for tuning in! If you’re referring to the data-ops UI, then it’s an open source project that you can review, deploy, and host on your own. Check it out on GitHub: github.com/kontent-ai/data-ops Have further questions? Definitely feel free to contact our support team. Get in touch via chat at kontent.ai/.

Hello there

Great Explanation!

To me stills looks like an API

Yea I was trying hard to find out what was so "new" and special about this realising it's what we've been doing for the past many, many years already.

This sentence was a better explanation than the video

You saved 2 minutes of my life

it's just an API, we know that API only required BODY

Then it's not for you lol, nobody is forcing you.

One of snipcart's data-items on the button markup is adding options so the customer can pick (predefined) colors or sizes. It's easy.

@@notthisguy1711 What if I'm making a website that requires users to send pictures that I make into 3-D printed lithophanes? Is there a way to make a field where users upload pictures and integrate that with snipcart?

You can use the smart button payments checkout flow documented here (developer.paypal.com/docs/checkout/#) and see a demo of it here (kzbin.info/www/bejne/o2HcdYp6otmjgas)

Hi Raph, good point. I think if you generate the site, use "gatsby serve" and then kill the server before trying out the offline version it should work too. I have .NET background, so I think I'm just used to IIS more :)

Hi Abderrahmen, no, you need to use the Link component. That way the click is intercepted by Gatsby and the requested page is provided from the cache. If you use classic anchor tag, browsers will automatically attempt to get the page from the server.

@abderrahmen Hey did it work with AniLink ? @Ondrabus btw AniLink is nothing to do with anchor tags. Edit: for anyone wondering yes it works with AniLink same way it does Link

@@Genidii Oh I confused it with "any link" :-) Thank you for getting back and verifying it works!

He did though

@@joerivde did he?

@@joerivde clearly did a bad job at it.

Hi, check out our e-book which explains headless CMS into deep: kenticocloud.com/headless-cms-guide

Hi, I would highly recommend reading article kenticocloud.com/blog/what-is-headless-cms which describes the whole story behind headless CMS. Headless means that the architecture is decoupled-the presentation layer is separated from the back-end. Content is stored in the back-end as well and consumed through its application programming interface (API) and displayed on the presentation layer.