I would like to seek advice on a couple of use cases regarding our service.
We have a few questions based on our service’s requirements.
1. Cursor-Based Pagination
Assuming we store user-generated content in Squidex, we anticipate accumulating at least 100,000 new content items each month. Our users will view this content through an infinite scroll interface.
From our initial review, it seems that Squidex does not support cursor-based pagination. We also need the ability to efficiently view and manage this large volume of content in the admin panel.
Cursor-based pagination is a critical requirement for us. Is there any way to achieve this?
2. Cross-App Content Referencing
Is it possible to reference content from one app within a different, separate app?
Our use case involves multiple teams working on individual services, but they often need to use a shared pool of content and assets. This scenario is especially frequent in services like games. (This is similar to the feature known as “Link content across multiple spaces” in other headless CMS contentful).
We are curious if there are any official plans to support these two features in the future.
I am not sure about this. It really depends on the implementation, if this works at all. I think the main requirement is the necessity of an index. I am not sure if it is possible to implement an efficient cursor-based-pagination for general queries.
2. Cross-App Content Referencing
There are no plans for it yet. You could implement it with a custom editor, but it raises a lot of questions around security.
I’m considering migrating from Contentful to Squidex.
I asked the previous questions because I manage UGC (user-generated content).
As you mentioned, it’s not necessary to apply these features to internally produced content.
Cursor pagination is a crucial element for UGC, so I’ve been exploring its capabilities.
I will look into the code to see if I can achieve both content references and cursor pagination in this scenario using an Extension.
Squidex.Domain.Apps.Entities.Contents.Repositoriess.IContentRepository : Stores the content itself. It can be challenging to implement the filtering.
Is it possible to achieve this problem with extensions in this sentence?
(I would appreciate any additional feedback you might have.)
If cross-app references are possible with a custom editor, I will also investigate that further.
Thank you.
Not the cursor pagination. This requires an update of the core logic. But I am not sure yet how it would solve the problem here and how it would look like. I have to dig more into that.