@ChrisFerdinandi @Netlify soon.
😓✍️😎
Note to self: Learn more @gohugo which makes things like this easy (when you know how)
2nd note to self: Branch deploys on @Netlify used to feel like a luxury. Now I can't imagine being without them. https://twitter.com/philhawksworth/status/952147565113376768
2nd note to self: Branch deploys on @Netlify used to feel like a luxury. Now I can't imagine being without them. https://twitter.com/philhawksworth/status/952147565113376768
@AndiSmith @GoHugoIO Solved. (thanks to a helpful hint from @brycekahle)
Now my multi-paragraph summaries are properly formatted. From this:
https://css-styled-summaries--hawksworx.netlify.com/blog/isomorphic-rendering-on-the-jam-stack/
to this:
https://styled-summaries--hawksworx.netlify.com/blog/isomorphic-rendering-on-the-jam-stack/
thanks to this:
Now my multi-paragraph summaries are properly formatted. From this:
https://css-styled-summaries--hawksworx.netlify.com/blog/isomorphic-rendering-on-the-jam-stack/
to this:
https://styled-summaries--hawksworx.netlify.com/blog/isomorphic-rendering-on-the-jam-stack/
thanks to this:
@ChrisFerdinandi @zachleat Gotcha!
It sounds to me like some case studies on how and why @smashinmagazine moved all their membership content, subscriptions, identity, and ecommerce to #JAMstack on @Netlify could not come soon enough.
https://www.smashingmagazine.com/2017/11/from-cats-with-love-welcome-the-new-smashing-membership/
#CracksNuckles
It sounds to me like some case studies on how and why @smashinmagazine moved all their membership content, subscriptions, identity, and ecommerce to #JAMstack on @Netlify could not come soon enough.
https://www.smashingmagazine.com/2017/11/from-cats-with-love-welcome-the-new-smashing-membership/
#CracksNuckles
@megatomche @GoHugoIO @Netlify Nice!
https://tomche.space/post/creating-hugo-and-netlify-powered-website-from-scratch-part-2-deploy/
Good tip about putting the @GoHugoIO version in your netlfiy.toml. And noting that you could even run different versions for different build contexts if you were developing against a snazzy new version that you're not yet ready to use in production
https://tomche.space/post/creating-hugo-and-netlify-powered-website-from-scratch-part-2-deploy/
Good tip about putting the @GoHugoIO version in your netlfiy.toml. And noting that you could even run different versions for different build contexts if you were developing against a snazzy new version that you're not yet ready to use in production
@ChrisFerdinandi @zachleat Even so, I'm looking forward to seeing how you got on dabbling with static sites :)
Also interested to learn what you're using WP to do which can't be done on the #JAMstack.
One of these days we'll get to have a proper chinwag about the possibilities, limitations and surprises.
Also interested to learn what you're using WP to do which can't be done on the #JAMstack.
One of these days we'll get to have a proper chinwag about the possibilities, limitations and surprises.
Delighted to see how @austintexasgov is avoiding vendor & technology lock-in by exploring #JAMstack & #HeadlessCMS approaches to managing & publishing content.
This thoughtful article by @MateoClarke nicely shares the thinking behind that. Looking forward to seeing the progress. https://twitter.com/MateoClarke/status/951130759322095617
This thoughtful article by @MateoClarke nicely shares the thinking behind that. Looking forward to seeing the progress. https://twitter.com/MateoClarke/status/951130759322095617
@calavera @Eiskis @Netlify @contentful I trigger lots of builds for one of my sites though @contentful. Although @Netlify's build scheduler is smart, my build notifications felt healthier after configuring Contentful to fire the build hooks only on publish events, instead of saves (which were after most keystrokes)
#AskMeGate continues.
Looking at you, @Casablanca and various other @Osmosoft-y coffee lovers.
https://www.hawksworx/ask-me
Looking at you, @Casablanca and various other @Osmosoft-y coffee lovers.
https://www.hawksworx/ask-me
Finding lots of handy git alias nuggets in this talk by @kannonboy at last year's https://git-merge.com/ conference.
https://www.youtube.com/watch?v=3IIaOj1Lhb0
https://www.youtube.com/watch?v=3IIaOj1Lhb0
@MikeRiethmuller @GoHugoIO Yeah. I define where it splits by using a comment as per:
https://gohugo.io/content-management/summaries/#summary-splitting-options
I guess I could create a macro which derived .NotTheSummary by subtracting .Summary from .Content ... but that feels a bit heavy handed as it seems like a variable which might already exist.
https://gohugo.io/content-management/summaries/#summary-splitting-options
I guess I could create a macro which derived .NotTheSummary by subtracting .Summary from .Content ... but that feels a bit heavy handed as it seems like a variable which might already exist.
@AndiSmith @GoHugoIO I write a meta description in the front matter, but ideally I want the content all to be in the body of the source files. More flexibility.
As a stop gap, I do indeed style the first paragraph with css. But some summaries span more than one para or include an image.
As a stop gap, I do indeed style the first paragraph with css. But some summaries span more than one para or include an image.
SWOOONING at this hot doggle https://twitter.com/cobra_winfrey/status/951195152957235200
@HeyDesigner A good companion to https://www.staticgen.com/ which lists (oh so very many) static site generators. Glueing the two together with some good automation can really make #JAMstack sites fly!
@yoavrheims @Netlify A quick clarification about the 3 deploys per minute - it applies to API-requested deploys, and not anything triggered by webhooks or continuous deployment (where the majority of deploys get triggered). So it's unlikely to ever be a ceiling you'll bump into.