Make sure every chapter starts with a (short) introduction before the first subtitle

This commit is contained in:
Charlotte Van Petegem 2024-01-31 16:53:19 +01:00
parent 1d6fbb1490
commit 30372c087c
No known key found for this signature in database
GPG key ID: 019E764B7184435A

View file

@ -2,7 +2,7 @@
#+AUTHOR: Charlotte Van Petegem
#+LANGUAGE: en-gb
#+LATEX_CLASS: book
#+LATEX_CLASS_OPTIONS: [paper=240mm:170mm,parskip,DIV=10,BCOR=10mm]
#+LATEX_CLASS_OPTIONS: [paper=240mm:170mm,parskip,BCOR=10mm,10pt]
#+LATEX_COMPILER: lualatex
#+LATEX_HEADER: \usepackage[inline]{enumitem}
#+LATEX_HEADER: \usepackage{shellesc, luacode}
@ -95,13 +95,6 @@ Remaining text should probably be written in the form of an article, so we can t
:CREATED: [2023-11-20 Mon 17:20]
:END:
*** TODO Make sure every chapter starts with a (short) introduction of that chapter
:PROPERTIES:
:CREATED: [2023-11-20 Mon 17:26]
:END:
Make sure to mention that the content is based on certain articles (if applicable).
** Medium priority
:PROPERTIES:
:CREATED: [2023-11-20 Mon 17:17]
@ -182,6 +175,9 @@ Increasing interactivity in learning has long been considered important, and fur
:CUSTOM_ID: chap:what
:END:
In this chapter, we will give an overview of Dodona's most important features.
The chapter is partially based on\nbsp{}[cite/t:@vanpetegemDodonaLearnCode2023].
** Classroom management
:PROPERTIES:
:CREATED: [2023-10-24 Tue 09:31]
@ -406,6 +402,11 @@ The evaluation tracks which submissions have been manually assessed, so that ana
:CUSTOM_ID: chap:use
:END:
This chapter will discuss the use of Dodona.
We start by mentioning some facts and figures, and discussing a user study we performed.
We then explain how Dodona can be used on the basis of a case study.
The chapter is partially based on\nbsp{}[cite/t:@vanpetegemDodonaLearnCode2023].
** Facts and figures
:PROPERTIES:
:CREATED: [2024-01-22 Mon 18:15]
@ -739,7 +740,7 @@ Dodona and its ecosystem comprise a lot of code.
This chapter discusses the technical background of Dodona itself\nbsp{}[cite:@vanpetegemDodonaLearnCode2023] and a stand-alone online code editor, Papyros (\url{https://papyros.dodona.be}), that was integrated into Dodona\nbsp{}[cite:@deridderPapyrosSchrijvenUitvoeren2022].
I will also discuss two judges that I was involved with the development of.
The R judge was written entirely by myself\nbsp{}[cite:@nustRockerversePackagesApplications2020].
The TESTed judge came forth out of a prototype I built in my master's thesis\nbsp{}[cite:@vanpetegemComputationeleBenaderingenVoor2018] and was further developed in two master's theses I supervised\nbsp{}[cite:@selsTESTedProgrammeertaalonafhankelijkTesten2021; @strijbolTESTedOneJudge2020].
The TESTed judge came forth out of a prototype I built in my master's thesis\nbsp{}[cite:@vanpetegemComputationeleBenaderingenVoor2018] and was further developed in two master's theses I helped supervise\nbsp{}[cite:@selsTESTedProgrammeertaalonafhankelijkTesten2021; @strijbolTESTedOneJudge2020].
** Dodona[fn:: https://github.com/dodona-edu/dodona]
:PROPERTIES:
@ -1478,6 +1479,8 @@ The DSL version of the example exercise can be seen in Listing\nbsp{}[[lst:techn
:CUSTOM_ID: chap:passfail
:END:
This chapter is based on\nbsp{}[cite/t:@vanpetegemPassFailPrediction2022], and also briefly discusses the work performed in\nbsp{}[cite/t:@zhidkikhReproducingPredictiveLearning2024].
** Introduction
:PROPERTIES:
:CREATED: [2023-10-23 Mon 08:50]