Skip to content

Commit bfbe0b2

Browse files
authored
Merge pull request #329 from mmesiti/fix-intro-spring2026
Minimal fix of intro for 2026
2 parents 988cb9c + 3ecda63 commit bfbe0b2

2 files changed

Lines changed: 20 additions & 10 deletions

File tree

CITATION.cff

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ authors:
2626
given-names: "Kjartan Thor"
2727
- family-names: "Wittke"
2828
given-names: "Samantha"
29+
- family-names: "Mesiti"
30+
given-names: "Michele"
2931
title: "How to document your research software"
3032
type: "dataset"
3133
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."

content/index.md

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,22 @@
33
In this lesson we will discuss different solutions for implementing and
44
deploying code documentation.
55

6-
We will start with a discussion about **what makes a good README**. For many
7-
projects, a README is more than enough.
6+
This demonstration will be mostly **independent of programming languages**
7+
(you will be able to follow and do all the exercises
8+
using the [CodeRefinery conda environment](https://coderefinery.github.io/installation/conda-environment/)).
89

9-
We will then learn how to build documentation with the
10-
**documentation generator** [Sphinx](https://www.sphinx-doc.org) (and compare it
11-
with others) and how to
12-
deploy it to [Read the Docs](https://readthedocs.org), a service which hosts
13-
open documentation for free.
1410

15-
This demonstration will be **independent of programming languages**.
11+
We will discuss best practices, and briefly discuss the available tools.
12+
13+
Then we will discuss the form of documentation which is the most immediate to write:
14+
**in-code** comments, and docstrings.
15+
16+
We will step up our game and discuss **what makes a good README**. For many
17+
projects, a curated README is enough.
1618

17-
We will also learn how
18-
to deploy a **project website or personal homepage** to [GitHub Pages](https://pages.github.com).
19+
We will then learn how to build documentation with the
20+
**documentation generator** [Sphinx](https://www.sphinx-doc.org) and how to
21+
deploy it to [GitHub Pages](https://pages.github.com).
1922
The approach that we will learn will be transferable to
2023
[GitLab Pages](https://about.gitlab.com/features/pages/) and
2124
[Bitbucket Pages](https://pages.bitbucket.io).
@@ -33,6 +36,11 @@ If you wish to follow in the terminal and are new to the command line, we
3336
recorded a [short shell crash course](https://youtu.be/xbTTDLA3txI).
3437
```
3538

39+
An optional episode is about
40+
deploying a **project website or personal homepage**
41+
to [GitHub Pages](https://pages.github.com).
42+
43+
3644
```{csv-table}
3745
:widths: auto
3846
:delim: ;

0 commit comments

Comments
 (0)