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.

53 lines
1.6 KiB
Markdown

---
categories:
- Proj
- grad
- frog
cover: enkidu.jpg
cover_alt: My tutors are enkidu and gilgamesh
date: 03/04/2023
description: Practical token to graduate
slug: proj-monorepo
title: proj monorepo
---
## 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:
- [soup generator](https://hub.xpub.nl/soupboat/soup-gen/)
- [padliography](https://hub.xpub.nl/soupboat/padliography/)
- [site inspire](https://www.siteinspire.com/)
- [kamo soupboat](https://hub.xpub.nl/soupboat/~kamo/)
- [tagging aesthetic](https://medium.com/schizocities/tagging-aesthetics-recap-fe1897ad4855)
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
![flask structure](schema_01.svg)
![nuxt structure](schema_02.svg)
Ok im not really sure if this is useful or accurate at all, but