git.stevedylan.dev

chore: update docs 3273049b

Steve · 2026-03-22 14:21 2 file(s) · +23 −3

docs/docs/pages/config.mdx +1 −0

    "publishDate": "date"
  },
  "ignore": ["_index.md"],
  "autoSync": true,
  "bluesky": {
    "enabled": true,
    "maxAgeDays": 30

docs/docs/pages/publishing.mdx +22 −3


## Updates

As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping track of the AT URIs for each post and generating content hashes for the content inside each markdown file. When you update a post and run the publish command, Sequoia will generate hashes again, see the difference, and update the existing post rather than creating a new one. 
As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping track of the AT URIs for each post and generating content hashes for the content inside each markdown file. When you update a post and run the publish command, Sequoia will generate hashes again, see the difference, and update the existing post rather than creating a new one.

### Auto-Sync

By default, Sequoia will automatically sync state from your PDS before publishing when the state file is missing or empty. This prevents duplicate posts when publishing from a fresh clone or CI environment. Auto-sync will:

- Fetch existing documents from your PDS for the configured publication
- Match them to local files by their URL path
- Update the local `.sequoia-state.json` with matched records
- Add `atUri` to the frontmatter of matched posts if not already present

To disable auto-sync, set `autoSync` to `false` in your config:

```json
{
  "autoSync": false
}
```

If you happen to loose the state file or if you want to pull down records you already have published, you can use the `sync` command. 
### Manual Sync

If you want to manually pull down records you already have published, you can use the `sync` command.

```bash [Terminal]
sequoia sync
```

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.
Sync will use your ATProto handle to look through all of the `site.standard.document` records on your PDS, and pull down the records that are for the publication in the config. Use the `--update-frontmatter` flag to also update your local markdown files with `atUri` fields.

## Bluesky Posting


23	23		"publishDate": "date"
24	24		},
25	25		"ignore": ["_index.md"],
	26	+	"autoSync": true,
26	27		"bluesky": {
27	28		"enabled": true,
28	29		"maxAgeDays": 30

18	18
19	19		## Updates
20	20
21		-	As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping track of the AT URIs for each post and generating content hashes for the content inside each markdown file. When you update a post and run the publish command, Sequoia will generate hashes again, see the difference, and update the existing post rather than creating a new one.
	21	+	As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping track of the AT URIs for each post and generating content hashes for the content inside each markdown file. When you update a post and run the publish command, Sequoia will generate hashes again, see the difference, and update the existing post rather than creating a new one.
	22	+
	23	+	### Auto-Sync
	24	+
	25	+	By default, Sequoia will automatically sync state from your PDS before publishing when the state file is missing or empty. This prevents duplicate posts when publishing from a fresh clone or CI environment. Auto-sync will:
	26	+
	27	+	- Fetch existing documents from your PDS for the configured publication
	28	+	- Match them to local files by their URL path
	29	+	- Update the local `.sequoia-state.json` with matched records
	30	+	- Add `atUri` to the frontmatter of matched posts if not already present
	31	+
	32	+	To disable auto-sync, set `autoSync` to `false` in your config:
	33	+
	34	+	```json
	35	+	{
	36	+	"autoSync": false
	37	+	}
	38	+	```
22	39
23		-	If you happen to loose the state file or if you want to pull down records you already have published, you can use the `sync` command.
	40	+	### Manual Sync
	41	+
	42	+	If you want to manually pull down records you already have published, you can use the `sync` command.
24	43
25	44		```bash [Terminal]
26	45		sequoia sync
27	46		```
28	47
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.
	48	+	Sync will use your ATProto handle to look through all of the `site.standard.document` records on your PDS, and pull down the records that are for the publication in the config. Use the `--update-frontmatter` flag to also update your local markdown files with `atUri` fields.
30	49
31	50		## Bluesky Posting
32	51