@ScottDevTweets @Netlify @graphcms This might be more of a CMS than Netlify question (depending on what CMS you are using). Many headless CMS have different APIs for prod/staging (@contentful for sure). Netlify can consume different APIs in your builds thanks to deploy contexts.
https://www.netlify.com/docs/continuous-deployment/#deploy-contexts
https://www.netlify.com/docs/continuous-deployment/#deploy-contexts
@kilianvalkhof I would never make a cookie consent notification a "wall" or barrier to entry. And implementing one of these is no different on a Netlify site as anywhere else, you can do it however you like.
There are lots of references to make it easier, like this:
https://cookieconsent.insites.com/
There are lots of references to make it easier, like this:
https://cookieconsent.insites.com/
@getcompositor Oops... you have a 404 on your ISO home page. https://compositor.io/iso/
(the link to docs in your header)
(the link to docs in your header)
@AndyDavies @patrickhamann @rachelnabors @perrydyball The joke was staring me in the face. I couldn't help it.
@AndyDavies @patrickhamann @rachelnabors @perrydyball I might have been seeking a shopping recommendation.
@rachelnabors @patrickhamann @patrickhamann At some point, can we please have a conversation about the shirt?
x
x
A million times, this. https://twitter.com/rachelnabors/status/1003251212769210368
@johnallsopp We have a strict no returns policy.
So if you don't want to keep him, just put him in the sea.
So if you don't want to keep him, just put him in the sea.
@kadamwhite @_munter_ I find that hard too.
I can listen or I can read. I struggle to do both at the same time if the words are much different.
I can listen or I can read. I struggle to do both at the same time if the words are much different.