@marcomwright @julesforrest @womenwhodesign @IFTTT @Netlify Very cool.
I do something similar where tweeting triggers a build which also pulls in recent tweets to my site.
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
If you need me, I'll be over here watching this by @SebLester over and over and over and over and over and over...
😍✒️❇️
https://www.instagram.com/p/BlBR6XCl4QG
😍✒️❇️
https://www.instagram.com/p/BlBR6XCl4QG
@dawgawel @GoHugoIO @Netlify psssst: That is possible on @Netlify, if you are crafty:
https://github.com/philhawksworth/content-shards/blob/master/gulpfile.js
https://github.com/philhawksworth/content-shards/blob/master/gulpfile.js
@growdigital @Netlify @GoHugoIO Great! I recommend looking at what exists for @GoHugoIO already and try to consider how your template might be different. Templates which do one thing really well, introduce concepts or features, or are visually different and impactful are all desirable!
http://templates.netlify.com/tags/hugo
http://templates.netlify.com/tags/hugo
@growdigital @Netlify @GoHugoIO Ha! In fact, the PR I see is from another Jake! Coincidence!
Checkout the guidance on contributing a template here:
http://templates.netlify.com/contribute
Checkout the guidance on contributing a template here:
http://templates.netlify.com/contribute
@growdigital @Netlify @GoHugoIO Oh, I missed that PR, @growdigital!
It looks great! We'll give it a good looking over later today, and then either feedback if there are any issues or accept the PR.
Thanks fo the contribution!
It looks great! We'll give it a good looking over later today, and then either feedback if there are any issues or accept the PR.
Thanks fo the contribution!
@haubertdashery @nejsconf @Netlify Beyond gutted that:
a. I won't be at @nejsconf at all!
b. I'll miss *this* talk!
🤩😭🤩😭🤩
a. I won't be at @nejsconf at all!
b. I'll miss *this* talk!
🤩😭🤩😭🤩
@bph @treb0r @paulmartin42 @WordPress @Netlify @NetlifyCMS @syntaxfm @webos @stolinski Yeah, those guys and that show are great!
I'd be very interested to hear how you get on if you do start experimenting. Especially if you are bridging between WP and #JAMstack like in this experiment: https://github.com/justinwhall/gatsby-wordpress-netlifly-starter
Or whatever you make! :)
I'd be very interested to hear how you get on if you do start experimenting. Especially if you are bridging between WP and #JAMstack like in this experiment: https://github.com/justinwhall/gatsby-wordpress-netlifly-starter
Or whatever you make! :)
@bph @treb0r @paulmartin42 @WordPress @Netlify That's fair. But also consider that this project included 4 different platforms with different functionalities all being combined into one, and that @NetlifyCMS and the open source glue layers which enable e-commerce and identity were created during the project. They exist now.
@nilsmielke @GoHugoIO Not specifically in depth, but asset pipelines will get some attention. I'm not going into very specific detail about any one SSG in particular, but will describe some of the different options and models.
Perhaps a follow up sessions will go deeper into individual SSGs.
Perhaps a follow up sessions will go deeper into individual SSGs.
@anthonybronkema @jgarber @jekyllrb We should add a Jekyll example to this set of quick start projects too, but if you are happy to just write md files, push them to git and have them automagically deploy, then there are some good starting points here. @eleven_ty feels simplest to me.
http://templates.netlify.com/
http://templates.netlify.com/
If you're interested in Static Site Generators and ways to get started with building on the #JAMstack, don't forget that on Tuesday 10th, I'll be giving this @smashingmag TV webinar. (And like other webinars, it's free if you are a Smashing Member)
https://www.smashingmagazine.com/smashing-tv/static-site-generators/
https://www.smashingmagazine.com/smashing-tv/static-site-generators/
@dstaley @Netlify Branch deploys are what you want.
https://www.netlify.com/docs/continuous-deployment/#branches-deploys
https://www.netlify.com/docs/continuous-deployment/#branches-deploys
@_munter_ @rohan10 @Netlify Netlify uses cloudfront for some of the optimised resources if you turn on the post-processing feature to automatically do some asset squeezing.
If your site is a @gatsbyjs build, you get various magical optimisation already, so you'll need to not enable that post-processing.
If your site is a @gatsbyjs build, you get various magical optimisation already, so you'll need to not enable that post-processing.
@humdingercomedy Hi there! A quick question - The comedy night that I am involved in (@comedyincrown) is spinning up another night with the name Humdingers and were trying to use a more suitable handle than @thosehumdingers.
Are you still active and using this handle?
Are you still active and using this handle?