Smaller is better – The rise, fall, and rise of flat file software
1–10 of 152 posts
Re: Smaller is better – The rise, fall, and rise of flat file software
#2As someone not overly backend proficient, I love the concept of flat-file. I just rebuilt my blog with another flat file CMS, literally finished it last night, and today I am reading this article and think, whether WonderCMS may have been a better choice.. but, no I won't start over.
The CMS I picked is PicoCMS - what flat file stuff have you used and can recommend? And probably important, how well does it scale? I cant give much input here, my blog has 21 posts so.. no ceiling in sight yet.
Here I made a post where I ramble a bit about blog systems, as far as I got in contact: https://riidom.eu/posts/021_en
Re: Smaller is better – The rise, fall, and rise of flat file software
#3Flat file websites make sense when you have a blog and such. I don't even know why you'd use a CMS when Next.js or SvelteKit can just generate all the pages from a folder with markdown files. Just write your content in Markdown or pull your content in at the static build stage and your content is ready to go.
Can anyone explain how sites like Flatboard handle user input into a flat file system? How do they handle conflicts with just one file? What's the workflow and set up like — can you use serverless or do you have to have a full server?
Re: Smaller is better – The rise, fall, and rise of flat file software
#4As someone not overly backend proficient, I love the concept of flat-file. I just rebuilt my blog with another flat file CMS, literally finished it last night, and today I am reading this article and think, whether WonderCMS may have been a better choice.. but, no I won't start over. The CMS I picked is PicoCMS - what flat file stuff have you used and can recommend? And probably important, how well does it scale? I c…
Before you worry about 1 million daily visitors. Worry about 50 daily visitors.
Re: Smaller is better – The rise, fall, and rise of flat file software
#5Flat file websites make sense when you have a blog and such. I don't even know why you'd use a CMS when Next.js or SvelteKit can just generate all the pages from a folder with markdown files. Just write your content in Markdown or pull your content in at the static build stage and your content is ready to go. Can anyone explain how sites like Flatboard handle user input into a flat file system? How do they handle con…
Funny you mention SvelteKit - my former blog version was written with Svelte/SvelteKit (using the static adapter).
I wrote a bit about why I went away from this, but in a nutshell: I am not using "modern" deploying techniques, and upping the compiled blob each time I write a new post felt like a huge drag to me. This is a general problem pretty much baked into SSG's, but I have hope that someone will adress this problem in near future.
Re: Smaller is better – The rise, fall, and rise of flat file software
#6As someone not overly backend proficient, I love the concept of flat-file. I just rebuilt my blog with another flat file CMS, literally finished it last night, and today I am reading this article and think, whether WonderCMS may have been a better choice.. but, no I won't start over. The CMS I picked is PicoCMS - what flat file stuff have you used and can recommend? And probably important, how well does it scale? I c…
Before you worry about 1 million daily visitors. Worry about 50 daily visitors.
Also it’s waaay easier to scale the flat file solutions to a million visitors.
Re: Smaller is better – The rise, fall, and rise of flat file software
#7Flat file websites make sense when you have a blog and such. I don't even know why you'd use a CMS when Next.js or SvelteKit can just generate all the pages from a folder with markdown files. Just write your content in Markdown or pull your content in at the static build stage and your content is ready to go. Can anyone explain how sites like Flatboard handle user input into a flat file system? How do they handle con…
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repository or build scripts required.
Re: Smaller is better – The rise, fall, and rise of flat file software
#8Flat file websites make sense when you have a blog and such. I don't even know why you'd use a CMS when Next.js or SvelteKit can just generate all the pages from a folder with markdown files. Just write your content in Markdown or pull your content in at the static build stage and your content is ready to go. Can anyone explain how sites like Flatboard handle user input into a flat file system? How do they handle con…
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repository or build scripts required.
i've found that folks without git experience are fine to use github.com as a cms when you take 20 minutes to show them how to edit, submit as a pr, and check the preview deployment before merging
Re: Smaller is better – The rise, fall, and rise of flat file software
#9Flat file websites make sense when you have a blog and such. I don't even know why you'd use a CMS when Next.js or SvelteKit can just generate all the pages from a folder with markdown files. Just write your content in Markdown or pull your content in at the static build stage and your content is ready to go. Can anyone explain how sites like Flatboard handle user input into a flat file system? How do they handle con…
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repository or build scripts required.
There are some really nice tools out there that bridge that gap, like Forestry:
Re: Smaller is better – The rise, fall, and rise of flat file software
#10Earlier quoted context omitted.
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repository or build scripts required.
i've found that folks without git experience are fine to use github.com as a cms when you take 20 minutes to show them how to edit, submit as a pr, and check the preview deployment before merging
Yep.
There is a long line of people complaining that git is hard to learn on the internet. But I've never met anybody on the real world that had any problem with the basic cycle of edit - push - review - accept (or the even simpler edit - push).