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.
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.
Edit: I have looked at the site, and indeed it has nothing to do with forestry. You would do well to include in the headline the straightforward description that is already in use on the page:
"Forestry: A simple CMS for Jekyll and Hugo sites"
It's probably a Heartbleed style GitHub Pages site for the latest bloat-free Rust rewrite of leftpad, anyway
@jpatters: if you care about this, move it to a .com. I winced.
• 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 concept. Get in touch at firstname.lastname@example.org if you have any specific needs.
You guys should consider replicating the Wordpress model: open-source tools and paid plans for hosting & support.
Don't think that S3 or github pages are too simple for a user to being autonomous in deployment. IMHO typical use case for your product is a tech guyssetting things up for some non tech people to administrate and write content afterwards.
This means the keys are :
- 0 tech steps in administration (no git push, no jekyll generate etc.)
But clearly if this can become an alternative to WP, this is great because devs hate WP and it scales really bad, while static websites is the complete opposite.
Having an interface to edit the blog content is great for us devs who would like to involve non-technical people in the copywriting.
However, I'm wondering about the fit of your solution to your target audience: jekyll users are developers, and use an open source solution they can control and customize.
Why would they want to add a closed-source hosted piece on top of it? Personally it's a no-go for me.
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 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.
Can I buy the software and run it locally? I'm extremely interested for a client, but there is no way they will surrender ownership of their content to a third party - and I sadly won't suggest they do.
I assume they could pay 150-300 bucks for a single-site license and something like 5-6 pages. Their website is very small. Honestly, cook up a license with per n-page fees and I'm sure you'll sell a bunch.
- Does it really need access to my private repos too? I don't get to only let it see public repos? There's a reason some of my repos are private, and I don't really feel comfortable letting a third-party accessing them.
- It's a bit weird that my posts are listed in reverse chronological order.
- Having a way do add a description and required formatting (string, date, int...) to the different YAML Frontmatter fields would be great. Prose.io supports this, for instance, and I think that this is hugely important for non-technical users.
- Why don't I get to see and/or edit the date of my posts?
Your posts should be listed with the most recent first. This seems to be pretty standard across content management systems. However, we will have sorting out into production soon.
I'm not 100% certain what you mean with regards to frontmatter. Right now, when you create a new page/post the fields that show up are determined by the frontmatter defaults (in Jekyll) or the archetype (in Hugo). The type of data that a field accepts is derived from the content in existing fields. We are working on giving the user the ability to change the content type of a given field and to add additional frontmatter fields.
The fields are derived from the frontmatter in a content file. If the content file has a date field in frontmatter, you will see a date field. I realize that Jekyll incorporates the date into the name of the content file so you may not have a reason to add a date field to frontmatter. I'll add that to my todo list.
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 - "That's stupid"
We passed another RV that had a "Forestry" logo on it
Scott - "Or forestry.io"
Jordan - "That's stupid too"
I did a search that night, caravan.io was taken but forestry.io was available :)
Nah, I got nothing.
Requested access though, looking forward to seeing more.
Edit/Addendum: I think this is an interesting service. For what it's worth, I'd rather pay someone to host this type of content with a SLA of some sort.
So, if anyone wants to give that a go, I'd be happy to see this implemented!
However, after adding the website repository, I'm not able to see any posts, is this only for pages? There are some UI issues with page editor on mobile that can be sorted out in beta. Nice product!
Update: I can access posts after changing the URL, but a direct link is missing in the UI.
I will certainly have a look at the issue you are having. Could you contact us via our support tool on the site? Or email us at support at forestry.io.
The mobile landing page plays the video on touchstart which makes it hard to scroll through the page since any touch of the thumbnails, even just for the purpose of scrollong, starts the videos :(
That being said, if you can do without plugins, I would highly recommend using a static site generator as it can reduce your development cost as well as your management cost. There is no backend to build and no server to manage. Forestry is a tool to allow you to take advantage of the benefits of a static site generator from a development and management perspective, and still allow your clients/users to be able to manage their content.
Still the best Jekyll CMS I've seen.
Probably an Admin/Editor/Writer hierarchy where admins can manage both Posts, Pages, and Chunks, and Editors can edit all writers' posts, whereas Writers can only create posts and edit their own. Perhaps Writers could also be restricted to only submitting a post for publication, which the editor could then pull the trigger on.
Chunks are really interesting, but I feel that permissions should be more granular. They're great to collate information about the writers (bio, Twitter, e-mail), but they should probably only be able to edit their own field.
I've just uploaded a Jekyll site, but it failed, the error message could have been more descriptive.
We plan to officially launch our ShowHN within a couple of weeks, so sorry if the marketing site and the documentation is not 100% ready.. but the product is already working, you can signup and start playing with it immediately :)