@dceddia @elijahmanor Yeah, this might be the issue. By design if an asset exists on the requested URL Netlify will serve that rather than applying a redirect rule.
Forcing (with a !) overrides that.
If you’re still having trouble http://community.netlify.com has lots of helpful people and info
Forcing (with a !) overrides that.
If you’re still having trouble http://community.netlify.com has lots of helpful people and info
@benmvp @elijahmanor Netlify redirects support that behaviour. You can have as many URLs as you like redirecting or rewriting to the same resource. In fact you can respond with any http response code you like.
The default (when no response code is specified) is to use a 301 redirect.
The default (when no response code is specified) is to use a 301 redirect.
This laid back hip hop playlist put together by @dnsandnick is making me unspeakably happy and productive today.
https://open.spotify.com/playlist/0FYPPpJ0HQ00tMhCNUo6mY
https://open.spotify.com/playlist/0FYPPpJ0HQ00tMhCNUo6mY
It's a constant perf party in @eleven_ty land at the moment!
This site scaffold from @cramforce is full of wonderful nuggets. Worthy of your attention!
https://www.industrialempathy.com/posts/eleventy-high-performance-blog/
This site scaffold from @cramforce is full of wonderful nuggets. Worthy of your attention!
https://www.industrialempathy.com/posts/eleventy-high-performance-blog/
@sebastienlorber @zachleat @slightlylate @kylemathews @youyuxi @swyx @sarah_edo @Rich_Harris @eleven_ty I think we can clearly distinguish between the modes/models... but the way one uses the tools can also have an influence. That's why I mentioned their "default".
1. Pre-rendered.
2. Client-side rendered.
3. Hybrid. (Pre-rendered with progressively enhanced client-side rendering)
1. Pre-rendered.
2. Client-side rendered.
3. Hybrid. (Pre-rendered with progressively enhanced client-side rendering)
@sebastienlorber @zachleat @slightlylate @kylemathews @youyuxi @swyx @sarah_edo @Rich_Harris I typically use @eleven_ty to pre-generate all of my views and serve them as HTML. But I could add some JS to that to progressively enhance and fetch JSON of subsequent pages, rendering them with client-side JS.
Many tools can be used for either model of we choose.
Many tools can be used for either model of we choose.
@sebastienlorber @zachleat @slightlylate @kylemathews @youyuxi @swyx @sarah_edo @Rich_Harris If a view of the content is generated in the browser with javascript, I consider that a client-side render.
Gatsby absolutely does client-side rendering. That rendering can happen as an enhancement for subsequent pages after the entry point is delivered as pre-rendered HTML.
Gatsby absolutely does client-side rendering. That rendering can happen as an enhancement for subsequent pages after the entry point is delivered as pre-rendered HTML.
@sebastienlorber @zachleat @slightlylate @kylemathews @youyuxi @swyx @sarah_edo @Rich_Harris The tricky thing is that although these have different defaults, all these tools can be used in builds to employ each model (with additional JS for some).
I think of the 2 models as pre-rendered/ready-rendered and client-side rendered.
I think of the 2 models as pre-rendered/ready-rendered and client-side rendered.
@gregiv_es @eleven_ty I'm going to have a proper play soon. But it looks wonderful! And big love for the excellent readme! ❤️
@tkg_codes @stackrole @jlengstorf @cassidoo @shortdiv @sarah_edo @Tzmanics We'll listen to all the others, and we'll let you know in our podcast if there is anything you need to hear.
Cool?
Cool?