Automating Content Generation: A Technical Deep Dive into JSON and Metadata Updates

TL;DR: I automated content generation for July 9th, updating JSON files and metadata, and fixed a minor bug in the changelog. This involved modifying multiple files, including bluesky_en.json, metadata.json, and changelog.md.

The Problem

While working on automating content generation, I encountered an issue with inconsistent metadata across different platforms. Specifically, the bluesky_en.json and bluesky_es.json files were not being updated correctly, leading to discrepancies in the published content. The error message I encountered was related to a missing newline character at the end of the file.

What I Tried First

Initially, I attempted to update the content-automation/changelog.md file to reflect the changes made on July 9th. However, I realized that I needed to modify the bluesky_en.json and bluesky_es.json files to include the new content. I also updated the metadata.json file to ensure consistency across platforms.

The Implementation

To resolve the issue, I made the following changes:

Updating bluesky_en.json and bluesky_es.json

// bluesky_en.json
[
  {
    "type": "progress",
    "text": "Just automated some content generation for July 9th. Fixed a minor bug in `content-automation/changelog.md`"
  }
]

// bluesky_es.json
[
  {
    "type": "avance",
    "text": "Finalmente actualicé los metadatos de los artículos en varios idiomas, resolviendo un pequeño conflicto en los archivos JSON"
  }
]

Updating metadata.json

{
  "pull_requests": 0,
  "releases": 0,
  "closed_issues": 0,
  "generated_content": true
}

Updating changelog.md

## [2026-07-09] content-automation

### Changed
- Auto-generación de contenido para el 2026-07-09 en varios formatos:
  * Se actualizó `content/2026/07/09/VS/changelog.md` con información adicional

Key Takeaway

The key takeaway from this experience is the importance of consistency in metadata across different platforms. By automating content generation and updating JSON files and metadata, I was able to ensure that the published content was accurate and consistent.

What's Next

In the next iteration, I plan to focus on automating the generation of content for multiple languages and platforms. This will involve exploring new tools and technologies to streamline the process and ensure that the content is accurate and consistent across all platforms.

vibecoding #buildinpublic #contentautomation #json #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-10

#playadev #buildinpublic