Stephen Davies, Javier Velez-Morales, & Roger King (2005), "Building the memex sixty years later: trends and directions in personal knowledge bases", Department of Computer Science, University of Colorado at Boulder. The Wikipedia article on personal knowledge bases (PKBs) is basically a summary of the technical report. The report defined personal knowledge base systems, described their benefits, reviewed relevant fields of research, and compared systems in terms of several aspects of their data models: structural framework, knowledge elements, schema, and the role of transclusion. This report is the most comprehensive publication I've read that compares PKB systems according to their key features.

They should be well-organized and easy for customers to locate the information they need. 

More than anything, however, consumers want to find answers on their own. A study by Forrester confirmed that customers prefer knowledge bases over all other self-service channels. This is likely because the vast majority of customers want an immediate response to their customer service question — 90%, in fact.

A knowledge base is a self-serve online library of information about a product, service, department, or topic. 

A knowledge base (KB) is a technology used to store complex structured and unstructured information used by a computer system. The initial use of the term was in connection with expert systems; which were the first knowledge-based systems.

About the argument against it, "{@const will make code less consistent ": I think the same is true now, since people can come up with very different ways of dealing with the "computed value inside each loop/if function" problem. Some extract components, some use functions, some will prepare the array differently beforehand.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.