Topic on Talk:Page Content Service/Flow

Under "Page previews content/Text", the page for the Popups extension says:

For third parties we encourage using the Page Content Service to enjoy using Popups with your local wiki. You can also use the Extension:TextExtracts extension. This extension has various caveats and we do not actively support use of this API.

I came across this when I deployed the Popups extension to Icannwiki earlier tonight and saw that, while some popups worked, most I tried did not. To see this, compare "ASCII" (working) and "DNS" (fails) under Internationalized Domain Name. I did some digging, and, not finding any obvious errors on the server, I went to look at the documentation. That's when I found the above quote and then the (seemingly) contradictory statements from @Jdforrester (WMF) below.

If we are really meant to not use the TextExtracts extension, it would help to outline how to set up PCS. Alternatively, maybe there is a list of tasks in phabricator that we can attack.

I agree that people shouldn't try to use the Popups extension, for various reasons, of which setting up your own PCS endpoint is probably the largest. You could file a task with the Web team asking for them to make the backing infrastructure requirements more generalisable, but I don't think there's any existing task about this.

The DNS page appears to be misusing a Table as a presentation-styling method. That's probably confusing the software, and I'd suggest trying to import a simple template that does the job properly, with divs, instead. E.g. wikt:Template:tocright looks like it might be fine to use.