Me personally I'd like to see something that supports easily creating and using different types of objects besides pages (such as: events, books, recipes, etc.), like content types and fields and views in wordpress or drupal, ideally aligned with schema.org like https://www.drupal.org/project/schemadotorg I think Hugo might support content types in YAML or something.
Show HN: Pages CMS – A CMS for GitHub
51–60 of 122 posts
Re: Show HN: Pages CMS – A CMS for GitHub
#52Any word on S3 media support? I have a few content heavy sites. And that would be essential to be practical to switch to.
Re: Show HN: Pages CMS – A CMS for GitHub
#53Good to see further development in this space. Would be interesting to see how it compares to Decap CMS https://decapcms.org/ and Static CMS https://www.staticcms.org/ Me personally I'd like to see something that supports easily creating and using different types of objects besides pages (such as: events, books, recipes, etc.), like content types and fields and views in wordpress or drupal, ideally aligned with schem…
Disclaimer: I used to work a lot with Drupal 10+ years ago. I more or less wanted the same kinds of features in Pages CMS.
Re: Show HN: Pages CMS – A CMS for GitHub
#54Re: Show HN: Pages CMS – A CMS for GitHub
#55Why do I have to give access to all my public and private repos instead of selecting the ones I want to give it access to?
Why do you need full access to all of my GitHub repositories?
Well, the GitHub API kinda sucks when it comes to OAuth scoping. Pages CMS relies on the OAuth App flow, which doesn't allow for granular permissions. The alternative would be to use the GitHub App flow instead, but:
It's a lot more complicated and would require us to store and orchestrate a lot more in the backend.
Since we need to impersonate users (for things like commits), we anyway need to request user tokens, which technically would give us the same access as with the OAuth App flow.
However, we do not store your GitHub OAuth tokens in the backend. The serverless functions used to facilitate the OAuth login pass the OAuth token to the front-end, allowing it to directly communicate with the GitHub API.
And if you still don't trust the online version, you can deploy your own version for free in less than 10 minutes our Cloudflare Pages.
Do let me know if I got some of this wrong (@hunvreus), and feel free to suggest improvements in the issue queue.
Additionally I've added the support for Fine-grained PATs [1], allowing you to use a repository specific token. You'll see the button that reads "Sign in with a Fine-Grained PAT" on the login screen.[1] https://github.blog/2022-10-18-introducing-fine-grained-pers...
Re: Show HN: Pages CMS – A CMS for GitHub
#56Why do I have to give access to all my public and private repos instead of selecting the ones I want to give it access to?
TLDR:
> Well, the GitHub API kinda sucks when it comes to OAuth scoping. Pages CMS relies on the OAuth App flow, which doesn't allow for granular permissions.
Re: Show HN: Pages CMS – A CMS for GitHub
#57EDIT: I didn't have a `media` entry in my pages.yml, which meant the rich text editor wasn't loading (JS error was being thrown). When I added that entry, it started working! Brilliant work! I'm using Jekyll, with yaml frontmatter, and it's not clear how to specify the body. The documentation says that a rich text field could be set up with a "name" option (and gives "body") as an example but my Markdown files don't…
I rolled out a hotfix, this should be fixed. Thanks for the feedback.
Re: Show HN: Pages CMS – A CMS for GitHub
#58Looks very nice. Any comparisons against other github based CMS? Personally I've been using Keystatic.
I've not tried it yet, but isn't that running on your local machine? Looks pretty good though.
Re: Show HN: Pages CMS – A CMS for GitHub
#59Why do I have to give access to all my public and private repos instead of selecting the ones I want to give it access to?