Board Thread:Code Review/@comment-24757753-20180805110740/@comment-24757753-20180809120215

Ideally, comments wouldn't be in the pages at all, but it's needed as all i18n-js pages currently start with.

An alternative could be to add a single space to the start of the first+last lines (so first line is ) - this space will put the content in a   element - then include a   as early as possible (perhaps in the   key i18nEdit uses). This'd give us page content that's 100% valid JSON while still preventing wanted links, etc. from being an issue.

Example: {   "_metadata": { " ": 0   },    "en": { "key1": "value1" } }

A reserved comment key like you mention would be useful for VSTF Wiki's JSON, where comments are used throughout page.