all files

Author: Sunneva

readme_template.md

@@ -0,0 +1,51 @@
+# Template README.md
+```
+# Title 
+Project description as a paragraph or so explaining what this project does and perhaps why.
+
+# Table of Contents
+[Easy to use TOC generator](https://ecotrust-canada.github.io/markdown-toc/)
+
+# Installation
+
+* software requirements
+* dependencies
+
+It is also helpful to provide commands which assist user installing the program or even providing an `install.sh` script which does it for the user.
+
+# Running
+How to run the program/application/model and common use-cases and outputs.
+For the program to be easily usable this section can be quite long.
+Make sure to include explenations for all coding examples since it makes them much more understandable. 
+
+## API reference (Optional)
+If lengthy, this should be a separate document placed as HTML into the `docs/` folder. For more inforation see `documentation`
+
+# License
+Mention which LICENSE the code uses and refer to the LICENSE file. For more information about licensing later.
+
+# Authors/Credit
+Reykjavik University
+
+Main authors <email.addresses>
+
+## Acknowledgements
+If the funding is from a public grant, mention the source of the funding and link to their website.
+
+"This project was funded by the Language Technology Programme for Icelandic 2019-2023. The programme, which is managed and coordinated by [Almannarómur](https://almannaromur.is/), is funded by the Icelandic Ministry of Education, Science and Culture."
+
+# Contributing (Optional)
+Explain how people can contribute to this repository. This can also link to a separate Developer reference (Contributing.md)
+
+* how to contribute
+* creating issues
+* where to get data
+* testing
+
+## Description of folder structure (Optional)
+
+# Changelog/Versions (Optional)
+# Papers/References (Optional)
+
+You would have a citation snippet here as a code block. For papers not yet accepted it is fine to mention you have submitted a paper to a particular conference and mention how you will reference it once has been accepted. For example you could add a citation or include the paper in the docs folder. 
+```

workflow_example.md

@@ -0,0 +1,61 @@
+# Example of a workflow:
+```
+name: LVL_CI_example
+
+# on controls when this specific action will run.
+on:
+  # The event/s you want to trigger this action
+  [push, pull_request]:
+    # Which branch/es the action will run on
+    branches: [ master ]
+
+#job defines a sequence of tasks that will run when this workflow is triggered. 
+job: 
+  # A unique id for a job containing only _ or letters, this one is called build
+  build:
+    # Specifies which kind of machine the job is run on. 
+    # It's up to you which machine to use but github hosted runners are highly encouraged.
+    runs-on: ubuntu-latest
+    
+    #steps defines a tasks to run as part of the job, the following steps 
+    steps: 
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+      
+      #--build project--
+      
+      ## Below are some examples of how to run code
+      
+      - name: example 1
+      run: echo run can run scripts
+      
+      - name: example 2
+      run: |
+      echo it can also run
+      echo multi-line scripts
+      
+      # this example uses a code from another file
+      - name: example 3
+        uses: ./.github/actions/my-action
+      
+      
+      
+  test: 
+     runs-on: ubuntu-latest
+     
+     steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+      
+      #--run your tests--
+      
+  package:
+    runs-on: ubuntu-latest
+     
+     steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v2
+      
+      #--run your packaging steps--
+  
+```