Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Grav is a modern open-source flat-file CMS

getgrav.org

Post reply on HN
Print view View original

41–50 of 69 posts

Re: Grav is a modern open-source flat-file CMS

#41

Post by tethys »

WA wrote: post #39
k4runa wrote: post #35

Earlier quoted context omitted.

Statamic is great for simple sites but for larger or multilingual sites it has lots of problems. I have a 5000+ page website that the static site generator takes 3 hours to build and there's been no improvement since v3 launched. You can use their "Static Caching" as an alternative to static generating but for my project requirements I need a purely static site. I'm busy doing a huge rewrite and switching to using St…

A very big German newspaper ( https://www.spiegel.de/ ) runs on Statamic and they probably have an order of magnitude more pages. But not sure what kind of improvements/custom implementations they've done.

This Statamic blog post has (at least some) insights: https://statamic.com/blog/statamic-at-spiegel-scale-2

> So how does SPIEGEL do it?

> Curious about how SPIEGEL’s stack works? Here’s their high level approach, keeping in mind this is running on v2. Upgrading to v3 streamlines even more of their stack.

> A huge flat file content store organized with each entry inside its own subdirectory (you can’t have more than 10k files inside a single directory, an operating system limitation)

> The content store is using a cloud storage solution.

> Statamic’s control panel pushes entries into the content store, and then into an ElasticSearch instance via message queue.

> ElasticSearch runs as a content API with blazing fast response times and is consumed by the control panel and front-end

> The front-end is built in Go.

> User accounts are connected with an Office 365 Active Directory integration with OAuth.

Re: Grav is a modern open-source flat-file CMS

#43

Post by sacnoradhq »

k4runa wrote: post #35
fideloper wrote: post #3

Oh, it's PHP - neat. Personally I think Statamic is the entry to beat for flat-file CMSes in the PHP space. This project is the Symfony flavor I suppose (vs Statamic being based on Laravel).

Statamic is great for simple sites but for larger or multilingual sites it has lots of problems. I have a 5000+ page website that the static site generator takes 3 hours to build and there's been no improvement since v3 launched. You can use their "Static Caching" as an alternative to static generating but for my project requirements I need a purely static site. I'm busy doing a huge rewrite and switching to using St…

Is or isn't Asana still mostly powered by Statamic?

Re: Grav is a modern open-source flat-file CMS

#44

Post by fbnlsr »

manuelmoreale wrote: post #7
fideloper wrote: post #3

Oh, it's PHP - neat. Personally I think Statamic is the entry to beat for flat-file CMSes in the PHP space. This project is the Symfony flavor I suppose (vs Statamic being based on Laravel).

Personally think https://getkirby.com is the entry to beat but I guess it’s just because I’m used to it and it works incredibly well for my use case.

I've had the pleasure to build a small website with Kirby and it was such a joy to use as a developer. The only problem I faced was with my client as he was used to Wordpress and making the transition to Kirby was a bit rough for him.

Re: Grav is a modern open-source flat-file CMS

#45

Post by sacnoradhq »

65 wrote: post #19

If only it wasn't built with PHP. We need a batteries included, non-headless, open source CMS for Node.js. Headless is pointless for the vast majority of use cases, so I don't really understand why Node.js developers keep making them. It's funny how CMSs follow the same design patterns based on the language. PHP CMSs are generally the same, Node.js CMSs are generally the same.

It's depressing when there's excessive imitation without differentiation leading to lack of innovation and too many similar options that lack advantages.

In case people were wondering: https://en.wikipedia.org/wiki/Headless_content_management_sy...

Most small shops and individuals want an integrated CMS that has an admin interface AND serves the content while handling content versioning, storage, and publication. If a site grew, then it might be worth revisiting which components should be separated.

Re: Grav is a modern open-source flat-file CMS

#46

Post by sacnoradhq »

xupybd wrote: post #28
anditherobot wrote: post #24

Earlier quoted context omitted.

Because PHP is bad or because you personally don't like PHP?

I think they just want it in Node.

Rewrite it in*

Maybe in a utopian future, there will be a universal seamless ABI for most dynamic and static languages such that rewriting will be both unnecessary and undesirable.

Re: Grav is a modern open-source flat-file CMS

#47

Post by revskill »

Sorry, nowadays i use json file to store metadata, then query with asql (sql for json), then parse the markdown to browser.

Frameworks need to die, just give the fuck core libraries to work across frameworks, or you get "vendor locked-in" sooner or later.

Re: Grav is a modern open-source flat-file CMS

#48

Post by withinboredom »

revskill wrote: post #47

Sorry, nowadays i use json file to store metadata, then query with asql (sql for json), then parse the markdown to browser. Frameworks need to die, just give the fuck core libraries to work across frameworks, or you get "vendor locked-in" sooner or later.

How does that work for multiple editors that aren’t programmers?

Re: Grav is a modern open-source flat-file CMS

#49

Post by merlincorey »

After reviewing the Basics Tutorial[0] I have a few reasons I don't like it, but others may:

- It is not purely Flat File based, but rather a specific Folder structure with specifically named and marked up Files in them

- URL Routing is implicit in your folder structure; however

  + URL Routing has some special cases wherein:

    a. Folders named starting with digits and a dot (i.e. "04.") will be "ordered"
    b. Folders named starting with digits and a dot (i.e. "04.") will be "included in the navigation menu"
    c. Folders named starting with digits and a dot (i.e. "04.") will be have the digits and dot removed in the URLs
    d. It is unclear what "unordered" pages mean
    e. It is unclear how to escape the starting numbers and dot so that they are included, but maybe just doubling "04.04." would work
- Page metadata such as HTML Meta Title and special CSS classes are included in a special header of the Markdown content - Page template is determined by the actual filename within the URL routed folder rather than in the Page metadata

Personally, I would prefer a simpler "flat file" format that simply mapped folders and files to URLs in a more naive manner. Metadata being in the page is fine and can totally include the Template that I want to use for that content. Metadata within a page could also include the "ordering" and "menu" information.

That said, I'd possibly prefer a declarative mapping somewhere of my templates to folder and file patterns and a declarative mapping of my menus to specific files rather than including that data within the content file.

Maybe I should start a side project.

[0] https://learn.getgrav.org/17/basics/basic-tutorial

Re: Grav is a modern open-source flat-file CMS

#50

Post by javier2 »

twic wrote: post #9

What is a flat-file CMS? What are CMSs that aren't flat-file? How many CMSs are there now? How come people are still making more? Why isn't this a boring, fairly stable commodity category the way web servers or something are?

CMSes cover wildly different needs and editors want all kinds of weird things in their articles. And they still need full control of the publishing. This leads to lots of work for us. And I dont even work on cms activity. I also think its weird that this is not more consolidated. One observation: dynamic langauges tend to be more succesful here, possibly because it is faster to make simple plugin systems and simpler to make one-off articles.
Post reply on HN