41–50 of 93 posts
Earlier quoted context omitted.
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.
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.
"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.
Earlier quoted context omitted.
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.
After you read the first three words of the main headline "a simple CMS", the chances that the site has anything to do with foresting are marginally small and thus not worth exploring.
Plans for middleman support?
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…
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.
- 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?