You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.7 KiB
1.7 KiB
| categories | cover | cover_alt | date | description | slug | title | git | url | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
enkidu.jpg | My tutors are enkidu and gilgamesh | 03/04/2023 | Practical token to graduate | writing-machines | Writing machines | https://git.xpub.nl/kamo/tag | https://hub.xpub.nl/soupboat/wm/ |
Things I'm sure about the graduation project
- It should be an interface between super technical people and super critical people
- Act as a backdoor: a way to expose certain kind of people to things they are not usually in contact with
- Mimetical ? ? ? Subtle, in plain sight
- A way to navigate documentation, but in critical waters
About the format:
- It could be an archive ?
- Loose and open categorization
- Expressive tag system
Apropos the tag system:
I can see the documentation sessions being a way to inform this tag system. To highlight critical aspects, diffract typical features, shift the balance.
Visual what
More like a visual archive, than a plain list? But what do you mean by visual? Don't you mean like.... screnshots? Mh i dont know ? I do read and visit a lot of code documentation, and all of them have a distinctive shape? More like their structure?
Would need some example of this for example flask documentation? nuxt/vue documentation? prepare a sketch
Ok im not really sure if this is useful or accurate at all, but