@jvhellemond @Netlify Hooray!
And it’s lovely to see a @fronteers site on @Netlify!
\o/
@jvhellemond @Netlify We don't currently support regex or negative matches. But since we honour the first rule we find that matches, I wonder if something like this would do what you need?
/static/* /static/:splat 301
/* /some-place/:splat 301
/static/* /static/:splat 301
/* /some-place/:splat 301
@eugenekudashev @pugson @NotionHQ @Netlify _redirect needs to be in your published site directory, and might look like this:
/from-here-relative-to-root https://to-here.com 301
More info and some added short url fun based on that...
https://www.hawksworx.com/blog/find-that-at/
/from-here-relative-to-root https://to-here.com 301
More info and some added short url fun based on that...
https://www.hawksworx.com/blog/find-that-at/
@rem @eleven_ty Not the answer, but a nice related tip: I like defining my templates in the eleventy config. It makes them easier to move around and is handy if you're moving to @eleven_ty from another SSG like Jekyll, where you might already have declared your layouts.
https://github.com/philhawksworth/eleventyone/blob/master/.eleventy.js#L10
https://github.com/philhawksworth/eleventyone/blob/master/.eleventy.js#L10
@rem @eleven_ty I often set this for each folder where I collect content types, like a blog.json file to define things for all the pages in my /blog folder.
https://github.com/philhawksworth/hawksworx.com/blob/master/src/site/blog/blog.json
...but I must admit, I'm not sure how to do this in the root folder. I'd like to.
https://github.com/philhawksworth/hawksworx.com/blob/master/src/site/blog/blog.json
...but I must admit, I'm not sure how to do this in the root folder. I'd like to.
RT @pixelpioneers: We announced the final speaker for @pixelpioneers Bristol (7 June) yesterday, which means the lineup is now complete. He…
@andypimlett @Netlify It's not a good look for me, but I can do this shit all day. 🤓
@andypimlett @Netlify No? And I was ready to talk about how those butlers/pages/minions seemed destined to deliver the news with an air of inevitability. With no doubt that the update would be delivered to the easel and attached securely to be available in perpetuity. Like @Netlify's build bots & ADN.
@andypimlett @Netlify Think of the easel as the edge cache, which is close to the camera lenses of the users. The notice meanwhile, was written on velum using the finest fountain pen, back in the palace (or decoupled build environment, if you prefer).
Your move, Andy!
Your move, Andy!
@stefanjudis (It's the new hotness. What? You don't even put your CMS in your CSS in your JS?)
@miklb @github @WorkingCopyApp @Textastic @Netlify I still feel like doing a victory dance any time I do that!
Congratulations to @CompuIves, @NikkitaFTW, and what I imagine will be a quickly growing team @codesandbox, following their $2.4M seed round!
@codesandbox has always been an amazing project to watch. they'll be unstoppable now!
https://codesandbox.io/post/CodeSandbox-Raises-2-4M-Seed-Round-led-by-Kleiner-Perkins
@codesandbox has always been an amazing project to watch. they'll be unstoppable now!
https://codesandbox.io/post/CodeSandbox-Raises-2-4M-Seed-Round-led-by-Kleiner-Perkins
@qubyte @callumacrae Yes, much "content".
I'm thinking about when comparing many "systems which manage content", or many CMS's ( 👈 which seems like the best answer to me, so far)
I'm thinking about when comparing many "systems which manage content", or many CMS's ( 👈 which seems like the best answer to me, so far)
Cutting to the chase with the most pressing question about e-commerce at @JAMstack Conference in New York.
https://youtu.be/oRG1E0xLB4U?t=177
https://youtu.be/oRG1E0xLB4U?t=177