I've been tasked with looking into how we could improve the editor experience when working with one of our main Prismic repositories. Currently, it's really sluggish when listing and editing content, and gives bad error messages every time we try to update/publish content, the editor shows "could not publish" error messages, yet, it still publish content, it seems to get stuck and timeout on the POST prismic.io/documents/<id> request.
The main problem I believe might cause this behavior is the large number of tags fetched (30k+) and handled in the Write Room frontend code on several requests. This has been an ongoing issue since the start when the content got imported from a previous WordPress backend.
My thought process atm has been to find a way to A, consolidate and reduce the number of tags somehow, B, change to a custom tag system (as outlined in Create a custom tagging system - FAQs - Prismic People), and C, move the content to an inhouse system with direct write-/read access to the data.
The roadblock I've hit right now is how to proceed with either option. Mainly the lack of finding a way to programmatically update the Prismic content. Suppose I could go through all articles with a spider. Mainly wondering if you have any suggestions, course of action to be able to improve the Prismic editor/workflow performance for our editorial team.