stevedylan.dev stevedylan.dev My first run of sequoia i got the paths and slugs config wrong and ended up publishing 20 bad records like doofus.
I then had to dig around on third party validators and at:// link viewers to figure out what was wrong.
If I could see the records before publishing them, either in the command output, or on disk where i could run a validator on them before posting, I'd have felt less like a doofus and a bit more in control of the process.
One idea might be to refactor record creation such that --dry-run could just write the record content to the console. Maybe like a --dry-run --raw or treat -n like a countable verbose e.g., -nn instead of -vv. Not sure if the current arg parser supports that, but just another idea in lieu of --raw or something like that.
I imagine some people probably wouldn't want to see such raw content. Problem with files is where to put them, whether they get .gitignore'd, etc.
@oli.zilla.org.uk actually, have you tried sequoia publish -n -v? I added the post URL a while back when I made some changes to pathTemplate. Does that give you what you need e.g.,
│
● Site: https://heaths.dev
│
● Content directory: ./_posts/
◇ Found 34 posts
●
│ 5 posts to publish:
│
│
│ ~ Introducing the sequoia-recommend button (content changed) [bsky: exists]
│ https://heaths.dev/atproto/2026/05/31/introducing-the-sequoia-recommend-button.html
│
│ ~ Initial stable release of Azure SDK for Rust (content changed) [bsky: exists]
│ https://heaths.dev/azure/2026/05/16/initial-stable-release-of-azure-sdk-for-rust.html
│
│ ~ Cooler theme palette (content changed) [bsky: exists]
│ https://heaths.dev/general/2026/05/03/cooler-theme-palette.html
│
│ ~ Improving the Azure SDK developer experience with MCP (content changed) [bsky: exists]
│ https://heaths.dev/azure/2026/05/01/improving-the-azure-sdk-developer-experience-with-mcp.html
│
│ ~ Light and dark themes for my blog (content changed) [bsky: exists]
│ https://heaths.dev/general/2026/04/20/light-and-dark-themes-for-my-blog.html
│
●
│ Bluesky posting: enabled (max age: 7 days)
│
●
│ Dry run complete. No changes made.
I would have felt more in control if there was a way to see exactly what records the tool would publish. It'd be ok to write some files to the pwd if the user has added a flag to ask for them.
This is a great idea! We already have a
--dry-runflag so adding output/writing to disk makes a lot of sense. Will look into it!