hello worlding hllo hello procrastination day

desc/entries.json

@@ -16,14 +16,31 @@
             "title": "1dl",
             "description": "1dimension ~ flat markup language ",
             "tags": "tool, markup, writing",
-            "gradient": "tool practice tool tool practice" 
+            "gradient": "tool practice tool tool practice"
         },
         {
             "title": "textoscope",
             "description": "adjust text intensity",
             "tags": "tool, reading, writing",
-            "gradient": "tool tool platform practice practice" 
-        } 
- 
+            "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"
+        }
     ]
-}
+}

desc/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" 
+        } 
+    ]
+}

desc/index.html

@@ -20,14 +20,13 @@
         line-height: 1.6;
         padding: 1em;
         border: 1px dashed currentColor;
-        display: inline-block;
         max-width: 80ch;
         margin-block: 1em;
     }
 
     table {
         border-collapse: collapse;
-    }
+    } 
 
     thead {
         font-weight: bold;
@@ -37,6 +36,11 @@
         border: 1px solid currentColor;
         padding: 1em;
     }
+    
+    td.title {
+        font-style: italic;
+
+    }
 
     .tag {
         display: inline-block;
@@ -56,6 +60,18 @@
 
     }
 
+    span {
+        transition: transform 5s ease-in 5s;
+        transform: translate(0,0);
+        display: inline-block;
+    }
+
+    span:hover {
+        transform: translate(0, -10px)!important;
+        transition: transform 0.2s;
+        cursor: zoom-in;
+    }
+
     </style>
 
 
@@ -67,28 +83,30 @@
 
 <h1>Hello worlding</h1>
 
-<section class="intro">
-A collection of writing machines to explore practices of code documentation.
+<section>
+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. 
+</section>
 
-A set of tools and prompts to handle code documentation. To reflect and operate on the words they use, on the assumption they make, on the ways they are produced.
+<section>
+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.
+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.
 </section>
 
-<section class="more">
+<section>
 Every entry comes with:
+<ul>
+    <li>some context</li>
+    <li>some reflections</li>
+    <li>some examples</li>
+</ul>
 
-- 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 can be further activated with workshops, or by applying it to different projects. so it can be something that slowly thrive and transform. 
-
-it's a way to explore sociality around code at different intensities
-some people could be more at ease using instruments
-some others more with developing habits and practical workflows
+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. 
 </section>
 
 
@@ -104,9 +122,9 @@ some others more with developing habits and practical workflows
 <table>
     <thead>
         <tr>
-            <td class="title">Title</td>
-            <td class="description">Description</td>
-            <td class="tags">Tags</td>
+            <td>Title</td>
+            <td>Description</td>
+            <td>Tags</td>
         </tr>
     </thead>
     <tbody>
@@ -154,17 +172,30 @@ some others more with developing habits and practical workflows
     }
 
 
+const r = (scale=1) => Math.random() * scale - (scale * 0.5) 
    
+const wobble = () => {
+    const all = document.body.querySelectorAll('*:not(table):not(tr):not(thead):not(tbody):not(.controller)')
+    Array.from(all).forEach(e=>{
+        e.innerHTML = Array.from(e.textContent).map(c=>{
+            // replace space with &nbsp; character, otherwise empty span = width 0
+            c = c == ' ' ? '&nbsp;' : c
+            // wobble with centered random function
+            return `<span style="transform: translate(${r(1)}px, ${r(2)}px)">${c}</span>`
+        }).join('')
+        e.style.transform = `translate(${r(10)}px, ${r(10)}px)`
+        console.log(r())
+    })
+    }
 
 
-
-
+    
 
     fetch('entries.json').then(res=>res.json()).then(res=> {
-        const table = document.querySelector('table tbody')
+        const table = document.querySelector('table tbody') 
         table.append(...populateTable(res.entries))
         })
-
+        wobble()
 
 
 </script>

desc/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)