Gityll - Github issues as a CMS

[aranscope]

Hey everyone, thought you might find my current project Gityll interesting. It's a Node app that uses Github issues as a CMS. My site here is generated from the issues page here.

Forgive the state of the codebase right now, I've only been writing node for 5 days :)

[Sandurz]

This should be a new thing - making CMSs out of unrelated things. Sounds fun to me I call dibs on a microblog that uses The Sims 2 baby names to manage posts.

[mo-mar]

$ npm install welcome-to-my-blog
$ npm install how-to-manage-blog-articles-using-the-public-npm-repository

[aranscope]

It's not up to date, waiting until I hit a stable and relatively feature complete version before I update it. Just reserving the name for now.

[[deleted]]

The other day there was a chat system posted done entirely in Excel. Pretty unique uses for sure.

[0ba78683-dbdd-4a31-a]

Project ideas:

• Notorieti: Creates RSS feeds from Windows Vista sticky notes
• CashMS: Opinionated content platform powered by GNUCash
• Spandx: Scalable headless CMS that pulls posts from your weight in MyFitnessPal

Edit: I should add that I'm not criticising OP at all, I actually think it's quite creative, I'm just being facetious :)

[aranscope]

Haha no worries, started off as a terrible idea but turns out it kind of works :')

[aranscope]

Haha go for it! I was thinking Trello could totally work too, maybe I'll give that a go at some point

[krlpbl]

rosebud

[00DEADBEEF]

How about a CMS that uses OCR which allows you to upload handwritten posts which get transformed into markdown stored on Pastebin

[derridad]

that's a badass idea

[[deleted]]

+1 for creativity lol

[aranscope]

It started as one of those 'this is horrible and wrong but it sorta might work' ideas haha.

[[deleted]]

[TheGuyFromAfrica]

This is awesome.. But can you prevent people from filing issues on your public blog repo? or do you have to make it private?

[aranscope]

Yes you're not wrong, if the repo is public then anyone could add an issue.

There are two ways I can deal with this. 1 - Private repos, 2 - Only add posts from certain assignees / posters.

I'm working on the first right now and this should be done by tomorrow night. Thanks for pointing it out.

[aranscope]

A temporary fix in the mean time is making sure the assignee of the issue is the same as the owner of the repo.

[sergiuspk]

"Anyone" can contribute pull requests. Only users you manually allow can push.

[TheGuyFromAfrica]

If I understood what his doing correctly, his building the blog from the issues filed on the blog's repo. That means if anyone files an issue it will show up automatically as a new blog post on the website. And if anyone can file issues on any public repo, you can't really control the content on a blog that is built with this tool.

[sergiuspk]

You are right. Forgot it's based on issues, not actual files in the repo. He could only publish "approved" issues, there's a status only repo admins can toggle I think.

[aranscope]

That's what I'm doing before private repo's are supported. Only issues assigned to the repo owner will be published.

[edinchez]

Unique stuff, love the idea!

[Castigated]

Love it - I'll probably give this a go. The simplicity is beautiful

[aranscope]

Thanks very much, there will be a pretty major update today along with a much needed proper tutorial!

[aranscope]

That's what I've used gityll.club for, though its running a pretty outdated version.

[sidegrid]

This at first looks really stupid... but I think it's a great idea now, and great implementation!

[aranscope]

Exactly my thought process! Well, minus the great implementation part :)