@Jack_Franklin @Netlify Correct. There is a soft limit in the terms of services... but it is massive. 100GB network bandwidth per month on free plans.
https://www.netlify.com/tos/
@livmadsen @Netlify Happy to hear it was useful, Liv. Thanks!
Yeah, the form handling and was the first things to make me realise that Netlify was not just a static web host. And that feature combined with notifications and triggers opens the doors to using it for so many things (for me, at least).
Yeah, the form handling and was the first things to make me realise that Netlify was not just a static web host. And that feature combined with notifications and triggers opens the doors to using it for so many things (for me, at least).
@m5 @brianleroux Some more "application-y" sites lend themselves better to client-side rendering driven by user actions etc as you mention. But the more you can deliver "ready to render" html down the wire, the better the perf and the fewer points of failure to worry about.
@brianleroux By the by, if someone was to write an article on how @smashingmag migrated to a #jamstack architecture and used things like https://github.com/netlify/gotrue to power authentication and user sessions...
...would it pique your interest enough to put it in your eyes?!
...would it pique your interest enough to put it in your eyes?!
@brianleroux Yes. That's where a term like #jamstack can be useful. As the ecosystem of static hosting, automation & microservices gets richer, we can go beyond what we thought of as the limits of static sites.
@smashingmag's move from lots of stacks to jamstack on @netlify is a good example
@smashingmag's move from lots of stacks to jamstack on @netlify is a good example
@m5 @brianleroux Heh. Not so much "naming a foundation", as trying to find a convenient term to refer to "static hosting with automated build and deployment infrastructure" – Which is a bit cumbersome to refer to.
Like how "LAMP stack" became a handy way to refer to quite a few moving parts.
Like how "LAMP stack" became a handy way to refer to quite a few moving parts.
@brianleroux I like to think of putting as much distance as practically possible between the user and the complexity. If the f/e can just request static assets which were baked earlier, there are fewer things to break or be attacked.
As Aaron Swartz said in 2002(!) — "Bake, don't fry"
As Aaron Swartz said in 2002(!) — "Bake, don't fry"
@brianleroux No problem. Except often we render on the b/e (or "generate HTML") in response to a request, when we could have done that at build time & de-risked all of our hosting infrastructure.
Not all cases of course, but do blogs really need a DB to reply to get requests? (For example)
Not all cases of course, but do blogs really need a DB to reply to get requests? (For example)
@lucianadrian Although I'm not the product manager.
*Puts hands in pockets and glances over at @phae as she unpacks her belongings onto her desk*
*Puts hands in pockets and glances over at @phae as she unpacks her belongings onto her desk*
@unicodeveloper @Netlify Nope. But it's nice to know that there are more and more of us. We should get jackets made!
https://medium.com/@philhawksworth/10-netlify-features-to-surprise-and-delight-225e846b7b21
https://medium.com/@philhawksworth/10-netlify-features-to-surprise-and-delight-225e846b7b21
A @netlify feature shaped brain burp:
https://medium.com/@philhawksworth/10-netlify-features-to-surprise-and-delight-225e846b7b21
https://medium.com/@philhawksworth/10-netlify-features-to-surprise-and-delight-225e846b7b21
@derekkinsman @sandertijink If you pull the content into your site at build time via the Contentful API, you'll probably not need to leave their free tier.
Or perhaps look at @NetlifyCMS which is shaping up nicely.
Either route assumes you have a static site generator building your site automatically.
Or perhaps look at @NetlifyCMS which is shaping up nicely.
Either route assumes you have a static site generator building your site automatically.
My excitement for @smashingconf London in February is only surpassed by my excitement in seeing my own name on the same list as these outrageously good speakers.
http://smashingconf.com/london-2018/speakers
Not. Intimidating. At. All.
http://smashingconf.com/london-2018/speakers
Not. Intimidating. At. All.
@xdesro @Netlify @thejohnstew We feel that this was a fair value exchange.
(and don't think we've forgotten about little Netfelix if you wanted to keep your 24/7 support line, dedicated CDN and performance SLA)
(and don't think we've forgotten about little Netfelix if you wanted to keep your 24/7 support line, dedicated CDN and performance SLA)