Show HN: Convert a GitHub repository into a CMS | Hacker News Reader

Show HN: Convert a GitHub repository into a CMS

writefully.codemy.net

41 pointsartellectual13 comments

I probably don't understand fully the concept of taxonomies in general, but it seems strange to me that the a custom taxonomy would inherit from Tag? What is the relationship between a taxonomy and a tag? In prose I mean, not in code. What is the result of applying the tag taxonomy as well as a custom one in terms of end-user experience on a hypothetical front-end of what this CMS would power, that is, what would the simplest example of the playlists taxonomy allow one to display?

I feel that the Tag is the most simple kind of taxonomy, I mean there is absolutely no business ideas in them, they are just there so you can tag multiple things with different keywords. The playlist on the other hand since it inherits from tag I could potentially add some features to it, like only a certain group of user can access certain playlists.

In terms of the significance to end user, being able to put different types of taxonomy into different "named" groups help people visualize them differently, I feel. People think of tags differently from playlists. Hence if you try out the filters on the posts page of our site, you can only view one playlist at a time, but you can activate multiple tags at once.

I hope that helps.

Wait, why does the video use a remix of Cro - "Easy" as background music? I was very surprised listening to some German rap suddenly.

This doesn't use Github pages isn't it? The title kind of misled me.

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.

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?

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.

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?

Is there any thing to do this?

can this be deployed to heroku? #noobquestionhere

Since it is a rails app, yes, that would be the case.

The current version of writefully might not work, as when the writefully process accepts a web hook from github, it does a pull into a directory to sync the data. Heroku doesn't allow you to do things like that.

We are thinking of a way to make it possible on heroku though.

thanks for the explaination

Reply on news.ycombinator.com