reorder flow

.github/workflows/main.yml

@@ -23,13 +23,13 @@ jobs:
 
     - name: Run @aviarytech/tev2-ingress
       run: bun tev2-ingress -c config.yaml
+
+    - name: Run @tno-terminology-design/mrg-import
+      run: bun mrg-import -s .
 
     - name: Run @tno-terminology-design/mrgt
       run: bun mrgt -s .
 
-    - name: Run @tno-terminology-design/mrg-import
-      run: bun mrg-import -s .
-
     - name: Run @aviarytech/tev2-hrgt
       run: bun tev2-hrgt glossaries/mrg* 
 

term-template.md

@@ -0,0 +1,13 @@
+# Title
+
+>_The title of this page ^^^ should be the word or phrase you want to define. It should NOT generally be capitalized; see [term-conventions.md](https://github.com/trustoverip/concepts-and-terminology-wg/blob/master/docs/term-conventions.md) for conventions and theory on capitalization, punctuation, plurals, spelling, and so forth. If your term has a short form or acronym, put the long form first, and then the short form in parentheses._
+
+## Definition
+>_What does this word or phrase mean, precisely? The first sentence of your definition acts as hovertext in hyperlinks, so make it as as pithy as possible. After that, add as much detail as you need: what criteria allow you to know for certain whether X is or is not an example of the concept? What misunderstandings need to be eliminated? If your term is a true synonym for something already defined in the glossary, just hyperlink to that definition rather than rewriting or copying it._
+
+## Usage Examples
+>_Optional but encouraged. Provide one or more short excerpts (or links) that show how the term has been used within the specific community of interest. These could come from a spec, github issues, whitepapers, etc._
+
+## Tags
+>_Add any additional hash tags that you feel would allow grouping in useful ways. See [hash-tags.md](https://github.com/trustoverip/concepts-and-terminology-wg/blob/master/docs/hash-tags.md) for details._
+