Merge pull request #19 from dwyl/tidy-how-section-issue#16

Tidy how section issue #16

README.md

@@ -142,7 +142,7 @@ And finally for the _third_ step, ***Complete***,
 we will build a simple checklist system.
 See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md)
 
-### USP: What is _different_ about the @dwyl App?
+### What is _different_ about the @dwyl App?
 
 A valid/relevant **question** is: what makes the @dwyl App unique?
 i.e. What is our
@@ -258,7 +258,8 @@ there are _so many_ useful features we want to build.
 _**Get involved today** and **help us prioritize**
 which **features** get built **next**_!
 
-## How?
+
+## _How_?
 
 If you want to get involved in helping us with the App,
 there are 4 ways to help:
@@ -276,15 +277,17 @@ See: https://github.com/dwyl/technology-stack
 
 ### Tech & Features Roadmap
 
-
 This list _will_ evolve over time. <br />
 We will insert links to specific features
 and check them off this list as we go.
 
+
 #### MVP Basic Workflow
 
 + [ ] Mobile First UI/UX to **Capture** **`plaintext`**
-+ [ ] Save **`plaintext`** data to Phoenix backend
+  Our _reasoning_ for mobile-first is that
++ [x] Save **`plaintext`** data to Phoenix backend
+  see: [dwyl/app/milestone/2](https://github.com/dwyl/app/milestone/2?closed=1)
 + [ ] Simple UX to **Categorise** (Transform)
 the **`plaintext`** into actionable items. <br />
 UI/UX **`help wanted`**: https://github.com/dwyl/app/issues/235
@@ -302,12 +305,16 @@ we will do a backlog grooming session to discuss the features/ideas list:
 
 + [ ] Create Progressive Web App using Elm.
 see: [dwyl/learn-elm#54](https://github.com/dwyl/learn-elm/issues/54)
+and [dwyl/app#254](https://github.com/dwyl/app/issues/254)
 + [ ] Save data on device if offline.
 
 #### Image Capture
 
+
+
 + [ ] Capture (_upload_) images from mobile.
-+ [ ] Categorise (_tag_) the images for findability.
++ [ ] Categorise (_tag_) the images for
+[findability](https://en.wikipedia.org/wiki/Findability).
 
 #### Authentication
 
@@ -317,6 +324,14 @@ see: [dwyl/learn-elm#54](https://github.com/dwyl/learn-elm/issues/54)
 + [ ] Associate **`items`** with **`person`**
 
 
+### Audit Logging and Record History
+
++ [ ] We need a way of preserving the history of certain records.
+Phoenix does not offer this by default.
+The Phoenix "CRUD" _overwrites_ records and **`deletes`** data _permanently_,
+this is undesirable if a person ever wants to _undo_ an action.
+See: https://github.com/dwyl/postgres-history-spike/issues/1
+
 
 <!--
 ## Brain Dump of Features

coaching-tool.md

@@ -16,7 +16,7 @@ I will request/try a non-alcoholic version of my favourite drink."
 
 > _**Note**: if we prefer to use an alternative goal-setting framework,
 we will incorporate that into the app with relative ease.
-This is just a starting point.
+This is just a starting point_.
 
 3. Frictionless Capture:
 Make tracking their behaviour/consumption as easy as possible; 2 taps.

collaborative-learning-community.md

@@ -10,10 +10,6 @@ he asks this "contrarian question":
 as it will make you _think_
 and encourage you
 to _question_ your own _assumptions_ & _biases_.
-> + Full PDF:
-http://gsl.mit.edu/media/programs/south-africa-summer-2015/materials/0to1.pdf
- (150 pages. read it! Peter is easily one of the smartest
-   people in the world!)
 > + Summary/discussion:
 https://fs.blog/2015/11/the-single-best-interview-question-you-can-ask/
 > + Video summary (recap):
@@ -26,7 +22,7 @@ https://www.reddit.com/r/IAmA/comments/2g4g95/peter_thiel_technology_entrepreneu
 This document is our _answer_ to the [question](https://github.com/nelsonic/nelsonic.github.io/issues/231#issuecomment-419693586).
 In short we feel that:
 
-### 1. _Most_ **education** is _fundamentally_ "broken".
+## 1. _Most_ **education** is _fundamentally_ "broken".
 
 Teachers in ***most*** primary, middle and high **schools**
 are forced to "_**teach** to the **test**_".
@@ -110,7 +106,7 @@ it would be a "door stop"!
 We intend to make each lesson "byte sized" and
 allow people to track their progress in a user-friendly way.
 
-### 2. Compairing relative skill/experience levels is _hard_.
+## 2. Comparing relative skill/experience levels is _hard_.
 
 It has _historically_ been
 quite difficult to _measure_ relative skill level
@@ -160,7 +156,7 @@ We have to "start somewhere"; we feel the best place to start
 is with sharing the knowledge we _already_ have.
 See details below in "Collaborative Learning Community".
 
-### 3. **Asking questions** online while learning is _frustrating_!
+## 3. **Asking questions** online while learning is _frustrating_!
 
 Asking questions is a source stress and frustration in many "forums"
 or question/answer sites where beginners often feel _unwelcome_.
@@ -227,7 +223,7 @@ feedback/reinforcement when they ask a question!
 + A tally of the questions they ask should be kept as a "karma score".
 
 
-### 4. Creative technology work is "_unevenly distributed_" by "gatekeepers"
+## 4. Creative technology work is "_unevenly distributed_" by "gatekeepers"
 
 Creative tech work is unfairly distributed
 to people with skills/experience by a handful of "gatekeepers"
@@ -374,7 +370,7 @@ without registration and licensed as creative commons (_non-commercial_).
   the answers become.
 + Questions/Answers should be linked to learning materials.
   + it should be clear at which point in the learning material
-  the question was raised. So the Q/A is _contextual_.
+  the question was raised. So the Q/A _contextual_.
   + Wherever possible questions/answers should be self-contained
   and thus generally applicable. But if the question is _specific_
   to the learning material in question, that's fine too,