sitemap

jitsedesmet · Dec 2, 2023 · f3448c0 · f3448c0
1 parent 17ec2ca
commit f3448c0
Show file tree

Hide file tree

Showing 4 changed files with 11 additions and 8 deletions.
diff --git a/_config.yml b/_config.yml
@@ -28,7 +28,7 @@ theme: minima
 plugins:
   - jekyll-feed
   - jemoji
-  - jekyll-sidemap
+  - jekyll-sitemap
   - jekyll-seo-tag
 
 kramdown:

diff --git a/README.md → index.md b/README.md → index.md
@@ -1,3 +1,7 @@
+---
+title: Thesis Jitse De Smet
+---
+
 Repo for my thesis work. (Don't expect this to be too organized. It's just a way of sharing thoughts + backups)
 
 ## Intro

diff --git a/user-stories/storage/LDP.md b/user-stories/storage/LDP.md
@@ -124,7 +124,6 @@ That means the picture contains metadata like:
 
 
 
-# User stories
 ## User story collection 1: update data I own
 ### Insert data
 When Florence loads the pictures onto her computer, we assume that they are marked using the appropriate metadata.
@@ -202,7 +201,7 @@ No new problem.
 ### Pass the quilt master badge
 There is no real way of doing this with conformance to ACID.
 
-# User story collection 3: Update data I cannot update directly
+## User story collection 3: Update data I cannot update directly
 ### Insert data
 Not possible. Would need [Solid Notifications Protocol](https://solidproject.org/TR/notifications-protocol)
 
@@ -218,7 +217,7 @@ Same as above.
 ### Pass the runner of the month token
 Same as above. Not possible in ACID way.
 
-# Conclusion
+## Conclusion
 We now evaluate what functional requirements are met using :white_check_mark: and :x:.
 1. Data should remain consistent with the requirements posed by the **technology** (e.g., solid):
    :x:

diff --git a/user-stories/stories.md b/user-stories/stories.md
@@ -6,7 +6,7 @@ title: stories
 Question to ask people regarding expectations on:
 * If you had taken a picture and would ask your smart device to place it somewhere on your computer, what would you expect?
 
-# Functional requirements
+## Functional requirements
 We construct the following requirements:
 1. Data should remain consistent with the requirements posed by the **technology** (e.g., solid).
    An update should not be able to break your data storage or at least give you a warning before doing so.
@@ -64,10 +64,10 @@ When updating, where to update if variables/ subjects span multiple documents?
 * Determine the scope given the type you have? `Medical pictures` vs `personal pictures`.\
   -> Virtual container? -> GroupedBy
 
-# User stories
+## User stories
 We will use a single, slightly complex example of a fictional person that has different, complex ways of handling data.
 
-## Context
+### Context
 
 Let's consider the story of a photographer named Florence and her husband Wally.
 Because of her profession, Florence wants fine-grained control over the pictures she took.
@@ -93,7 +93,7 @@ The friend group organizes a monthly competition which they call "runner of the
 The winner of last month gets to keep a token, which they pass around based on who wins the competition.
 Notice that apposed to with her husband, the friends do not share update rights on their storage space.
 
-## Extracted stories (As an X, I want Y, so that Z, …)
+### Extracted stories (As an X, I want Y, so that Z, …)
 
 1. As a pod owner, I want to insert a picture that is **accessible by other pod** owners decided by me,
    so these people can access the pictures I took for them.