Adding example OFM file for new editors

[dnotes]

Working to fix #7 by adding all sections to spec.md, without examples (tests) but with some explanation for each section.

[dnotes]

Shoot. Chose the wrong branch. Rrr.

[chadananda]

We need a /docs branch with a single-page side-by-side editor with some example MD on the left and styled HTML on the right side. We'll need an 'ocn.css' file for this. Also, this could be a place wherein we document Ocean conventions. Or, perhaps all this should be reserved for the Library collections editor. I'm finding Netlify a nightmare to actually use. All the CMS tools seem to be highly opinionated about how one should actually render the MD. I just want a lightweight, configurable editor for managing Git MD collections without having to integrate it into the website (assuming there even is a website).

…

On Sat, Jun 1, 2019 at 8:52 AM David Hunt ***@***.***> wrote: Shoot. Chose the wrong branch. Rrr. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8?email_source=notifications&email_token=AAHJ5Q3ZY2RS3IRMXVG5IYTPYJ5J3A5CNFSM4HSARP62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXBCLA#issuecomment-497946924>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHJ5Q7KQV32T7QSK2B3ZZDPYJ5J3ANCNFSM4HSARP6Q> .

[dnotes]

I thought we could have a basic Markdown file (the one in this PR, for starters) that would be pulled into a side-by-side editor somehow. No idea yet on the "somehow"—any ideas?

[dnotes]

I guess maybe we could use vuepress for the documentation and make a custom component for the example page? Maybe the component could even be an existing side-by-side editor like Toast UI Editor, modified for OFM, that we could then use as a widget in something like Netlify CMS?