Add licensing module ordering

modules/licenses/02.copyright.md

@@ -1,6 +1,12 @@
+---
+title: Copyright
+type: reading
+order: 2
+---
+
 ## Copyright and software
 
-Creative works, like books, paintings and music, but also scientific articles and software, are covered by copyright. Copyright is a legal construct that gives the owner of the copyright on a work the exclusive right to reproduce, modify, publicly perform and distribute the work. As a result, anyone who is not the copyright holder needs to have permission from the copyright holder to also be able to do so. 
+Creative works, like books, paintings and music, but also scientific articles and software, are covered by copyright. Copyright is a legal construct that gives the owner of the copyright on a work the exclusive right to reproduce, modify, publicly perform and distribute the work. As a result, anyone who is not the copyright holder needs to have permission from the copyright holder to also be able to do so.
 
 Newly created works are automatically covered by copyright. This copyright is owned by the creator of the work, unless they were employed and created the work as part of their employment, in which case their employer owns the work. If multiple persons or organisations contribute to a work, then they each own a share of the copyright, and all need to give permission for others to be able to do any of the things protected by copyright. This permission is called a *license*.
 

modules/licenses/03.university_policy.md

@@ -1,3 +1,9 @@
+---
+title: Software policies
+type: reading
+order: 3
+---
+
 ## University software policies
 
 Universities employ researchers, who often create and use software in the course of doing research. That means that they create and use copyrighted works, activities governed by copyright law. Works created by employees as part of their work are normally owned by their employer. This is the default legally in many places, and is almost always stated in the employment contract as well. So, the university owns the software created by its employees, and because the employees also act on behalf of their employer, is responsible for any violations of copyright by their employees.

modules/licenses/04.ex_have_licensing_policy.md

@@ -1,3 +1,9 @@
-## Exercise 2: Does your university have a software licensing policy?
+---
+title: Your policy
+type: exercise
+order: 4
+---
+
+## Exercise 1: Does your university have a software licensing policy?
 Try and find out whether your university has a software (licensing) policy. If you can find it, compare it with the ones from [TU Delft](https://zenodo.org/record/4629662), [ASTRON](https://zenodo.org/records/7307162) and [the Netherlands eScience Center](https://www.esciencecenter.nl/wp-content/uploads/2020/05/nlesc_ip_policy_2017.pdf). What elements are commonly found? Which differences do you see, and what is their respective motivation?
 

modules/licenses/05.ex_licenses_in_use.md

@@ -1,3 +1,9 @@
-## Exercise 3: What licenses do researchers at your university use?
+---
+title: Licenses in use
+type: exercise
+order: 5
+---
+
+## Exercise 2: What licenses do researchers at your university use?
 Search on [GitHub](https://github.com/) or other software repositories for software created by researchers at your university. What licenses do they use? Do they adhere to a policy (if there is one?)
 

modules/licenses/06.licenses.md

@@ -1,3 +1,10 @@
+---
+title: FOSS Licenses
+type: reading
+order: 6
+---
+
+
 ## Software licenses
 
 Software licenses are legal statements that give permission to use, modify and/or distribute software. By copyright law, only the copyright owner(s) can give this permission, so the license must be granted by those owners.

modules/licenses/07.ex_choose_a_license.md

@@ -1,4 +1,10 @@
-## Exercise 1: Choose a license for or using your policy (10 minutes)
+---
+title: Choose a license
+type: exercise
+order: 7
+---
+
+## Exercise 3: Choose a license for or using your policy (10 minutes)
 
 One of the concerns typically addressed in a software policy is licensing of software developed at the institution. Policies can choose a single license, or offer a range of options.