Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Forestry.io

forestry.io

Post reply on HN
Print view View original

31–40 of 93 posts

Re: Forestry.io

#31

Post by schneidmaster »

jpatters wrote: post #27
schneidmaster wrote: post #24

Earlier quoted context omitted.

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-…

Ah got it, that all makes sense. Thanks for the response! :)

Re: Forestry.io

#32

Post by jpatters »

chrsstrm wrote: post #13

If 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…

Co-creator here. We certainly didn't intend for this feeling and have removed the Mailchimp form. There is now just a direct link to the signup page.

The people that signed up to the beta invite list will not be subscribed to our newsletters unless they sign up to Forestry and choose to opt into our newsletter. Mailchimp was simply an easy way for us to manage a list of people interested in the service. Having the list and not linking to forestry.io/beta was just our way of saving development effort. We were merely creating an artificial control over who could sign up.

Rest assured that any users that have not signed up to Forestry and opted into newsletters will be sent nothing but an invite to the beta.

Re: Forestry.io

#33

Post by if_by_whisky »

parennoob wrote: post #30
if_by_whisky wrote: post #28

Earlier quoted context omitted.

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…

I agree you should be aboveboard

Re: Forestry.io

#34

Post by ryanSrich »

sethjgore wrote: post #19
ryanSrich wrote: post #11

Earlier quoted context omitted.

This was my initial thought as well. We used siteleaf for around 6 months until we outgrew it.

What were the factors that caused you to outgrow it? I'm curious

At 300+ pages the compile time became an issue. We started to build very custom layouts that didn't necessarily lend themselves to a typical CMS. On top of that we trasitioned our core marketing content to hubspot, while our highly directed pages remained static.

Re: Forestry.io

#35

Post by sakopov »

Cerium wrote: post #16
sippeangelo wrote: post #5

"Forestry". Really? I can understand many other hot startups using names of random objects, but using the name of an entire completely different profession?

I was excited at the prospect of an API service offering up to date forestry data.

Ditto. That's the only reason i clicked on the link.

Re: Forestry.io

#37

Post by b34r »

It's like the heavens have been listening to me! I've been studying static site generators and needing a non-technical editing solution... Looks like this might fit the bill.

Re: Forestry.io

#38

Post by sgallant »

lxcid wrote: post #17
sgallant wrote: post #14

Co-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…

Cool site. May I ask is your WYSIWYG custom made?

We're using Redactor.

Re: Forestry.io

#39

Post by BinaryIdiot »

sippeangelo wrote: post #5

"Forestry". Really? I can understand many other hot startups using names of random objects, but using the name of an entire completely different profession?

Yeah I'll admit it took me way too long to try and figure out what this website had to do with foresting before I realized it was absolutely zero. I scrolled, read and clicked around way to make to try and make sure I wasn't missing something.

Re: Forestry.io

#40

Post by sgallant »

rubiquity wrote: post #21

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.

Thanks!!
Post reply on HN