I've thought about building this a million times. For the people that don't understand it, it's web UI managed Jekyll that takes those web changes and puts them into git/github (presumably GitHub) so that you get the auto-deploy feature of Jekyll based GitHub pages. Kudos and good luck.
Forestry.io
21–30 of 93 posts
Re: Forestry.io
#22Earlier quoted context omitted.
Hahaha. Co-creator here. I know, it's silly. Here's how we came up with it: My partner and I used to drive 2 hours to meet our team every Monday at our old startup. We conceived of the idea on one of these drives and the conversation went like this: Jordan - "So what are we going to call this thing?" Scott - "I don't know, some cool .io name?" We passed an RV that had a "Caravan" logo on it Scott - "Like caravan.io"…
Jordan was right.
Agreed. Still not sure what it does.
Re: Forestry.io
#23Is this like how http://prose.io/ is with github? I've been using that and it works ok, though sometimes things don't seem to take the first time.
Re: Forestry.io
#24Co-creator here. I was building a website for someone last summer and I REALLY didn't want to use WordPress, so my friend and I built forestry.io. Some highlights: • Supports all Jekyll plugins • Integrates with GitHub & Bitbucket (commits back to your repo) • Zero configuration for you project • Hosting not provided (deploy to S3, Github Pages, FTP) • Use Markdown or WYSIWYG I'd love to know what you think if the co…
Hey -- this seems really cool, especially for one Jekyll site I manage but want a nontechnical person to be able to update. I found a bug(?) though -- I linked it to a site deployed on S3 and published a test post, and it pushed all the newly built files to s3, but didn't set them to the public-read ACL, so I got AccessDenied errors on refresh until I logged into s3 and manually set them public myself.
Edit: Another piece of feedback -- it's really awesome that it picks up on my custom frontmatter when editing posts, but when I create a new post, none of the custom frontmatter fields are there. Can I enter the frontmatter in the WYSIWYG or is there some other way to add it?
Re: Forestry.io
#25I went there to read some forestry information and I couldn't see the wood for all the trees!
Re: Forestry.io
#26I was actually looking for a CMS I could use for my dad's forestry company. I could set up the server and design, and he could log in to change the content.
Re: Forestry.io
#27Co-creator here. I was building a website for someone last summer and I REALLY didn't want to use WordPress, so my friend and I built forestry.io. Some highlights: • Supports all Jekyll plugins • Integrates with GitHub & Bitbucket (commits back to your repo) • Zero configuration for you project • Hosting not provided (deploy to S3, Github Pages, FTP) • Use Markdown or WYSIWYG I'd love to know what you think if the co…
Hey -- this seems really cool, especially for one Jekyll site I manage but want a nontechnical person to be able to update. I found a bug(?) though -- I linked it to a site deployed on S3 and published a test post, and it pushed all the newly built files to s3, but didn't set them to the public-read ACL, so I got AccessDenied errors on refresh until I logged into s3 and manually set them public myself. Edit: Another…
Hey,
Co-creator here.
In regards to the first issue, we assume that you have applied Amazon's recommended bucket policy as per https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteAcces.... We do this in case the website being deployed isn't meant to be publicly available.
Re custom frontmatter, with Jekyll we respect the defaults that are set in your config (https://jekyllrb.com/docs/configuration/#front-matter-defaul...). If a post matches a type or path that is specified in a default, we make those fields available in the post. We have come to realize that this feature of Jekyll isn't used as often as it should be (it's really useful) and are working on giving users the ability to add fields to their posts.
Re: Forestry.io
#28If I were you, I would rethink your "beta invite" flow. Adding an email address and clicking on the "Request Invite" button doesn't send you an invite, it adds you to their MailChimp newsletter list and sends an email asking you to confirm your address (for opt-in). There is no invite code or protected page, anyone can just go to https://forestry.io/beta to sign up. Don't trick me into opting in to your newsletter wh…
I'd just add a disclaimer about the newsletter to what he's already doing. I don't like email marketing either, but it works ridiculously well. No marketer would do what you're suggesting.
Re: Forestry.io
#29Just out of narcissistic curiosity, I would be interested to know where you got the design inspiration from. It looks super similar to one of my services, although you have executed it with more polish!
Re: Forestry.io
#30If I were you, I would rethink your "beta invite" flow. Adding an email address and clicking on the "Request Invite" button doesn't send you an invite, it adds you to their MailChimp newsletter list and sends an email asking you to confirm your address (for opt-in). There is no invite code or protected page, anyone can just go to https://forestry.io/beta to sign up. Don't trick me into opting in to your newsletter wh…
I'd just add a disclaimer about the newsletter to what he's already doing. I don't like email marketing either, but it works ridiculously well. No marketer would do what you're suggesting.
> I don't like email marketing either, but it works ridiculously well. No marketer would do what you're suggesting.
Note that the framework is not necessarily for the average person, who would respond in a certain way to your average email marketer. It is ostensibly "Built for devs who hate bloat."
Tricking someone into signing them up for a newsletter they didn't sign up for by way of a beta invite form is bloat of the malicious sort. I would say that while marketing to your target group, it is something you should avoid.