The current content date fields use the English words for months in the dates. This can lead to some confusion among Crowdin translators. If this date field is set to an empty string, it will result in the content api failing to deploy.
Proposed Solution
update all existing documents to use numeric a numeric based date format (like the ISO 8601 standard)
Problem
The current content
datefields use the English words for months in the dates. This can lead to some confusion among Crowdin translators. If thisdatefield is set to an empty string, it will result in the content api failing to deploy.Proposed Solution
Related: https://github.com/solana-foundation/developer-content/issues/225