git.stevedylan.dev

minor fix: typo caaefffb

Teon L Brooks · 2026-03-14 13:29 1 file(s) · +1 −1

docs/docs/pages/publishing.mdx +1 −1


## Updates

As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping tack 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. 

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. 


18	18
19	19		## Updates
20	20
21		-	As you publish content Sequoia will store a record of content in `.sequoia-state.json`, keeping tack 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	22
23	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.
24	24