Auto-Generating Content with Bluesky and Metadata Updates
TL;DR: I updated the content-automation repository to auto-generate posts for Bluesky and refresh metadata. This involved modifying JSON files, updating changelog entries, and adjusting automation scripts.
The Problem
The content-automation repository required auto-generation of posts for Bluesky and updates to metadata. The initial issue was that the Bluesky posts were not being generated correctly, and the metadata was not being updated.
What I Tried First
I first attempted to update the changelog.md file manually, but this proved to be error-prone and time-consuming. I then decided to automate the process using scripts.
The Implementation
To implement the auto-generation of Bluesky posts, I updated the bluesky_en.json and bluesky_es.json files. Here are the changes:
// content/2026/07/15/content-automation/bluesky_en.json
[
{
"type": "progress",
"text": "Finally wrapped up the auto-generation for today's content. Fixed the bug in `craft.service.ts` that was causing issues."
}
]
// content/2026/07/15/content-automation/bluesky_es.json
[
{
"type": "avance",
"text": "Finalmente actualicé los metadatos de automatización de contenido en content-automation. Revisé los cambios en `metadata.json`."
}
]
I also updated the metadata.json file to reflect the changes:
// content/2026/07/15/content-automation/metadata.json
{
"pull_requests": 0,
"releases": 0,
"closed_issues": 1,
"bluesky_published": true,
"bluesky_uris": {
"en": "https://bsky.app/uri",
"es": "https://bsky.app/uri-es"
}
}
The changelog.md file was updated using a script to automate the process:
// content/2026/07/15/content-automation/changelog.md
## 2026-07-15 content-automation
### Changed
- Auto-generated changelog entry for 2026-07-16
- Updated Bluesky posts for 2026-07-16 in `content/2026/07/15/content-automation/bluesky_en.json` and `content/2026/07/15/content-automation/bluesky_es.json`
Key Takeaway
The key takeaway from this experience is the importance of automating repetitive tasks, such as updating changelog entries and generating posts. By using scripts to automate these tasks, I was able to save time and reduce errors.
What's Next
Next, I plan to explore using more advanced automation tools, such as GitHub Actions, to streamline the content-automation process. This will enable me to focus on more complex tasks and improve the overall efficiency of the repository.
vibecoding #buildinpublic #content-automation #bluesky #metadata
Part of my Build in Public series — sharing the real process of building SaaS projects from Playa del Carmen, México.
Repo: zaerohell/content-automation · 2026-07-16
#playadev #buildinpublic
Top comments (0)