TLDR: I thought it would be for sites that are heavy on charts, searches, or other forms of data analysis, but it isn't. Clance also is planning on moving to Po

TLDR: I thought it would be for sites that are heavy on charts, searches, or other forms of data analysis, but it isn't. Clance also is planning on moving to Postgres. ---- I don't really "get" this. A lot of the comments here are focused on SQLite, but the page clearly says: > Clace currently runs on a single node. When multi-node support is added later, the plan is to use a shared Postgres database instead of using local SQLite for metadata and file data storage. Let's start with some basics: 1: What problem is Clance trying to solve? (IE, did the authors encounter problems hosting / generating static sites, and Clance is designed to solve a specific problem they had?) 2: Why can't Clance be multi-node today? (What potential problems would happen if I had multiple Clance nodes pointed to the same database, or github repo?) Naively, I thought Clance wasn't serving truly static sites; IE, I thought Clance would be serving sites that allow querying static / infrequently changing data. I thought it would be for sites that are heavy on charts, searches, or other forms of data analysis.