Go team Web!
The community at work, and a great response from the folks at @Wikimedia https://twitter.com/marcysutton/status/986705731394027520
@marcysutton Good question. Do you have recommendations of the ideal behaviour there? I bet @jdlrobson would be curious.
@iamsmarts @Netlify @SlackHQ Yeah, that a potent combo. I made a comments moderation tool with those.
https://youtu.be/-5z74ORssHE
https://youtu.be/-5z74ORssHE
This is fascinating. Congratulations to the team who delivered this. Making such changes when the content comes from such a large and varied community must be very tricky. https://twitter.com/jdlrobson/status/986664683741392896
@smashingconf I loved presenting an intro to @Netlify yesterday over lunch. Thanks for all the great questions. Some asked for slides. Behold! Here they are with a few of the examples. #smashingconf
💻 https://jamstack-comments.netlify.com
💻 https://twavatar.netlify.com
👀 https://hawksworx.com/talks/netlify-intro
💻 https://jamstack-comments.netlify.com
💻 https://twavatar.netlify.com
👀 https://hawksworx.com/talks/netlify-intro
@BenjaminEHowe @Netlify That's possible. Since the _headers file (it's just a file) can specify your CSP, you could produce it as an output of your build and the Netlify CDN would pick up that config for you. You could make your build process define those rules programmatically.
"Be ridiculously generous. And generosity goes beyond swag. Share insights and experience. Repsond to people."
— @yourfrienderin on engaging and growing a community. #heavybit
— @yourfrienderin on engaging and growing a community. #heavybit
"Avoid the shoulds.
- You probably don't need to go to SXSW.
- You don't need an April Fools joke campaign."
— @yourfrienderin of @Netlify
So much good stuff in this talk at @heavybit. Trying to resist urge to rush the stage and dispatch high fives.
- You probably don't need to go to SXSW.
- You don't need an April Fools joke campaign."
— @yourfrienderin of @Netlify
So much good stuff in this talk at @heavybit. Trying to resist urge to rush the stage and dispatch high fives.
Everyone, you can stop making things for the web now. The final piece of the puzzle has been put in place. Thanks for all your efforts, but the internet is now complete. https://twitter.com/Netlify/status/986296481031344130
@ChrisFerdinandi @saltcod That's generous. Happy to see a growing wealth of writings and resources on the subject. Exciting times ahead!
@ChrisFerdinandi @addyosmani Ha ha.
NOT trying to add another buzzword. It just encapsulated some thoughts as a result of a discussion.
NOT trying to add another buzzword. It just encapsulated some thoughts as a result of a discussion.
Says @addyosmani at #smashingconf - "Improve your database performance to improve server response times and page performance."
Agreed. Wherever possible, I like to optimise the database completely out of my stack.
#JAMStack
https://www.hawksworx.com/blog/webserverless/
Agreed. Wherever possible, I like to optimise the database completely out of my stack.
#JAMStack
https://www.hawksworx.com/blog/webserverless/
@smashingconf For those lovely people who joined me to look at @Netlify over lunch, the message in @TrentWalton's talk about 3rd party scripts would have been a *slam dunk* to include in our section about A/B testing. (Had we spent more than 3 mins introducing and deploying that)
Hoping my neck is strong enough to cope with the aggressive nodding in agreement which @TrentWalton's #smashingconf talk is triggering in me.
@smashingconf Coffee is happening, breakfast is happening, talks will be happening, and over lunch today, this is happening:
From zero to a deployed site using lots of Netlify's snazzy features.
Spaces limited, so grab a free ticket. #smashingconf https://twitter.com/Netlify/status/985947801472217088
From zero to a deployed site using lots of Netlify's snazzy features.
Spaces limited, so grab a free ticket. #smashingconf https://twitter.com/Netlify/status/985947801472217088
@mikemak_es @benschwarz @contentful @prismicio @Netlify @awscloud FWIW, If you use a static site generator, Contentful needn't be pricey since you'd be consuming its content only for builds, and not serving the world via its API.
And you can get to AWS Lambda directly via Netlify Functions these days.
But yeah. What you said.
:)
And you can get to AWS Lambda directly via Netlify Functions these days.
But yeah. What you said.
:)
@notwaldorf @charis @MikeRiethmuller @Netlify Whichever it is... these are unisex American Apparel, so I'm using my initiative and giving an option of small or medium.
Also, I am slowly transitioning into a (terrible) tailor.
Also, I am slowly transitioning into a (terrible) tailor.
@AndyDavies @benschwarz @NetlifyCMS @contentful Either way, an SSG (whichever) can let you retain good control over development, while a decoupled or headless CMS can provide a focussed and empowering authoring experience without the noise of a CMS which lets authors tinker with layout.
Build automation glues it all together
Build automation glues it all together
@AndyDavies @benschwarz You rang?!
I strongly favor using a static site generator to give good control over f/e perf and give solid workflows and deployment options. For authors, git is a no go, but you can use it invisibly behind the scenes with @NetlifyCMS or use a #headless option like @contentful
I strongly favor using a static site generator to give good control over f/e perf and give solid workflows and deployment options. For authors, git is a no go, but you can use it invisibly behind the scenes with @NetlifyCMS or use a #headless option like @contentful