Work with @ingridepure!
(And some other rather excellent and lovely people at @Netlify) https://twitter.com/opinionatedpie/status/1126818887880859653
(And some other rather excellent and lovely people at @Netlify) https://twitter.com/opinionatedpie/status/1126818887880859653
@bruised_blood @jaffathecake note to self: all "site loading..." status bars should be a row of the correct number of floppy disks.
💾💾💾💾💾...
💾💾💾💾💾...
@mongoaron @Netlify Absolutely.
You can see some info (and ask for more, if you have some specific questions) in the Netlify Community.
https://community.netlify.com/t/common-issue-using-the-command-line-interface-to-manually-link-a-git-repository/140
You can see some info (and ask for more, if you have some specific questions) in the Netlify Community.
https://community.netlify.com/t/common-issue-using-the-command-line-interface-to-manually-link-a-git-repository/140
"CMSs" seems to win out.
But to the 40 or so who opted for "CMCSSinJS"... who hurt you? https://twitter.com/philhawksworth/status/1125717180778201089
But to the 40 or so who opted for "CMCSSinJS"... who hurt you? https://twitter.com/philhawksworth/status/1125717180778201089
@swyx @preetster @Netlify Yeah, this can seem a bit fiddly.
It's like when I sometimes built sites on the LAMP stack which didn't have a database, but did use PHP and Apache on a Linux sever. I didn't consider that to be a stack that needed a new name.
It's like when I sometimes built sites on the LAMP stack which didn't have a database, but did use PHP and Apache on a Linux sever. I didn't consider that to be a stack that needed a new name.
@rem @eleven_ty No, it does. “yarn start” runs a gulp task which watches for changes and compiles the css and js into a location where @eleven_ty expects to include them from. And @eleven_ty is watching for changes too, so any code and content changes get live reloaded.
@davidbrunelle @stubbornella This sounds really good. Looking forward to watching the video of that one.
@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. 🤓