Remove YAML front matter from editable content in the Static Site Editor
Problem to solve
Front matter is included at the beginning of a markdown file to provide the static site generator the necessary metadata to format, configure, or parse the page. This content, however, isn't frequently edited after initial creation and becomes a bit of a liability when presented alongside the rest of the page content. If a user unfamiliar with the very specific formatting and available options for any given front matter value attempts to edit it (or accidentally edits it) the entire page could fail to render.
Users of the Static Site Editor should feel confident that the changes they make to the page will not break formatting.
User experience goal
The user should not see any YAML front matter when editing a page in the WYSIWYG mode of the Static Site Editor. Users can still make critical front matter edits in the Markdown editing mode.
We should hide or otherwise ignore the front matter in the file when displaying content in the WYSIWYG mode of the editor. The content should not actually be removed from the file, since we want that data to remain after the user submits changes and we still want it to appear in the Markdown editing mode.
In another issue, we'll use the front matter data to present the properties as form fields. So it's important that we are actually parsing the data, not just throwing it out.
Availability & Testing
What does success look like, and how can we measure that?
- A user does not see any front matter in the WYSIWYG or raw Markdown areas of the Static Site Editor