FrAC repository at GitHub / suggested migration from HTML to Markdown

Dear all,

hope this finds you safe and sound. Two issues regarding  the emerging   
OntoLex module on frequency, attestations and corpus information.

(1) GitHub repository

I moved the GitHub repository that we use to develop the FrAC module to  
the OntoLex organization on GitHub. It can now be found under

https://github.com/ontolex/frequency-attestation-corpus-information

The old repository (https://github.com/acoli-repo/ontolex-frac) remains  
accessible but now contains a pointer to the new repo and will no longer  
be updated.

(2) Migration to from HTML to Markdown

So far, the FrAC draft has been developed as a native HTML document, using  
the template of the lexicog module, but to facilitate collaborative  
editing, I created an experimental Markdown version:

https://github.com/ontolex/frequency-attestation-corpus-information/blob/master/index.md

Note that this can be directly edited online, and that this includes a  
preview option:

https://github.com/ontolex/frequency-attestation-corpus-information/edit/master/index.md

Guidelines for writing Markdown can be found under  
https://guides.github.com/features/mastering-markdown/, and a convenient  
online editor is available, for example, with https://stackedit.io/.

The original HTML contains somewhat more information (and ultimately has a  
nicer layout), but seems to be less convenient for online editing:

https://github.com/ontolex/frequency-attestation-corpus-information/blob/master/index.html
(see https://acoli-repo.github.io/ontolex-frac/ for how it looks like when  
published, some stylesheets still not working ...)

I suggest the OntoLex community to review both versions within the next 5  
calendar days, and unless there are preferences to continue working with  
HTML, I suggest to edit only the Markdown version and to deprecate the  
HTML version. As the Markdown does not contain all layout and metadata  
information stored in HTML <div> attributes (it does contain all the  
text), we will turn back to HTML again, but only as part of the  
publication process, after the content is stable and agreed upon.

Please let me know what you think.

Thanks a lot,
Christian