Problem
Currently, syncing English/Spanish content and YouTube IDs with code is a manual process in .mdx files. This causes issues with consistency, manual labor, and potential errors.
Proposal
Alfonso suggested introducing a centralized index.csv file to control all content synchronization. However, the solution needs to be flexible and provide a better developer experience (DX).
Requested Action
- Research alternative and improved ways to centrally manage and synchronize multilingual content (ENG/SPA), YouTube video IDs, and code references.
- Evaluate pros and cons of using a CSV or other formats (e.g., JSON, YAML, database, CMS, etc.).
- Suggest DX improvements for content authors and developers.
- Consider automation or tooling that could streamline the process.
Goal
Arrive at a solution that makes content synchronization flexible, maintainable, and developer-friendly.
Problem
Currently, syncing English/Spanish content and YouTube IDs with code is a manual process in
.mdxfiles. This causes issues with consistency, manual labor, and potential errors.Proposal
Alfonso suggested introducing a centralized
index.csvfile to control all content synchronization. However, the solution needs to be flexible and provide a better developer experience (DX).Requested Action
Goal
Arrive at a solution that makes content synchronization flexible, maintainable, and developer-friendly.