Why we built Forestry
My friend, Emily, needed a simple website for her restaurant. She’s a chef and didn’t want to deal with the hassle of DNS, hosting, design, etc. As a recovering freelancer, I offered to help.
Normally, I would use WordPress for a site like this, but I was fed up with the headaches that comes with maintaining a WordPress site. So, I took an evening and cranked out a simple 1-page static site.
A Response to Amazon Web Services
My friend (and business partner), Jordan, asked me where I was going to host it but I didn’t know. I wanted to throw it on S3, but didn’t want to be tied to her S3 bucket for the rest of my life. And I knew Emily would never be able to navigate the nightmare-interface that is AWS.
Amazon’s cluttered UI (it reminds me of C-Panel).
We decided to build a more user-friendly interface that allowed us to easily host sites on S3. So we could hand it off to Emily.
Our system for of hosting static sites S3
Feedback from HN
We shared this project on Hackernews and to our surprise, it got a lot of interest and went to the homepage. What people were most excited for was this little CMS feature we had on the side. It wasn’t really built, but we described our plan with some screenshots and said it was “coming soon”.
Hosting Platform Vs CMS
We decided to run a simple test comparing the two directions we could take focus on Hosting or focus on a CMS. Our guts told us there was a bigger need for a CMS and data backed that up (slightly).
StatikCMS - The ad for our fake CMS platform
StatikHost - The ad for our fake hosting platform
Months of hard work
Caught a mistake or want to contribute to the blog? Edit this page on Github!