@ -48,6 +48,8 @@ Tipically an API architecture is centralized: there's a grand scheme and everyth
SI16 has been a space for plural, vernacular autorship to emerge. On the server side the API is structured as a directory, and to insert a new function it's enough to upload a Jupiter Notebook file with the script and its documentation. Jupiter Notebooks are interactive documents where code snippets and their explanations can be weaved together. They come handy for prototyping and documenting learning processes, writing code to be read not only from computers, but also from other programmers as well, in a paradigm also known as _literate programming_, introduced by Donald Knuth in 1984.
![Screenshoot of a Jupyter Lab IDE](../img/SI16_NB.jpg "Jupyter Notebook of the repeat function. On the left panel the filesystem with the other function files.")
![Technical documentation showing on the left side parameters, and on the right the returning values.](../img/SI16.jpg "Documentation generated from the Notebook files for the Repeat function")
![The picture of a parrots and description of the function.](../img/SI16_2.jpg "Versioned excerpt from the wikipedia page about parrots to explain the Repeat function.")