great work with the explainer video etc.
good luck w/ the project @ OP.
Show HN: Pages CMS – A CMS for GitHub
101–110 of 122 posts
Re: Show HN: Pages CMS – A CMS for GitHub
#102I randomly found this a few days ago was planning on giving it a shot. Thanks for sharing!
I was always looking for a good web interface for Hugo. Static site generators are nice...but sometimes you really just want to drag and drop and image and write a short post without all the extra hassle of moving the file to the post directory, linking it with the file name in the post, then preview is broken because of some path issues etc.
Re: Show HN: Pages CMS – A CMS for GitHub
#103Very nice! It looks a bit like Publii [0], but the editor part is cloud hosted instead of running as an app on your machine. [0] https://getpublii.com/
I've not tried it yet, it looks pretty slick.
It is quite nice, but since there is no way to configure URLs, it‘s best used for greenfield projects, not moving from some other CMS with a differing URL structure.
Re: Show HN: Pages CMS – A CMS for GitHub
#104Earlier quoted context omitted.
If you can send me screenshots at hunvreus@gmail.com or file an issue on GitHub ( https://github.com/pages-cms/pages-cms/issues ), I'd love to fix it. > Tried it out [1], and with a bit of work got it to function. Media, posts, all seem to upload and be viewable. With the lead-in, kind of thought it was going to be "click-a-button, you're done." However, had to wander around a bit figuring out what format zones in th…
Opened new issue at https://github.com/pages-cms/pages-cms/issues/3 with documentation. On the second comment, kind of figure it was a WIP currently, hence suggestions. Thanks for the work, as its a fairly light weight way to have a quick little CMS.
I rolled out a hotfix release, let me know if that fixed it.
Re: Show HN: Pages CMS – A CMS for GitHub
#105This looks cool but I moved all my repos to a self-hosted forge when GitHub openly and notoriously refused to stop collaborating with ICE (that runs concentration camps in Texas). It would be nice to have this support generic/arbitrary git servers. I’ve been feeling this pain point for a while and have been considering building something like this myself.
I am looking into GitLab and Bitbucket, but I don't plan on supporting generic Git, unless I can find a way to slap an API in front of it. I'll add that to the backlog.
Maybe you could add support for Gitea? It’s a pretty handy way to slap an API in front of git and it’s much simpler to self host than GitLab.
Re: Show HN: Pages CMS – A CMS for GitHub
#106Earlier quoted context omitted.
I am looking into GitLab and Bitbucket, but I don't plan on supporting generic Git, unless I can find a way to slap an API in front of it. I'll add that to the backlog.
Maybe you could add support for Gitea? It’s a pretty handy way to slap an API in front of git and it’s much simpler to self host than GitLab.
Aspects of the API look fairly similar to GitHub actually. I'll look into it.
Re: Show HN: Pages CMS – A CMS for GitHub
#107Earlier quoted context omitted.
Maybe you could add support for Gitea? It’s a pretty handy way to slap an API in front of git and it’s much simpler to self host than GitLab.
Aspects of the API look fairly similar to GitHub actually. I'll look into it.
How much of your API is dependant on GIT like semantics and how much could work with "plain files" storage?
It's neat to be able to transplant a CMS on top of other services that don't necessarily deploy by CI pipes, I made a DAV plugin(basic auth) for Netlify (back before the forks) so as long as a server supported listing(only DAV dependency really), GET, PUT and DELETE you could just plunk down the CMS files somewhere and point to the DAV share.
Re: Show HN: Pages CMS – A CMS for GitHub
#1081. Does the template have to look like that, or can I have almost any template I want ?
2. does the repo have to be public?
Re: Show HN: Pages CMS – A CMS for GitHub
#109I have tried and tried to make Decap cms work for my huge go hugo site. I just could never make it work without refactoring a LOT of my code.
I just tried this out, and after an hour of work, I managed to get it working for my weird use case! It's way slicker and better performant than decap. Fantastic job!
The main issue I've had with Decap and Front Matter:
I have a flat file with hundreds of entries for a _collection_. (Yes, I know I'm misusing this, but I don't have time to refactor everything)
But for my use case, I don't want to have a folder with a file for each entry. I want a flat yaml to act as the collection.
Re: Show HN: Pages CMS – A CMS for GitHub
#110Is there a way to configure this with media colocated with posts (i.e., not in a /media folder but in/a/post/subfolder/image.png)?
Both the content collections and media can filter by file extension so you could very well have something like: media: input: posts output: /posts categories: [ image ] content: - name: posts label: posts type: collection path: posts fields: - { name: title, label: Title, type: string } - { name: body, label: Body, type: rich-text } The collection of posts will only show the `md` files (that's the default, but you co…
Interesting. I need to dig into this because this looks like a good solution to my editing dilemma. Thank you for the work, and for the response.