A CLI for publishing standard.site documents to ATProto
sequoia.pub
stevedylan.dev
standard
site
lexicon
cli
publishing
chore: docs updates
+4
docs/docs/pages/publishing.mdx
+4
docs/docs/pages/publishing.mdx
···
27
27
```
28
28
29
29
Sync will use your ATProto handle to look through all of the `standard.site.document` records on your PDS, and pull down the records that are for the publication in the config.
30
+
31
+
## Troubleshooting
32
+
33
+
- If you have files in your markdown directory that should be ignored, use the [`ignore` array in the config](/config#ignoring-files).
+17
docs/docs/pages/verifying.mdx
+17
docs/docs/pages/verifying.mdx
···
15
15
Every document or blog post that is published needs a `<link>` tag in the `<head>` of your blog post HTML page. The content of that link tag needs to be the AT URI for the record we just published on your PDS. There are two ways you can handle these:
16
16
- `sequoia inject` (recommended) - By running this command after publishing, and after building the site with your SSG, Sequoia will inject the link tags into your finished HTML. This way you don't have to manually edit it or mess with an SSG config to set it up. Just deploy the build folder after you have run `sequoia inject`!
17
17
- Manual - After you have run `sequoia publish` the CLI will add in a new `atUri` field to every post's frontmatter. This way you can configure your SSG to read that frontmatter and include it in the build step, similar to how it might include an opengraph image in the meta tags. This approach gives you full control over the HTML files but will take a bit more skill.
18
+
19
+
## Testing Verification
20
+
21
+
After your publication and your document records have been published and you site has been deployed, you can test the verification of your records a few ways.
22
+
23
+
### pds.ls
24
+
25
+
Visit [pds.ls](https://pds.ls) and in the search bar paste in a `arUri` for either your publication or document, click the info tab, and then click the "info" tab. This will have a schema verification that will make sure the fields are accurate, however this will not cover Standard.site verification as perscribed on their website.
26
+
27
+
### Standard.site Validator
28
+
29
+
Visit [site-validator.fly.dev](https://site-validator.fly.dev/) and paste in the URL for a blog post that has a record on your PDS. This site will check the schema as well as the requirements for standard.site verification.
30
+
31
+
## Troubleshooting
32
+
33
+
- Make sure that you are either using `sequoia inject` or manually handling the required `<link>` tags for each post. Read [workflows](/workflows) for a clear order of operations to publish, inject, and deploy.
34
+
- Make sure that the `.well-known` publication record is present in your public/static folder, and that it's populating to your build folder (e.g. `dist`). There are some SSGs that will not automatically include dot files or directories.