@igloo_si @Netlify Ha ha. That will teach me to get cocky!
In fairness the admin UI is not optimised to be used on mobile. Although it works, it's not where we expect most are configuration to take place.
@skippednote @SaraSoueidan @Netlify BOOM!
The ability to do devops from a bus seat is rather gratifying!
The ability to do devops from a bus seat is rather gratifying!
@SaraSoueidan @Netlify There is no built-in form validation, but you can add your own client-side validations and submit via javascript if you like. You can also make use of an automated honeypot to cut down on spammers.
https://www.netlify.com/docs/form-handling/#spam-filtering
https://www.netlify.com/docs/form-handling/#spam-filtering
@SaraSoueidan @Netlify Delighted to hear this!
@sallylait @SaraSoueidan @Netlify It's simple yet surprisingly powerful. (I suppose that's what happens when you also add API access to features)
Happy to answer any questions if you run into limitations for your use case. but I suspect you'll be off and running in no time. It's alarmingly quick to set up!
Happy to answer any questions if you run into limitations for your use case. but I suspect you'll be off and running in no time. It's alarmingly quick to set up!
@Paul_Kinlan @grigs @owencm @slightlylate For reasons other than those you hoped, this is my favourite tweet of all time.
@SaraSoueidan @Wufoo @Netlify Yep. You can set the submission notification to be an email, so you'll get an email summary of each one.
@Scott_Helme @AppSecCali @estark37 @manicode @HttpSecHeaders @JillianTessa @bcrypt @frgx @owaspgbg @TeliaSverige @BizzGrid @IrisClasson @nomxprotocol @BBCClick @ProfWoodward @PwnieAwards @dannsimmons @UKFast @gcluley @LloydsBankBiz @Secarma @ivanristic @thorsheim @feistyduck @spenley @EuropeanCentral @Infosecurity @drjessicabarker @TheKenMunroShow @BSidesLondon @info_dox @J4vv4D @Phantasialand @typo3 @owasp @troyhunt @fuzzerman @NDC_Conferences @dylanbeattie @PubConf @toddhgardner @KylieMHunt @SURFnet @joostd @elsje73 @BSidesLV @jessysaurusrex @Snubs @hak5darren @smashingconf *beaming* with pride at that photo.
Bristling at your judicious use of the word "and".
Bristling at your judicious use of the word "and".
@SaraSoueidan @Wufoo To can get @Netlify to provide a back end for all of your forms. All posts to the forms can trigger notifications, are accessible via an API and can also trigger builds etc.
Shout if you need any help but the docs are pretty good.
https://www.netlify.com/docs/form-handling/
Shout if you need any help but the docs are pretty good.
https://www.netlify.com/docs/form-handling/
Phil Hawksworth
@philhawksworth •
Wow. #BlackMirror4. USS Callister. Wow.
Just... Wow.
Here endeth the review.
Just... Wow.
Here endeth the review.
@reszahid @gatsbyjs Nice thing about a #JAMstack build... if you find that @gatsbyjs works well for you, you won't need to be tied to any one hosting provider. You should be able to move it to whichever one you find suits your workflow and requirements best.
@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.
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.
Phil Hawksworth
@philhawksworth •
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?
@jllord Somehow I missed this, but I found it in the end. Thank you for sharing this painful story. Bravery, determination and openness like yours is inspiring.
♥️
♥️
Phil Hawksworth
@philhawksworth •
So much to enjoy in this: https://twitter.com/joshbloch/status/946495641978417152