Bludit Community Support Forum

Hello,
Before I start the process of creating 1000s of pieces of content and tagging them using an elaborate taxonomy, I would like to understand the limitations of Bludit.

I like it that it's filesystem based and not dependent on SQL.

However, I noticed that all the article content is stored in a single file!

Also, concerned about the tags.

I want to use it as a headless cms for the most part.

What are the limitations you can think of or gotchas?

I could of course deploy multiple bludit instances given that it is light weight.. but before I do that it will help to understand physical limitations.

Every Page is an own single file but all meta data of all pages are stored in one single file. With this concept, Bludit performs with 1000s of pages, but if you use the meta data (tags, custom fields, e.g.) too much, the meta data file gets bigger than in normal use cases like blogs or normal websites. I'm not sure if it's the best case for you.

Maybe other, real headless cms, could be better for you. For examples Cockpit (getcockpit.com).