You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
message: "If you use this lesson material, please cite it using these metadata."
3
+
authors:
4
+
- name: "CodeRefinery"
5
+
- family-names: "Bast"
6
+
given-names: "Radovan"
7
+
- family-names: "Wikfeldt"
8
+
given-names: "Kjartan Thor"
9
+
- family-names: "Rantaharju"
10
+
given-names: "Jarno"
11
+
- family-names: "Darst"
12
+
given-names: "Richard"
13
+
- family-names: "Wittke"
14
+
given-names: "Samantha"
15
+
- family-names: "van der Burg"
16
+
given-names: "Sven"
17
+
- family-names: "Razick"
18
+
given-names: "Sabry"
19
+
- family-names: "Rasel"
20
+
given-names: "Annajiat Alim"
21
+
- family-names: "Negru"
22
+
given-names: "Stefan"
23
+
- family-names: "Lindi"
24
+
given-names: "Bjørn"
25
+
- family-names: "van Vliet"
26
+
given-names: "Marijn"
27
+
- family-names: "Orozco"
28
+
given-names: "Luisa"
29
+
title: "How to document your research software"
30
+
type: "data"
31
+
abstract: "The lesson 'How to document your research software' gives an overview of the different ways how a code project can be documented: from small projects to larger projects. Markdown and Sphinx are central tools in this lesson."
0 commit comments