commit 61ad59c1ab97f4af555d143dc4b7d469e0f1c055 Author: km0 Date: Sun May 21 17:34:09 2023 +0200 init diff --git a/entries.json b/entries.json new file mode 100644 index 0000000..5232146 --- /dev/null +++ b/entries.json @@ -0,0 +1,46 @@ +{ + "entries": [ + { + "title": "exex", + "description": "collaborative writing for branching documentation", + "tags": "tool, writing, collaborative", + "gradient": "tool practice tool practice tool tool" + }, + { + "title": "pair documenting", + "description": "like pair programming, but for documentation", + "tags": "practice, writing, collaborative", + "gradient": "practice practice practice" + }, + { + "title": "1dl", + "description": "1dimension ~ flat markup language ", + "tags": "tool, markup, writing", + "gradient": "tool practice tool tool practice" + }, + { + "title": "textoscope", + "description": "adjust text intensity", + "tags": "tool, reading, writing", + "gradient": "tool tool platform practice practice" + }, + { + "title": "read out loud", + "description": "voicing code documentation", + "tags": "reading, audio", + "gradient": "practice tool practice" + }, + { + "title": "openings", + "description": "inflating deflating first sentences", + "tags": "reading, language", + "gradient": "practice practice practice tool" + }, + { + "title": "tree", + "description": "code documentation wanderer", + "tags": "tool, markup, practice", + "gradient": "tool practice tool practice tool practice" + } + ] +} \ No newline at end of file diff --git a/entries/exex/index.html b/entries/exex/index.html new file mode 100644 index 0000000..465fc95 --- /dev/null +++ b/entries/exex/index.html @@ -0,0 +1,132 @@ + + + + + Exex + + + + + + +

EXEX

+
collaborative writing for branching documentation
+ +
+
+ collaborative + writing + tool +
+ + +
+ + + + + + + + + + +
+

Context

+

+ A branching version of the exquisite corpse game, forked from the exquisite branch drawing app developed for SI17. +

+

+ Write something, upload it and send the link to someone else: they will continue from your excerpt. With a catch: if you send to just one person the chain will continue linearly, but send it to more people and things will start branching in different directions. +

+ +

+ Could be a writing machine to work on the collective pubblication for the graduation, inspired by what Kim wrote here +

+
+ +
+

reflections

+ + + + +
+ +
+

examples

+
+ + + +
+ + + + + + + + + diff --git a/entries_backup.json b/entries_backup.json new file mode 100644 index 0000000..4474712 --- /dev/null +++ b/entries_backup.json @@ -0,0 +1,28 @@ +{ + "entries": [ + { + "title": "exex", + "description": "collaborative writing for branching documentation", + "tags": "tool, writing, collaborative", + "gradient": "tool practice tool practice tool tool" + }, + { + "title": "pair documenting", + "description": "like pair programming, but for documentation", + "tags": "practice, writing, collaborative", + "gradient": "practice practice practice" + }, + { + "title": "1dl", + "description": "1dimension ~ flat markup language ", + "tags": "tool, markup, writing", + "gradient": "tool practice tool tool practice" + }, + { + "title": "textoscope", + "description": "adjust text intensity", + "tags": "tool, reading, writing", + "gradient": "tool tool platform practice practice" + } + ] +} diff --git a/index.html b/index.html new file mode 100644 index 0000000..ee86fb6 --- /dev/null +++ b/index.html @@ -0,0 +1,141 @@ + + + + + A toolkit,,, erg + + + + + + + + +

Hello worlding

+ +
+There are words around code: they create entry points and help understand software. They offer ways to reason about programming, they highlight certain features and hide unexpected flaws. They describe the surroundings of an application: how does it interact with neighbouring systems and how does it address involved developers. +These words make worlds around code. Worlds with embedded values, active actors and politics of participation. +
+ +
+Here is a collection of writing machines to explore practices of code documentation. To reflect and operate on the words they use, on the assumption they make, on the ways they are produced. + +A writing machine is a device that transforms writing. It can be a tool, such as a pen or a typewriter or a text editor, it can be a practical approach, like documenting in pairs or avoiding or insisting on specific terms. + +This collection includes strategies developed during the past two years of within the context and infrastructure of the Soupboat, a small self-hosted server home to various piece of software and experiments. +
+ +
+Every entry comes with: + + +Every entry can be further activated with workshops, or by applying it to different projects. It can be something that slowly thrives and transforms. + +Every entry it's a way to explore sociality around code at different intensities: some developers could be more at ease using instruments, some others more with developing habits and practical workflows. +
+ + + + +
+tools + +pratices +
+ + + + + + + + + + + + +
TitleDescriptionTags
+ + + + + + + + + + + diff --git a/new.py b/new.py new file mode 100644 index 0000000..a5e90ea --- /dev/null +++ b/new.py @@ -0,0 +1,19 @@ +import json + +title = input('Title: ') +description = input('Description: ') +tags = input('Tags: ') +gradient = input('Gradient: ') + +with open('entries.json', 'r') as f: + data = json.load(f) + +data["entries"].append({ + "title": title, + "description": description, + "tags": tags, + "gradient": gradient +}) + +with open('entries.json', 'w') as f: + json.dump(data, f, ensure_ascii=False, indent=4) diff --git a/prev.html b/prev.html new file mode 100644 index 0000000..ba9c9e7 --- /dev/null +++ b/prev.html @@ -0,0 +1,110 @@ + + + + + + + + +
+mh trying to sort out a gradient way to filter the writing machines
+using yet another writing machine such as a gradient
+that seems more expressive than a percentage system, 
+
+the very same amount
+    (
+    tool: 60%
+    practice: 40%
+    )
+
+it can be written in a gradient form as 
+    (
+    tool tool tool practice practice
+    )
+
+but also
+    (
+    tool practice tool practice tool
+    )
+
+in a way that adds more qualities to the quantity
+in a similar way, just adding another feature
+is as easy as adding it to the gradient
+    (
+    tool tool tool practice practice platform
+    )
+while in a percentage system adding                 hooowwww where are yanother dimension
+would mean to revisit all the previous property to sum up to 100 
+
+ +
+    but maybe the point is not to filter things ?
+    could anyway be something interesting to develop:
+    1 find components
+    2 place them spatially
+        2pi / components.lenght = angle for each component
+        how to place components?
+        could it be a mix between
+
+            a. chronologic order
+                cycle through components
+                insert every new component in a new angle position
+            
+            b. positional order
+                ??? 
+                cycle again through components
+                get first and last distincts of list
+                grade them
+                aaa ok too difficult for now
+                actually maybe this is multi d vector math 
+                and i dont have the minimal clue about it
+                ahah
+
+ + +
+ + + + diff --git a/readme.md b/readme.md new file mode 100644 index 0000000..7ef768f --- /dev/null +++ b/readme.md @@ -0,0 +1,17 @@ +# Hello worlding + +There are words around code: they create entry points and help understand software. They offer ways to reason about programming, they highlight certain features and hide unexpected flaws. They describe the surroundings of an application: how does it interact with neighbouring systems and how does it address involved developers. These words make worlds around code. Worlds with embedded values, active actors and politics of participation. + +Here is a collection of writing machines to explore practices of code documentation. To reflect and operate on the words they use, on the assumption they make, on the ways they are produced. A writing machine is a device that transforms writing. It can be a tool, such as a pen or a typewriter or a text editor, it can be a practical approach, like documenting in pairs or avoiding or insisting on specific terms. This collection includes strategies developed during the past two years of within the context and infrastructure of the Soupboat, a small self-hosted server home to various piece of software and experiments. + +Every entry comes with: + +- some context +- some reflections +- some examples + +Every entry can be further activated with workshops, or by applying it to different projects. It can be something that slowly thrives and transforms. Every entry it's a way to explore sociality around code at different intensities: some developers could be more at ease using instruments, some others more with developing habits and practical workflows. + +## Note + +Experimenting with inflatable identity diff --git a/style.css b/style.css new file mode 100644 index 0000000..d32f581 --- /dev/null +++ b/style.css @@ -0,0 +1,117 @@ + + body { + margin: 32px; + font-family: sans-serif; + line-height: 1.6; + color: dodgerblue; + } + + pre, + section { + font-family: sans-serif; + font-size: 1rem; + line-height: 1.6; + padding: 1em; + border: 1px dashed currentColor; + max-width: 80ch; + margin-block: 1em; + transition: all 0.6s ease-out; + } + + table { + border-collapse: collapse; + } + + thead { + font-weight: bold; + } + + tr { + border: 1px solid currentColor; + position: relative; + } + + td { + border: 1px solid currentColor; + padding: 1em; + } + + td.title { + font-style: italic; + + } + + td.tags { + display: flex; + justify-content: flex-start; + flex-wrap: wrap; + gap: 8px; + border: none; + } + + .tag { + display: inline-block; + background-color: dodgerblue; + color: white; + border-radius: 1em; + padding: 2px 8px; + } + + + .controller { + margin-block: 32px; + + } + + span:not(.tag) { + transition: transform 5s ease-in 5s, margin 5s ease-in 5s; + transform: scale(1); + display: inline-block; + margin: 0; + + } + + span:hover:not(.tag) { + transform: scale(2)!important; + transition: transform 0.2s, margin 0.2s; + cursor: zoom-in; + margin: 4px; + } + + h1 { + margin-bottom: 0; + font-size: 46px; + } + + h2 { + margin-block: 0; + } + + + .meta { + display: flex; + align-items: center; + gap: 16px; + } + + .links { + list-style: none; + padding: 0; + display: flex; + gap: 8px; + } + + a { + color: currentColor; + font-weight: bold; + } + + .stretched-link:after { + content: ''; + position: absolute; + top: 0; + left: 0; + width: 100%; + height: 100%; + z-index: 50; + }