4
14
u/its_nzr Feb 08 '25
This is cool but, Why not just use GitHub pages?
20
u/m4xshen Feb 08 '25
GitHub Pages is great for static sites, but my system turns GitHub Issues into a full blogging platform. Posts and comments are stored as issues, with a simple interface for writing and publishing.
3
u/its_nzr Feb 08 '25
Nice sounds good. Im thinking of something similar. Right now I’m using gh pages for my website but also thinking about using normal markdowns to be used as blogs. Also i use gist as a config for the website i can dynamically change when needed
4
u/UnconstitutionalRig Feb 08 '25
Hi this is fantastic. Can I also use it? Been looking for something like this. Cause I love GitHub issues for managing CMS basically. They have great text editing tools and even version control for the post and comments!
5
2
54
u/JakeSteam Feb 08 '25
Nice! Reminds me of Giscus, which uses GitHub discussions for comments: https://giscus.app/
4
u/TheTanadu Feb 08 '25
You used the... what? Damn, that's impressive. Quite easy to do from API standpoint, to get data, but... wow, what a feat haha.
1
u/CURVX Feb 08 '25
OP, any caching or revalidation done on the server? Or just SSR'd when client requests?
Rate limiting by GitHub?
1
u/m4xshen Feb 08 '25
Currently, everything is SSR'd on request with no caching. GitHub allows 5000 requests per hour (with personal access token), so caching could be a nice future enhancement.
1
u/mcaruso Feb 08 '25
Does it only render the posts from issues that you (the configured author) have created? Presumably it wouldn't just allow random users to publish blog posts.
4
u/m4xshen Feb 09 '25
I currently only show issues with label
blogas posts. Since other users can't add label to issue, they won't be able to publish post on your blog.2
1
1
u/cugarsoat Feb 08 '25
That’s a great idea. Are there some limitations although I will be researching on it also very soon..
2
u/m4xshen Feb 09 '25
There's a rate limit of 5,000 requests per hour to GitHub API. This could be improved in the future by adding some cache at the server side.
1
u/Advanced_Emphasis609 Feb 09 '25
Is there any downsides of it ?
1
u/m4xshen Feb 09 '25
There's a rate limit of 5,000 requests per hour to GitHub API. This could be improved in the future by adding some cache at the server side.
1
u/zittoone Feb 09 '25
Any reason why the oauth permissions are not just bound to issues ?
issue-blog by Max Shen
wants to access your account
Repositories
Public and private
This application will be able to read and write all public and private repository data. This includes the following:
Code
Issues
Pull requests
Wikis
Settings
Webhooks and services
Deploy keys
Collaboration invites
Note: In addition to repository related resources, the repo scope also grants access to manage organization attributes and organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users.2
u/m4xshen Feb 09 '25
I use OAuth app, which doesn't have fine-grained permission control. It must include these scopes in order to control issues.
1
u/Neomee Feb 10 '25
It could be neat to be able to filter posts by tags or categories. In GH issues case - tags/custom tags. For example, I'm interested, do you have anything around Vim. "Click", "click" - all Vim related "posts".
2
1
2
2
u/Wholelota Feb 08 '25
Love it! I use discord as my sql database and encoded binary data. Data is data just transforms until it fits the required spec 🙃
2
1
1
u/Classic-Dependent517 Feb 09 '25
I just tested your demo site and speed is not that bad although lacks large contents
1
1
1
u/Negative-Magazine174 Feb 10 '25
that's serious issues right there 🤣 well done, i use google sheet as database 💀
1
1
u/Green_Branch_3059 Feb 14 '25
It`s cool! How about adding a tag categorization feature to the blog? It could be implemented using GitHub's issue tagging system, which would work really well.
1
1
-16
1




45
u/doesnt_use_reddit Feb 08 '25
This is brilliant! It doesn't go against any terms of use though, does it?