@reszahid There are similarities and overlaps for each. Like Netlify, Surge hosts static assets, where as Now can also run your Node back end or similar.
I'm excited by Netlify's CI build pipeline, branch deploys, other useful fetures.
We're big @gatsbyjs fans and it's a great fit.
On the back of this dangerously reckless (and feckless) tweet, I'm seeing his supporters trying to push the phrase "fake science".
I'm lost for words. https://twitter.com/realDonaldTrump/status/946531657229701120
I'm lost for words. https://twitter.com/realDonaldTrump/status/946531657229701120
@duckinator @Netlify @O2 Aha. Jolly good. Fingers crossed they resolve that quickly for you.
boop.ws looks handy!
boop.ws looks handy!
@duckinator @Netlify @O2 Although those instructions seem focussed on o2 customers. If you are not on o2 yourself, it looks like their online safety helpline might be the place to flag this: +44 808 8005002
@duckinator @Netlify I'd not expect this to be caused by @o2 classifying sites served from a given hosting provider as mature content, but some other frustrating misclassification of your site.
I see that you can report misclassifications to o2 directly via: https://www.o2.co.uk/help/safety-and-security/age-restricted-content-and-age-verification
I see that you can report misclassifications to o2 directly via: https://www.o2.co.uk/help/safety-and-security/age-restricted-content-and-age-verification
@reszahid @abeisgreat Ha! That's fair. Certainly strengths to each depending on your needs.
Personally I'm a big fan of a #jamstack approach, and in baking a static site at build time, then serving it from a good CDN. Esp for portfolio site. But you may have more exotic reqs.
Any preferred tools?
Personally I'm a big fan of a #jamstack approach, and in baking a static site at build time, then serving it from a good CDN. Esp for portfolio site. But you may have more exotic reqs.
Any preferred tools?
So much to enjoy in this: https://twitter.com/joshbloch/status/946495641978417152
@beep @MinaMarkham Seeing lots of suggestions for @GoHugoIO, @jekyllrb or other SSGs in this ample stream of replies... I'd offer that you can add a customisable CMS to any static site generator with @NetlifyCMS (which wrangles the content in your git repo)
After years of decrying CMSs, I'm a fan
After years of decrying CMSs, I'm a fan
@sonniesedge @jensimmons @pixelpaperyarn @MinaMarkham Agreed! Take a peep at @NetlifyCMS which is pretty much that... except it quietly manages your content in your git repo via a non-techie content admin.
@deathmtn @richlitt The free tier should allow you to do everything you can do on gh-pages and quite a bit more. Certainly would cover your custom domain, https and build automation needs.
More advanced features like form handling and split testing are also free with a nice high ceiling.
More advanced features like form handling and split testing are also free with a nice high ceiling.
@Jack_Franklin Yeah the ceiling is pretty high. If you fancy it, I could get you access to a beta of what I think is a really very interesting new feature. Just let me know.
@Jack_Franklin Right!?
Pleased to hear that it worked out well for you. There's quite a bit to explore once you start dabbling.
Pleased to hear that it worked out well for you. There's quite a bit to explore once you start dabbling.