plan and list'

master
km0 1 year ago
parent 2a17a1b968
commit 1c1f3ebf3d

@ -48,6 +48,16 @@ ul + ul {
margin-top: 1rem;
}
li > ul {
font-family: serif;
font-style: italic;
display: inline;
}
li > ul:before {
content: "⟶";
}
/* p br {
height: 0;
line-height: 0;
@ -115,3 +125,8 @@ code {
top: 1rem;
right: 1rem;
}
h2 {
display: block;
margin-block: 1rem;
}

@ -44,8 +44,6 @@
<br>
- _writing machines_
- [bonfire - shared documentation surface](https://hub.xpub.nl/soupboat/bonfire/)
- [1dl - flat markup language](https://git.xpub.nl/kamo/dlist)
@ -103,7 +101,6 @@
- [drw ](https://git.xpub.nl/kamo/drw)
- [pad-bis](https://git.xpub.nl/kamo/pad-bis)
## third round
- emerging patterns
@ -129,17 +126,23 @@
- context: soupboat
- index of writing machines
- documentation for every writing machine
- thoughts around archiving situated software
- thoughts around document situated software
- thoughts around future of the soupboat
- focus points for selection
- what worked
- what didnt
<br>
- output
- outputs
- _digital_
- website?
- (admittedly im a bit bored of that)
- see opening of wlist readme
- "A small writing machine to experiment the list format. Its again web-to-print, its again flask, its again markdown, its again its again its again. Im 30% sorry."
- (that could be a nice trigger )
- but it's probably the most viable option
- could it be something different??
- really inspired by soft serve
@ -163,5 +166,119 @@
- like legs 👀
- like 3d printed legs such as the ones for the soupboat
## round 4
- publishing a series of readme files
- of significative documentations
- (significative for different reasons!)
- (style, writing methods, contents, etc.)
- for writing machines developed in the context of the soupboat
- additional focus points:
- thoughts around document situated software
- thoughts around future of the soupboat
<br>
- padliography -> situated software
- workbook -> collaborative
- exquisite branch / exex -> versioning
- si16 -> multi author
<br>
- _padliography_
- __what's there__
- intro
- catchy features!
- quick start
- how does it work / ecosystem
- development
- license
- __what's missing__
- from where it comes from
- serve behind reverse proxy
- updated api documentation
- interaction with the wiki
- deleting by accident chae's pages in the wiki
- choices made in development:
- vue?
- wiki?
- beautiful soup?
- hosting and hospitality
- multiple tables
- situated?
- constant padology is a good reference to create a context
- default pages
- environmental variable and credentials for the wiki
- future?
- example: installing it on the breadcube
<br>
- _workbook_
- developed together with supi!!!
- so also could be a place to try pair documenting
- __what's there__
- intro and overview
- add instrument
- export from Figma
- export from inkscape
- __what's missing__
- what + why / intentions
- add patch
- add snippet
- clone / development
- code documentation and tool documentation blend
- choices made in development:
- custom instruments
- flexibility accessibility performance goat
- situated?
- future?
- collaborative?
<br>
- _xbranch_ _exex_
- exex is a version of xbranch
- no documentation at all for xbranch
- started documenting
- __what is there__
- intro
- install
- overview
- __what is missing__
- development
- serve behind reverse proxy
- documentation from the api
- examples!
- background behind development? previous versions?
- situated?
- future?
- versioning?
<br>
- ok plan is to start these and then see what happens

Loading…
Cancel
Save