You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read this interesting blog about using daily deploys on netlify to 'schedule' blog posts.
Essentially the posts are given a date in the future, and the static site generator doesn't process them until that date is in the past. The author set up Netlify to redeploy his site daily - so when the post he'd already pushed eventually had a date in the past, it gets rendered that day.
I think you could probably do this now with Eleventy using permalink=false and some javascript testing for the current date - but not very cleanly as the templates need extra code to make it work.
Cleaner would be config in eleventyConfig - which people could make conditional depending on whether they're running in production or dev
Possibly if draft support comes to eleventyConfig, that might support this too. Something like:
I read this interesting blog about using daily deploys on netlify to 'schedule' blog posts.
Essentially the posts are given a date in the future, and the static site generator doesn't process them until that date is in the past. The author set up Netlify to redeploy his site daily - so when the post he'd already pushed eventually had a date in the past, it gets rendered that day.
I think you could probably do this now with Eleventy using permalink=false and some javascript testing for the current date - but not very cleanly as the templates need extra code to make it work.
Cleaner would be config in eleventyConfig - which people could make conditional depending on whether they're running in production or dev
Possibly if draft support comes to eleventyConfig, that might support this too. Something like:
The text was updated successfully, but these errors were encountered: