Show HN: Convert a GitHub repository into a CMS

Re:Show HN: Convert a GitHub repository into a CMS by roryokane on Wednesday May 28, 2014 @08:21PM (#7813879)

Yeah, I expected that too but it doesn’t. Instead, it generates a Rails app for you that you have to host yourself, but in the configuration for that Rails app, you point it to a GitHub repository that contains the content of the site. The idea is that you can use the full power of Rails to manage how the content in the content GitHub repository is displayed, such as requiring password logins to sections of the site.

See https://github.com/codemy/writefully#why-dont-you-just-use-s... for more differences from GitHub Pages.

[ Parent | on HN ]

Re:Show HN: Convert a GitHub repository into a CMS by jaytaylor on Wednesday May 28, 2014 @08:37PM (#7813929)

Why start with a full-blown ruby app for something like this? What is the drawback to starting simple with a git+markdown based statically generated site?

[ Parent | on HN ]

Re:Show HN: Convert a GitHub repository into a CMS by artellectual on Thursday May 29, 2014 @01:54AM (#7814948)

If your trying to build a site that will allow you to sell digital goods, you are going to have problems if you use a static site.

With writefully the idea is you get real business objects you can build business intelligence into. So for example I only want users who buy a piece of content to be able to view it, I can do that with associations or some sort of logic to detect who bought what. It's difficult to do that sort of thing with static sites.

[ Parent | on HN ]

Re:Show HN: Convert a GitHub repository into a CMS by intull on Thursday May 29, 2014 @08:24PM (#7819460)

Won't this logic be open source then? In some cases, business rely on such logic and would want to hide it. How would writefully handle that?

[ Parent | on HN ]