|
|
|
|
@ -6,8 +6,8 @@ categories:
|
|
|
|
|
- Web
|
|
|
|
|
- API
|
|
|
|
|
- Community
|
|
|
|
|
cover:
|
|
|
|
|
cover_alt:
|
|
|
|
|
cover: ah.jpg
|
|
|
|
|
cover_alt: ahah guy in paint
|
|
|
|
|
git: https://git.xpub.nl/kamo/workinon
|
|
|
|
|
url: https://hub.xpub.nl/soupboat/workinon/
|
|
|
|
|
---
|
|
|
|
|
@ -18,11 +18,15 @@ A small and shared archive to keep track of how ideas change during work, resear
|
|
|
|
|
A call to share what we are doing with others, while we are doing it.
|
|
|
|
|
In a way that doesn't focus on results, but on process and sharing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## How does it work
|
|
|
|
|
|
|
|
|
|
The core of Workinon is a small API that read and write updates to a JSON file.
|
|
|
|
|
The inputs can be received through a form from the application page.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Structure of the JSON:
|
|
|
|
|
|
|
|
|
|
a list of projects, and each update has a codename and a list of steps
|
|
|
|
|
@ -37,3 +41,5 @@ to update with a new step just refer to the name you used the first time and add
|
|
|
|
|
this structure is not super robust.
|
|
|
|
|
if two different project use the same codename, this could lead to interferences between the two
|
|
|
|
|
so one suggestion for the usage of the Workinon could be to choose a really really really personal title
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
