Help improve tutorials

Help improve tutorials#

We highly appreciate any contributions to the Tutorials!

If you find typos, missing links or anything else wrong, don’t hesitate to fix it.

It is as easy as forking the repository on GitHub , making your changes, and issuing a pull request. If you have any questions about this process don’t hesitate to ask.

Building the tutorials#

The tutorials are created using sphinx, a tool for software documentation. Sphinx converts markup text files into html, pdf or other formats.

All tutorials are written in Markdown, which are simple text files with extra markup to define headers and formating. Having the tutorials as Markdown makes it easy to control changes to the documents and ensure consistent style.

The tutorials are automatically build with sphinx when commits are pushed to the github repository. The process is handle by Github Actions, here. If the build fails, for example because of wrong syntax etc, the Pull Request can not be merged.

Once the pull request is accepted on Github and the changes are merged to the master branch the tutorials becomes availble online.

The newest released version of the tutorials are available at:

The newest development version (current master branch) is availble at:

Building the tutorials locally#

Even though the tutorials are build automatically, it is also possible to build them locally to view the layout and see results before pushing changes to the server. It is often not necesssary when making small fixes to existing tutorials. But when writing major new sections it nice to view how things look.

The easiest way to install needed packages tools, is to have the pixi package manger installed.

Then run the following commands to install the necesssary packages.

c:\path\to\anybody_tutorials> pixi run html

Tip

See the pixi.toml fil for a list of the predefined build commands you can use to build the tutorials.

Once the build is complete it should automatically open the file: _build/html/index.html in a browser to view the result.

Short Markdown guide#

There are plenty of guides on Markdown available on Google. The tutorials uses a flavor of markdown called MySt designed for techincal documentaiton and publishing.

See also

The detailed documenation on Markedly Structured Text (MySt)

So here is just a quick run through over some of the markdown concepts which are important for the tutorials.

Paragraphs#

Any block of text is a paragraph. Paragraphs must be separated by one or more blank lines. Identation matters in markdown, so lines of the same paragraph must be left aligned to the same indentation.

  • one asterisk: *text* for emphasis (italics),

  • two asterisks: **text** for strong emphasis (boldface), and

  • backquotes: \text` ` for code samples.

There are also options for subscript and superscript plus more:

{subscript}`subscript` and {superscript}`superscript`

Headers#

# Chapter header

## Section header

### Subsection header

Lists and Quote-like#

- A bullet list item
- Second item

  - A sub item

1. Numbered list
2. It has two items

Quotes are just paragraph preseed with a > character.

This is an ordinary paragraph, introducing a block quote.

> "Don't panic"
> > -- HG2G

Highlighting code#

Highlighting AnyScript code snippets is also supported, using the pygments_anyscript extension to pygments.

AnyScript highlighting is started using the code-block directive and specifing AnyScriptDoc as the highlighting language.

The AnyScriptDoc is highlighter specifically for the documentation in sphinx. It can highlight AnyScript code even if the syntax is not correct, and any code fenced with § is §marked in red§.

Here is an example


```AnyScriptDoc

AnyBodyStudy Study = {
    AnyFolder &Model = .Model;
    Gravity = {0.0, §-9.81§, 0.0};
}; // End of study
```

Which gives the following:

AnyBodyStudy Study = {
    AnyFolder &Model = .Model;
    Gravity = {0.0, -9.81, 0.0};
}; // End of study

Valid values for the highlighting languages are:

  • none: no highlighting

  • AnyScript: AnyScript (Syntax must be valid)

  • AnyBodyDoc AnyScript (Allows invalid syntax)

  • python/c++/ruby Different known programming languages

  • markdown Markdown

  • … and any other lexer alias that Pygments supports.

Contents