demo assessment

master
km0 2 years ago
parent 361ea1b921
commit a50541b1a8

@ -0,0 +1,99 @@
(situated documentation)
[demo]
assessment as a demo!!!
that means use a prototype of the list
to talk about the list
current writing machine is:
a flat markup language
that combines minimal hierarchy
and the linearity of a list structure
with the purpose of being easy to read and easy to write
and eventually flexible enough to be written in concert
more about it
https://git.xpub.nl/kamo/dlist
>> an updated version of the project proposal
>> keep in mind that we are talkin about an updated proposal
>> like a translated proposal sooo everything is already supercharged with meaning, but every transformation need to be addressed properly
(what do you want to make)
[overview]
A small documentation framework and a pubblication
grounded in the development of situated software
in the context of our group in XPUB
[our group]
up to 20 participants
10~ students + tutors + guests
coming from various background
[our ecosystem*]
the main space where these software run is the Soupboat
a server running on a Raspberry Pi
that hosts tools and prototypes
https://hub.xpub.nl/soupboat/
the main space used to document things is the wiki
along with scattered etherpad documents
and sometimes git
https://pzwiki.wdka.nl/mediadesign/
https://pad.xpub.nl/
https://git.xpub.nl/
* actually this is just a fraction of the whole XPUB infrastructure
[outcome]
it is actually composed by two parts
that held hands together
1
a pubblication
a soft index of the tools
we developed and are developing
what do they do
where to find them
how to use them
from where they come from
how we are documenting them
and how to contribute
2
the writing machine to work on it
a system as simple as a markup language
\(like this flat markup used to write this)
easy to read and easy to write
flexible and expressive enough
to articulate our tools as common
and this work of documentation as a form of care
(how do you want to make it)
[process]
facilitate the design of a system to keep track of our tools
offer some prompts on how to do it
that means where to gather them
--> to keep track == minimum viable product of documentation
[iterative]
[collaborative]
>> distinction between public and userbase
>> userbase > public
>> userbase < public

@ -0,0 +1,13 @@
12 i giorni della settimana se c'erano i # e b (salamino and all, 2022)
a thesis about documentation, that is: how to make the software
12 days a week if there were # and b (t o fu 12312 k - - zz, 2022)
and other things
(hello, 2022)

@ -74,4 +74,4 @@ def parse(file):
line = f.readline()
return json.dumps(parsed, indent=4)
print(parse('list.1dl'))
# print(parse('list.1dl'))

@ -0,0 +1,24 @@
# flat markup language
#2 layers
```
(title)
[section]
text
--> note (not clear about this)
>> comment
```
# 3 layer
```
{title}
[section]
(paragraph)
Text
--> note
>> comment
```
Loading…
Cancel
Save