Static page markdown transfer

[jameslzhu]

Pull request #15 added markdown pages: static pages (with no dynamic js content), which can be created and edited by regular users in Markdown. (You may be more familiar with Github Flavored Markdown). If you've ever written a comment on Reddit, Stack Overflow, or Github, chances are you've unwittingly been using Markdown.

Many of the pages on the old site are either hard-coded in HTML or uploaded under our static page feature in HTML. This project will entail converting these pages to simplified Markdown text, so we can re-upload these in the new website.

You can do this either manually or automatically with cleanup; a quick search on doing this task with pandoc suggested this stack overflow link with the following snippet:

pandoc -f html -t commonmark myfile.html >myfile.md

As for the exact pages to convert, you'll have to hunt them down on the current website (hkn.eecs.berkeley.edu). I've found a few examples below:

• Service
• Junior EECS Day
• Indrel

Of note, if you'd like to rewrite these pages, you should definitely check first with the corresponding committee - simpler is better, but not if it omits important information. Also, in some cases these committees may want the extra formatting HTML can offer.

We'll give you compserv permissions on the site for you to access the copy-paste HTML, without the header / footer cruft.

If you take on this task, you should ask us to add you to the org so you can access the old hkn-rails site and the html files.

Of note, these will eventually need to be stored as text fields in the database. (This functionality is already implemented in the markdown-pages app.) But since we don't have a stable database / backups, we won't be uploading these to the SQL database in the OCF apphost, but instead saving these text files in the Github somewhere for the time being. (Preferably somewhere sensible like hknweb/static/md, but idk.)

[bri25yu]

Combining with #432