sgallant

15 ms·

121.
by sgallant 7y ago
Forestry.io | Senior Ruby/RoR Software Engineer | Remote | Full-Time Forestry.io | Intermediate Ruby/RoR Software Engineer | Remote | Full-Time Forestry.io | Front-end Developer | Remote | Full-Time & Part-Time Forestry.io | D
122.
by sgallant 7y ago
Co-founder of https://forestry.io here. The author describes how writers can use branch logic (i.e. merging as an editorial tool). We're currently building multi-branch support into our CMS for just this. If you want early
123.
by sgallant 7y ago
Forestry.io ( https://forestry.io ) | Remote | Full-Time & Part-Time Forestry.io is a content management system for sites built with tools like Gatsby, Jekyll, and Hugo (static site generators or the "JAMstack"). We
124.
Static E-Commerce with Hugo and Snipcart(snipcart.com)
3 points by sgallant 7y ago|0 comments
125.
by sgallant 8y ago
Does this work with Netlify Large Media?
126.
by sgallant 8y ago
Forestry.io ( https://forestry.io ) | Remote | Full-Time We are a small, engineering-focused team. Forestry.io is a content management system (CMS) for static websites that are built with tools like Jekyll, Hugo, Gatsby, etc. Deve
127.
by sgallant 8y ago
Have you considered using a service like Cloudinary.com, imgix.com or github.com/thumbor/ (open source) for image transformations? IMO, they're a much better way to handle variations of your images.
128.
by sgallant 8y ago
Just discovered Tilt last weekend. Great project.
129.
by sgallant 8y ago
Forestry.io ( https://forestry.io ) | Remote | Full-Time We are a small, engineering-focused team. Forestry.io is a content management system for static websites that are built with tools like Jekyll, Hugo, and Gatsby (static site
130.
by sgallant 8y ago
https://forestry.io just launched beta support for Gatsby (like today). Forestry.io is a CMS for markdown + Git, where all edits get committed to your repo. If you want access to the beta, message the folks at support@forestry.i
131.
by sgallant 8y ago
I agree with most of this, but if you like programming and front-end development, I would suggest you focus on getting REALLY good at that first. Optimize for learning and master your craft. If you become among the top 5% - 10% of front-end
132.
by sgallant 8y ago
Hugo is a single executable with no dependencies
133.
by sgallant 8y ago
Good job! We see many orgs adopting this approach for the same reasons you mentioned (disclaimer: we build a CMS for these sites https://forestry.io ). The healthcare.gov site might be a good comparison for your team. It was a la
134.
by sgallant 8y ago
I didn't realize how amazing this project was until I used it the first time. It's by far the quickest way to go from new site to writing frontend code.
135.
by sgallant 9y ago
Lol! Great investigation!
136.
by sgallant 9y ago
True. We use it for our Algolia search index too (documented here: https://forestry.io/blog/search-with-algolia-in-hugo/ )
137.
by sgallant 9y ago
If you're new to Hugo's custom output formats, this is a great example of what you can do with it. https://gohugo.io/templates/output-formats#output-formats
138.
by sgallant 9y ago
We use Hugo + Algolia (search) + Formspree + AWS. We disabled commenting (but used to use Disqus). You can read about our set up here https://gohugo.io/showcase/forestry/
139.
by sgallant 9y ago
This is the second part of a 2-part series on using the Hugo static site generator. Part one is here: https://forestry.io/blog/up-and-running-with-hugo/
140.
Hugo Static Sites (part 2): GitHub and Forestry (CI and CD)(forestry.io)
16 points by sgallant 9y ago|1 comments
141.
Ask HN: What was the most effective dev team that you’ve been a part of?
1 points by sgallant 9y ago|0 comments
142.
Hugo static search with Algolia(forestry.io)
17 points by sgallant 9y ago|2 comments
143.
Bulletproof Jekyll Search with Algolia and Webtask(forestry.io)
9 points by sgallant 9y ago|0 comments
144.
by sgallant 9y ago
Happy to hear that! We (forestry.io) would love any feedback you might have.
145.
by sgallant 9y ago
I 100% agree that there are many factors to take into account. Liquid templating is a huge benefit of Jekyll, for example. This article was just looking at build times and we'll put another one out soon looking at other factors.
146.
by sgallant 9y ago
If you run a Jekyll or Hugo site (or other), we would love to know what your build times are. For example: Static Site Generator: Jekyll Approximate number of pages: 200 Build time: 3.4 seconds
147.
Hugo vs. Jekyll: Benchmarked(forestry.io)
26 points by sgallant 9y ago|5 comments
148.
by sgallant 9y ago
Static site generators are very WYSIWYG friendly, see my comment above about our Jekyll and Hugo CMS. https://news.ycombinator.com/item?id=16254696
149.
by sgallant 9y ago
We're helping bridge the gap for non-technical users with our Jekyll and Hugo CMS ( https://forestry.io ). There are many other options too, just check out https://headlesscms.org . It's an exciting time to b
150.
by sgallant 9y ago
Wow, we're paying A LOT more than we need to.

More ›