This is the type of thing I wish I would use my skills for. Instead I'm jealous and going to use it. Got it set up in 5 minutes, now to work on my post backlog.
Show HN: Pages CMS – A CMS for GitHub
91–100 of 122 posts
Re: Show HN: Pages CMS – A CMS for GitHub
#92amazing concept, would be even more amazing if you could be able to deploy this on other places besides github pages. (cloudflare pages?) or anything else..
Re: Show HN: Pages CMS – A CMS for GitHub
#93amazing concept, would be even more amazing if you could be able to deploy this on other places besides github pages. (cloudflare pages?) or anything else..
i see is supported already, could be neat to setup blogs thank you
Re: Show HN: Pages CMS – A CMS for GitHub
#94This is great as it is, but I would love to see support for posts in plain HTML. There's a huge potential for static sites generated by Webflow and other platforms like it. Hosting costs are the biggest issue with these platforms. It would help so many designers and marketing teams that don't have access to a developer or simply don't want (or don't know how) to set up themselves a Jekyll, Next.js, Astro, Hugo, or Nu…
So are you saying that you would appreciate an editor that saves your posts in plain old html?
Any preference of storing said posts in a database or .mdx markdown file?
Re: Show HN: Pages CMS – A CMS for GitHub
#95This is great as it is, but I would love to see support for posts in plain HTML. There's a huge potential for static sites generated by Webflow and other platforms like it. Hosting costs are the biggest issue with these platforms. It would help so many designers and marketing teams that don't have access to a developer or simply don't want (or don't know how) to set up themselves a Jekyll, Next.js, Astro, Hugo, or Nu…
You can save `.html` and `.mdx` single files, I just don't have great support for collections yet (I'll need to sort out a few things as right now it expects a frontmatter to display the table).
Re: Show HN: Pages CMS – A CMS for GitHub
#96If you don’t have an existing repo/site, can you start from scratch via this webui/CMS to create a new repo/site via some sort of SSG boilerplate/template etc? If that’s not already there it might be a good feature to add.
Re: Show HN: Pages CMS – A CMS for GitHub
#97If you don’t have an existing repo/site, can you start from scratch via this webui/CMS to create a new repo/site via some sort of SSG boilerplate/template etc? If that’s not already there it might be a good feature to add.
I was working on it last week and dropped it to make this release.
On the home screen you'll have the ability to choose from a few repos to fork with pre-configured CMS: vanilla, Next.js, Astro, 11ty, Hugo, Jekyll...
I'm still curating the projects I'll be using as a starting point, so do let me know if there are templates for your favorite SSG that you'd like me to consider.
The more challenging feature is building a configuration wizard that figures out your content structure for you. I think this will adoption a lot as the main friction right now is around getting a working config file up and running.
Re: Show HN: Pages CMS – A CMS for GitHub
#98This looks and sounds great...
I'm currently using contentlayer [https://github.com/contentlayerdev/contentlayer] to manage docs and blog content, mostly .mdx files on urlbox.com.
It works well with next.js but unfortunately is abandonware now.
I also have a few custom remark/rehype plugins.
You're right it is a pain to update articles buried in your repo especially with less technical team members. I already tried out TinaCMS to try and solve the editing issues, but their editor wasn't so nice, and it seemed to implicitly make a commit on every tiny change to any content, so I'm really hoping I could use something like this to edit my already existing content...
Re: Show HN: Pages CMS – A CMS for GitHub
#99Is 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)?
Re: Show HN: Pages CMS – A CMS for GitHub
#100Is 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 }