Version 2.0.0 - use github issues as posts & add comments feature! #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
todo: - add pagination after 10 posts - add reactions section from post object
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Use GitHub Issues as blog posts instead of Contentful API, and add comments feature.
Why?
I'm inspired by the blog from swyx.io that uses GitHub issues and comments, as mentioned here.
The friction of writing a GitHub issue is less daunting than using a fully-fledged CMS like Contentful, because you have to log in to their page, navigate to the content section, host the images yourself, etc.
This will (hopefully) lead to more writings in the future 🤞
Changelog
github-blogandutterancesscripts for comments feature.Deployment Notes
GITHUB_TOKENenvironment variables