Speculative move to Markdown

BeeWare.lektorproject

@@ -70,7 +70,6 @@ url_prefix = /pl_PL/
 locale = pl_PL
 
 [packages]
-lektor-rst = 0.2.0
 lektor-github-repos = 0.1.1
 lektor-gravatar = 0.1.2
 

README.md

@@ -0,0 +1,94 @@
+[![image](http://beeware.org/static/images/brutus-270.png){width="72px"}](https://beeware.org)
+
+# beeware.github.io
+
+This is the homepage for the [BeeWare project](http://beeware.org).
+
+It is a [Lektor](https://getlektor.com)-based site.
+
+If you want to contribute a modification, you can fork this repository
+and submit a pull request. However, **do not fork the master branch** -
+fork the [lektor
+branch](https://github.com/beeware/beeware.github.io/tree/lektor) and
+make changes there instead.
+
+If you want to test out a change before you submit it, create a virtual
+environment, and install [Lektor](https://getlektor.com):
+
+    $ python3 -m venv venv
+    $ source venv/bin/activate
+    (venv) $ python -m pip install lektor
+
+Then from the root directory of the checkout, run:
+
+    (venv) $ lektor server
+
+This will [start a webserver](http://127.0.0.1:5000) that will
+autoreload whenever you make a change to site content.
+
+## Community
+
+You can talk to the community through:
+
+-   [\@pybeeware on Twitter](https://twitter.com/pybeeware)
+-   BeeWare Gitter channel:
+    [beeware/general](https://gitter.im/beeware/general)
+-   [Tickets on the beeware.github.io issue
+    tracker](https://github.com/beeware/beeware.github.io/issues)
+
+## Contributing
+
+If you find problems with this website, [log them on
+GitHub](https://github.com/beeware/beeware.github.io/issues). If you
+want to contribute, please [fork the
+code](https://github.com/beeware/beeware.github.io/tree/lektor) and
+[submit a pull
+request](https://github.com/beeware/beeware.github.io/pulls).
+
+Before submitting a pull request, please make sure your forked branch is
+up to date with the original branch. To do this:
+
+-   set your upstream remote:
+
+        $ git remote add upstream https://github.com/beeware/beeware.github.io.git
+
+-   make sure you have the latest changes from upstream:
+
+        $ git fetch upstream
+
+-   rebase your **lektor** branch to **upstream** before pushing to git
+    and submitting a pull request:
+
+        $ git rebase upstream/lektor
+
+## Translating
+
+Want to make BeeWare more accessible to non-English-speakers? Help
+translate the site! Steps are as follows:
+
+1.  Add language specification to
+    [BeeWare.lektorproject](https://github.com/beeware/beeware.github.io/blob/lektor/BeeWare.lektorproject).
+
+    Fill out the name of the language, its url prefix, and the locale.
+    Make sure you use the correct [ISO
+    639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) locale
+    code - for many countries, it\'s not the same as the national TLD.
+    For example, the ISO 639-1 Danish locale is \'da\', but Denmark uses
+    the \'.dk\' TLD.
+
+2.  Add an entry for your language to the [Atom
+    configuration](https://github.com/beeware/beeware.github.io/blob/lektor/configs/atom.ini).
+
+3.  Add your first translation, by translating the names for the menus
+    at the top of each page. Edit [the menus translation
+    file](https://github.com/beeware/beeware.github.io/blob/lektor/databags/menu.ini),
+    adding a block for your language.
+
+4.  Start adding translations for content pages on the site. Translated
+    files are at the same directory level as the primary English files,
+    but have a language suffix. For example, Arabic\'s locale is \'ar\',
+    so you would add [contents+ar.lr]{.title-ref} wherever the original
+    file name is [contents.lr]{.title-ref}
+
+A great place to start translating is the [contributing
+section](https://beeware.org/contributing/).

flowblocks/text-block.ini

@@ -9,11 +9,11 @@ type = markdown
 
 [fields.text]
 label = Text
-description = reStructuredText
-type = rst
+description = Markdown
+type = markdown
 
 [fields.image]
-label = Image 
+label = Image
 type = select
 source = record.attachments.images
 width = 1/4

models/blog-post.ini

@@ -26,5 +26,5 @@ width = 1/4
 
 [fields.body]
 label = Body
-description = reStructuredText
-type = rst
+description = Markdown
+type = markdown

models/blog.ini

@@ -21,5 +21,5 @@ type = string
 
 [fields.gutter_top]
 label = Gutter top
-description = reStructuredText
-type = rst
+description = Markdown
+type = markdown

models/event.ini

@@ -43,5 +43,5 @@ type = string
 
 [fields.description]
 label = Description
-description = reStructuredText
-type = rst
+description = Markdown
+type = markdown

models/events.ini

@@ -13,8 +13,8 @@ type = string
 
 [fields.gutter]
 label = Gutter
-description = reStructuredText
-type = rst
+description = Markdown
+type = markdown
 
 [children]
 model = event