Published records should be immediately verifiable #13

The recommended workflow in the Quickstart has publishing to PDS come before verification by deploying the static site.

But if an AppView is watching the firehose, it might try to validate the publication/document as soon as the record comes in. If the site hasn't been deployed, it's liable to throw out the record. This is how longform.fyi currently works, although I might have to change it.

It's probably best to suggest publishing to PDS after deploying the static site.

Hey @jackv.phd! Thanks for bringing this up. Unfortunately it's a bit of a chicken - egg problem:

In order to publish the site we need the at:// URIs for each post to be included in the <link> tags for verification
In order to get the at::// URIs we need to publish to the PDS

This is why the suggested sequoia flow is to publish to the PDS first, and when that happens sequoia injects the markdown files with each post's at:// URI, which can then be used to inject into the head link tags.

I solved the indexing problem by implementing a flow that checks if an article is verified, and if it fails the flow will mark in the DB that the article is invalid and when it was checked. Then I do a re-check after a period of time to see if it's valid. I also have the benefit of using Tap that posts to a webhook endpoint on the server which puts the post into a queue. That queue takes at least a few minutes to start and finish, so if someone did a publish to PDS -> publish site in a script workflow, the document is verified by the time the queue gets to it. You can see this in action at the docs.surf repo if you'd like!