diff --git a/README.md b/README.md
index 1afbb61..bbb293b 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,7 @@ My problem is that I don't trust any of the systems I am currently using:
 - head: I forget things, short-term memory limited
 - paper: many slips flying around, can get lost easily
 - CLIs: too verbose to use, didn't get me the information I needed in time
+- web: too many clicks, too slow, not available offline, often unflexible
 
 # Design
 
@@ -27,9 +28,10 @@ The most important rule: Everything is a task. There is nothing else.
 
 Projects, Areas, Epics - they can all be mapped onto tasks, and doing so will allow you to leverage the same toolset on everything.
 A project or epic is a completable task with subtasks - it can itself be a subtask.  
-If you want to divide your task list into areas, these can simply be uncompletable tasks at the root level.
+To divide your task list into areas, simply put everything under uncompletable (see task type activity) root tasks.
 
-With everything being a task, areas and projects can also have all kinds of tags and attributes. And then subtasks may inherit these attributes (particularly tags).
+With everything being a task, areas and projects can also have all kinds of tags and attributes.
+And then subtasks may inherit these attributes (particularly tags).
 
 More fundamentals:
 - UNIX philosophy: use plain text is possible, separate into independent modules
@@ -87,9 +89,21 @@ I have been using [taskwarrior] for a few weeks now, but I am already starting t
 # Links
 
 [taskwarrior]: https://taskwarrior.org/  
-- https://tasklite.org/related.html: List of CLI-oriented productivity systems  
+
+## Discussions
+- https://kolaente.dev/vikunja/api/issues/1198: 
+  Thoughts on Vikunja, my new hope.
+- https://github.com/lyz-code/pydo/issues/73: 
+  Short discussion on a beta-level tool with convenient short ids.
+- https://www.wired.com/2016/03/best-to-do-list-app/: 
+  Maybe Technology won't help, after all...
+
+## Projects
+- https://codeberg.org/equilibrium/equilibrium: 
+  A Haskell project I started to link task managers,
+  unfortunately abandoned by now.
+- https://tasklite.org/related.html: 
+  List of CLI-oriented productivity systems  
   Should have a look at:
-  - org mode
+  - org mode (agenda)
   - taskell
-- https://github.com/lyz-code/pydo: new tool, short ids
-- https://www.wired.com/2016/03/best-to-do-list-app/: Why technology 
diff --git a/concepts.md b/concepts.md
index 583da0a..b5b9d08 100644
--- a/concepts.md
+++ b/concepts.md
@@ -2,12 +2,13 @@ All task managers I have seen so far were quite opinionated. Since task manageme
 To build trust in the system, it needs to be your system.
 
 So the foundational principle of this task manager is to rely as little as possible on special mechanics, implementing all convenience behavior and specialized features in a generalized way, allowing to easily compose and customize them.
-The 
 
+One only really needs key-value properties and tags (valueless properties) which can be assigned to tasks,
+all other structures which humans might want can be derived from these in the frontend.
+
+Then one can define views/lists/filters using key-value and tag queries:
 ```
-[tag]
+[view]
 	big=size:l
 	break=size:s -pc
-
-
 ```