Patrick Näf

The following notes, which I wrote down elsewhere, need to be reviewed - they may or may not be useful anymore. ``` Allow multiple board setups, one for each variation...

### Markup systems Wikipedia has an article with a list and comparison of [Lightweight Markup Languages](https://en.wikipedia.org/wiki/Lightweight_markup_language). LMLs not to be considered are those tied to a specific application, such as...

### Website hosting There are roughly these 3 options: - Hosting on dedicated server - Hosting on GitHub via GitHub Pages - Hosting on Read the Docs. Requires Sphinx and,...

### Generators - [Sphinx](https://www.sphinx-doc.org/). Requires reST. - [MkDocs](https://www.mkdocs.org/). Requires Markdown. - [Pandoc](https://pandoc.org/). Seems super-flexible, can process reST, AsciiDoc and also all sorts of Markdown flavours. - [Hugo](https://gohugo.io/): A generic website...

Final solution: - Markup system: Markdown (GitHub Flavored Markdown), optionally AsciiDoc - Generator: Hugo - Website Hosting: GitHub Pages (https://littlego-usermanual.herzbube.ch/)

`NodeTreeViewModel` already has a boolean property `displayNodeNumbers`. Implementing this feature would therefore likely consist of - Exposing the property as a user preference. - Making sure that the node tree...

The major problem with implementing this feature is that Fuego only supports stone setup on an empty board. For instance, the GTP command `gogui-setup B A1` on a non-empty board...

Brain dump of some notes that I took for implementing this: - Currently `GoGame` is the model class that stores board setup information. Because there is only one `GoGame` object...