141–150 of 187 posts
Built vote by mail website for Florida ( https://www.stampthevote.com ) using a single JSON file with 1500 zip codes and Gatsby.js and deployed with Netlify. Great to be in the future and not have to worry about hosting a server for such a simple site.
How to Vote in Clay County (undefined)
Plug for my site: https://www.joshuahu.io/
So much praising so little talk about its limits. I consider myself to be kinda stick in a Rails way of thinking. But most projects I touch heavily depend on a backend, database, or raw computing power. Everything that doesn't fall in those categories is something I create static (ex nanoc.) i just build out locally push to my git and let a post-commit hook do the Copy pasta. My static Web server runs without attenti…
I don't quite get this. I'm a long time Heroku user and this seems to be much more limited and not much better in any dimension, why is this so popular? This is an honest question, I just don't quite get why there's so much excitement in the comments. Thanks!
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
I run destinysets.com, a companion site for the video game Destiny 2, and I cannot say how much of a life saver it has been for me. Not only are deploys as simple as a git push, but I also get next-level things like "preview environments" for pull requests _for free_. The PR preview environments are super important to me because there's a lot of curated data that powers the site, as JSON files in the repo, and I acce…
I'm also a very happy Netlify user. Their product seems years ahead of other tools. My favorite thing is that you can now manage DNS and generate SSL for all domains with a single click. Perfect for static sites, SPAs, etc.
Earlier quoted context omitted.
Yeah, we integrate pretty deeply already. We do have some new flows that could potentially make the story around publishing to Netlify from GitLab cloud seamless from an authentication standpoint, would be happy to brainstorm!
Great, please send an email to kirsten@ our company domain with a link to this comment and we'll discuss.
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
Can you edit (say Jekyll blogs) on GitHub and them somehow push to Netlify automatically? This is critical for me since I edit using my Android Jekyll-optimized tool Teddy Hyde ( https://play.google.com/store/apps/details?id=com.EditorHyde... ).
Netlify connects to GitHub and rebuilds your site automatically when a change is made in the master branch. There's no technical setup – you just connect to your GitHub account with their UI.
I used to use GitHub Pages to host my blog, but Netlify provides more features and it's also free.
Earlier quoted context omitted.
The advantage is that the resulting website being just static pages will be much faster and secure that your hosted wordpress. And compared to wix etc, you have a lot more control on the appearance and structure of your website, because you can use wathever static website builder you choose
How is it more secure when you're still accessing an API? Wordpress itself might not be the best product but other fully-hosted services are all the same, whether they render the site or just give you an API. A CDN is equally fast when the content is cached, and if you're building the entire site as static pages then it's not really a dynamic site in the first place and can also be done with HTML or markdown in the s…
It only accesses the API with a read-only token during the build process.
> it's not really a dynamic site in the first place and can also be done with HTML or markdown in the same repo
This is definitely true and was an option we considered, however colocating hundreds+ posts with code made the repo unnecessarily heavy and slowed our build time drastically. Our content creators also didn't want to use git to edit their content (they would have to learn git / or use the web UI which is a suboptimal editing experience), nor did I want content creators in our repos.
> The fine control seems the be the only real advantage, at the cost of more moving pieces.
Lots of other advantages that I won't outline here, but our data is completely decoupled from our frontend now, so we can do cool stuff like crossposting to different properties via webhook, data cleanup via API (I ran all the blog posts from WP through some remark tools so we have a more standard look and feel), etc... Might not be the right setup for you, but it works really well for us!
i dont get why i should use netlify over aws? what is the advantage here, i might give it a try.
Earlier quoted context omitted.
CSS """expert"""
Chris Coyier is pretty well known in the front end community. He created CSS-Tricks and co-founded CodePen. If anyone can claim to be an expert it's him. But if you're just trying to have a laugh at CSS - well, that's fine too I guess.