@mbleigh @slightlylate @jensimmons But it's a fair comment. The term "static site generator" doesn't really describe all the things that these sometimes bundle in.
@mbleigh @slightlylate @jensimmons It's common now for SSGs to roll in a JS framework too. Which can be great, but can also mean you need to know what that does and how so you don't mishandle it and cause yourself problems.
@jensimmons - It allows a variety of templating tools
- It feels logical & organised
- It has a small technology footprint (so is easy to install)
- I can extend it with JS (which I understand)
And a biggie for me...
- It only outputs what you ask. No frameworks or unexpected JS magic.
- It feels logical & organised
- It has a small technology footprint (so is easy to install)
- I can extend it with JS (which I understand)
And a biggie for me...
- It only outputs what you ask. No frameworks or unexpected JS magic.
@heydonworks @eleven_ty Likewise
@FinalBullet Yes! In Pocklington, near York.
I still have my old PE teacher’s shouts of “GET OFF THE APARATUS!” ringing in my ears from when we were too eager and started dangling from it before given the say so.
I still have my old PE teacher’s shouts of “GET OFF THE APARATUS!” ringing in my ears from when we were too eager and started dangling from it before given the say so.
@ludobourgoin @Netlify Yep. You can make your own page for the thank you message. And tell @Netlify to send people to that by specifying it as the "action" property of your form html element.
@uhhyeahbret Nailed it.
@trysmudford @GoHugoIO Yeah! Not only does this bring an update to the Linux distro, but it also adds the ability to select the build image used by the build bots for each of your sites.
Making future distro rollouts far easier.
Double win!
Making future distro rollouts far easier.
Double win!
Phil Hawksworth
@philhawksworth •
Phil Hawksworth
@philhawksworth •
By crikey, that @bruised_blood is a talented chap! I'm currently soaking up all the beautiful pixels in his glorious portfolio, please don't disturb me from my happy place. https://twitter.com/bruised_blood/status/1106188151599648768
@_munter_ @SaraSoueidan Oh, that's nice.
This approach also attempts to address the need to perform those image transformations at build time, which can slow builds down of you have many many images.
This approach also attempts to address the need to perform those image transformations at build time, which can slow builds down of you have many many images.
@_munter_ @SaraSoueidan Assetgraph did this too? I might misunderstand. How would it do these on-the-fly transformations directly on the CDN at request time?
That's mostly what I'm demonstrating here. The macro for html generation is a pretty common utility in SSGs, right?
That's mostly what I'm demonstrating here. The macro for html generation is a pretty common utility in SSGs, right?
@SaraSoueidan You bet.
The @eleven_ty part is just a helper to output the markup for the picture element. @GoHugoIO could do that bit too.
@Netlify Large Media gives you sensible version control of this large source image assets and automatic asset transformation on-the-fly.
The @eleven_ty part is just a helper to output the markup for the picture element. @GoHugoIO could do that bit too.
@Netlify Large Media gives you sensible version control of this large source image assets and automatic asset transformation on-the-fly.
@SaraSoueidan Pssst. You might be there already.
https://twitter.com/philhawksworth/status/1105862954300395525
https://twitter.com/philhawksworth/status/1105862954300395525
@StuRobson @eleven_ty @frctl 🤔 Wondering what in my little boilerplate project might demand that.
For what it's worth, I install node and npm via nvm to make my life a little easier if I need to jump around to different versions on different projects.
For what it's worth, I install node and npm via nvm to make my life a little easier if I need to jump around to different versions on different projects.
Phil Hawksworth
@philhawksworth •
I made a little example of using @Netlify's new image transformation service along with a shortcode in @eleven_ty (but you could use any SSG in this way) to generate the markup and assets for responsive images using the <picture> element.
https://example-nlm-picture.netlify.com
https://example-nlm-picture.netlify.com
@johnlindquist @Netlify I love this too. And I use it a lot for quick-starting projects.
You can even feed it more configuration to set up more of the environmental pieces if you need to.
Super handy if you have a list of project boilerplates, like you might have at an agency.
https://www.netlify.com/docs/deploy-button/
You can even feed it more configuration to set up more of the environmental pieces if you need to.
Super handy if you have a list of project boilerplates, like you might have at an agency.
https://www.netlify.com/docs/deploy-button/
@tudor_prodan @healves82 @smakosh @gatsbyjs @GraphQL @HasuraHQ @Netlify If the friction in deploying is low, and your confidence in automated deploys is high, this model works really nicely. It means your site can stay fresh without you needing to manage a server to keep it alive.
My own site redeploys every time I tweet.
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
My own site redeploys every time I tweet.
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
@healves82 @tudor_prodan @smakosh @gatsbyjs @GraphQL @HasuraHQ @Netlify If only this were up to me!
Prepare for... HawkStack™
I think we should use whichever term makes it easiest to communicate what the architecture is. #JAMstack has been getting more broadly understood, but I've also heard:
- StaticFirst
- Pre-rendered
- ShortStack
& more!
Prepare for... HawkStack™
I think we should use whichever term makes it easiest to communicate what the architecture is. #JAMstack has been getting more broadly understood, but I've also heard:
- StaticFirst
- Pre-rendered
- ShortStack
& more!
@qlex_ @Netlify Most odd. 🤔
Would you mind contacting the support team? They are usually in a much better position to help with this sort of thing.
Reach them via http://netlify.com/support
Would you mind contacting the support team? They are usually in a much better position to help with this sort of thing.
Reach them via http://netlify.com/support