Fix multiline ul/ol

src/css/minimalist.css

@@ -129,14 +129,16 @@ blockquote:after {
 li {
     position: relative;
     display: block;
-}
-li li {
     padding-left: 20px;
 }
 ul > li:before {
     content: "– ";
     font-weight: bold;
     opacity: 0.5;
+    float: left;
+    position: relative;
+    left: -20px;
+    width: 0;
 }
 ol {
     counter-reset: ol;
@@ -145,6 +147,10 @@ ol > li:before {
     content: counter(ol) ". ";
     counter-increment: ol;
     font-weight: bold;
+    float: left;
+    position: relative;
+    left: -20px;
+    width: 0;
 }
 img {
     max-width: 100%;

src/demo.org

@@ -89,14 +89,23 @@ There should be a forced newline.
       :END:
 
  - this is an unordered list following a header.
- - this is an unordered list following a header.
+ - this is an unordered list following a header. This time with quite a long
+   text that should goes to the line. Let's write a bit more text with some
+ =code= here, just to be sure that it use many lines.
  - this is an unordered list following a header.
 
- 1. this is an ordered list following a header.
- 2. this is an ordered list following a header.
+ 1. this is an ordered list.
+ 2. this is an ordered list that will use many lines. I will fill it with a bit
+    of random text. Also I will but some =code= inside it, with /italic/ and *bold*
+    text just to check the line-height.
     - sub unordered
       - sub sub unordered
-      - xxx
+      - Ok, Haxx0r ipsum concurrently malloc leet new injection bin epoch daemon
+        system Leslie Lamport shell spoof. Finally boolean continue mutex endif
+        it’s a feature gobble packet public irc race condition grep ifdef I’m
+        compiling. Try catch bar bytes I’m sorry Dave, I’m afraid I can’t do
+        that pragma win sql gnu kilo deadlock blob try catch exception Donald
+        Knuth brute force.
     - unordered
       1. ordered again
       2. yep :)
@@ -192,10 +201,19 @@ just to check.
        - State "HOLD"       from "IN-REVIEW"  [2019-07-09 Tue 13:44] \\
          some reason
 ****** WAITING waiting status
+       :PROPERTIES:
+       :CUSTOM_ID: waiting-status
+       :END:
        - State "WAITING"    from              [2019-07-09 Tue 13:44] \\
          waitin for someone
 ****** DONE done status
+       :PROPERTIES:
+       :CUSTOM_ID: done-status
+       :END:
 ****** CANCELED canceled status
        CLOSED: [2019-07-09 Tue 13:45]
+       :PROPERTIES:
+       :CUSTOM_ID: canceled-status
+       :END:
        - State "CANCELED"   from              [2019-07-09 Tue 13:45] \\
          cancel reason

src/index.org

@@ -16,8 +16,8 @@ So programming, functional programming in particular.
 That website was created with the following constraints in mind by order of
 priority:
 
-1. /Respect Privacy/; no tracker of any sort (no google ads, no referrer for all external links,
-   etc...)
+1. /Respect Privacy/; no tracker of any sort (no ads, no google analytics, no
+   referrer for all external links, etc...)
 2. /javascript free/; no js at all, yes even the theme changer
 3. /disability friendly/; should be easy to read on a text browser so people
    with disabilities could easily consume it