4 ms·

There are couple great solutions that fit points you describe. One of them is Statamic (https://statamic.dev/blade https://statamic.dev/blade) which is IMO the

by mirzap 4y ago

There are couple great solutions that fit points you describe. One of them is Statamic (https://statamic.dev/blade https://statamic.dev/blade) which is IMO the best flat-file CMS currently available with a lot of flexibility if you're dev and want to extend to it (it's free for solo writers). Another one that I know is GravCMS (https://getgrav.org/ https://getgrav.org/). I didn't have much experience with Grav, but it looks OK.

mg 4y ago
These projects are gigantic: git clone https://github.com/statamic/cms.git cd cms git ls-files | wc 3133 find . -name '*.php' | xargs wc -l ... 225023 total 3133 files. 225023 lines of PHP code. Plus dependencies, which are not counted here. I am going for 1 file with 50 lines of code and no dependencies.
- mirzap 4y ago
  Good luck with that. Personally I don't see a point in avoiding dependencies. I'll always trust more software that is built on collective wisdom with carefully picked dependencies, rather than a single (or couple) geeks that put everything in single file, avoiding dependency hell. To me that's a red flag.
  - mg 4y ago
    With a single script with 50 lines of code, I will forever be able to pick it up again, understand it, use it, improve it. Handling will be quick. No installation, just copy the script, run it, done. Using a project made of thousands of files and dependencies, there is way more maintenance ahead. Handling is slower and more cumbersome. If the project moves in a direction I don't like, maintaining a fork would be too much work.
naetd 4y ago
I have to work on a legacy site using statamic v2 regularly and I absolutely hate it; it's slow as all hell and littered with template rendering and parsing bugs. I'm sure v3 is nicer though from the amount of times I've searched the docs with an issue and seen "fixed in v3".

by mirzap 4y ago

mg 4y ago

These projects are gigantic: git clone https://github.com/statamic/cms.git cd cms git ls-files | wc 3133 find . -name '*.php' | xargs wc -l ... 225023 total 3133 files. 225023 lines of PHP code. Plus dependencies, which are not counted here. I am going for 1 file with 50 lines of code and no dependencies.

mirzap 4y ago
Good luck with that. Personally I don't see a point in avoiding dependencies. I'll always trust more software that is built on collective wisdom with carefully picked dependencies, rather than a single (or couple) geeks that put everything in single file, avoiding dependency hell. To me that's a red flag.
- mg 4y ago
  With a single script with 50 lines of code, I will forever be able to pick it up again, understand it, use it, improve it. Handling will be quick. No installation, just copy the script, run it, done. Using a project made of thousands of files and dependencies, there is way more maintenance ahead. Handling is slower and more cumbersome. If the project moves in a direction I don't like, maintaining a fork would be too much work.

naetd 4y ago

I have to work on a legacy site using statamic v2 regularly and I absolutely hate it; it's slow as all hell and littered with template rendering and parsing bugs. I'm sure v3 is nicer though from the amount of times I've searched the docs with an issue and seen "fixed in v3".