Refactor: Add custom notes layout

Author: benmezger

content/notes/2020-05-30--19-14-46Z--information_theory.md

@@ -4,7 +4,7 @@ author = ["Ben Mezger"]
 date = 2020-05-30T16:14:00-03:00
 slug = "information_theory"
 tags = ["computing", "theory", "information", "studies"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
@@ -39,7 +39,6 @@ drawings, each would contain the same number of bits though in different
 
 `Key contents: entropy; density, information`
 
-
 ## What is the density of a bit? {#what-is-the-density-of-a-bit}
 
 Bit density measures how many bits can be stored in some area or volume. As far
@@ -62,8 +61,7 @@ about 1.65 cm^2 so its bit density is about 64 GB / 1.65 cm^2 = 38.8 GB / cm^2.
 So, by this rough calculation the bit density of a microSD card is about
 24,250,000 times greater than that of a sheet of paper.
 
-
-## CURRENT Measuring information {#current-measuring-information}
+## <span class="org-todo todo CURRENT">CURRENT</span> Measuring information {#measuring-information}
 
 How can we quantify/measure an information source? Let's say Alice and Bob live
 on the opposite road of each other and they want to communicate during the
@@ -99,4 +97,4 @@ func main(){
 	}
 }
 
-```
+```

content/notes/2020-05-30--21-56-36Z--list_of_spority_artists.md

@@ -4,13 +4,13 @@ author = ["Ben Mezger"]
 date = 2020-05-30T18:56:00-03:00
 slug = "list-of-spotify-artists"
 tags = ["music"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 | Artists                            |
-|------------------------------------|
+| ---------------------------------- |
 | Lana Del Rey                       |
 | Slipknot                           |
 | CocoRosie                          |
@@ -408,4 +408,4 @@ bookCollapseSection = true
 | Steinsopp                          |
 | Sync24                             |
 | Grupo Revelação                    |
-| In The Hearts Of Emperors          |
+| In The Hearts Of Emperors          |

content/notes/2020-05-30--22-10-05Z--cool_companies.md

@@ -3,7 +3,7 @@ title = "Cool companies"
 author = ["Ben Mezger"]
 date = 2020-05-30T19:10:00-03:00
 slug = "cool-companies"
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++

content/notes/2020-05-30--22-22-20Z--org_mode_firefox_bookmarks.md

@@ -4,7 +4,7 @@ author = ["Ben Mezger"]
 date = 2020-05-30T19:22:00-03:00
 slug = "orgmode-firefox-bookmark"
 tags = ["emacs", "orgmode", "firefox"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
@@ -14,16 +14,21 @@ tags
 
 Add the following scripts to call org-capture from Firefox
 
-
 ## Call capture template {#call-capture-template}
 
 The following calls capture template key `n`
 
 ```js
-javascript:location.href='org-protocol://capture?template=n'+'&url='+encodeURIComponent(window.location.href)+'&title='+encodeURIComponent(document.title)+'&body='+encodeURIComponent(window.getSelection());
+javascript: location.href =
+  "org-protocol://capture?template=n" +
+  "&url=" +
+  encodeURIComponent(window.location.href) +
+  "&title=" +
+  encodeURIComponent(document.title) +
+  "&body=" +
+  encodeURIComponent(window.getSelection());
 ```
 
-
 ## Without a capture template {#without-a-capture-template}
 
 If unspecified, the template key is set in the variable
@@ -37,4 +42,4 @@ available:
 %i              The selected text
 ```
 
-See: <https:orgmode.org/manual/The-capture-protocol.html#The-capture-protocol>
+See: <https:orgmode.org/manual/The-capture-protocol.html#The-capture-protocol>

content/notes/2020-05-30--22-30-53Z--org_roam_firefox_bookmark.md

@@ -4,7 +4,7 @@ author = ["Ben Mezger"]
 date = 2020-05-30T19:30:00-03:00
 slug = "org-roam-firefox-bookmark"
 tags = ["emacs", "orgmode", "roam", "firefox"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
@@ -21,17 +21,16 @@ More documentation on the templating system can be found here.
 
 These templates should contain a `#+ROAM_KEY: ${ref}` in it.
 
-
 ## `Roam-ref` protocol {#roam-ref-protocol}
 
-Find and creates from with a specific ROAM\_KEY
+Find and creates from with a specific ROAM_KEY
 
 ```js
-javascript:location.href =
-'org-protocol://roam-ref?template=r&ref='
-+ encodeURIComponent(location.href)
-+ '&title='
-+ encodeURIComponent(document.title)
+javascript: location.href =
+  "org-protocol://roam-ref?template=r&ref=" +
+  encodeURIComponent(location.href) +
+  "&title=" +
+  encodeURIComponent(document.title);
 ```
 
-Related link: <https://org-roam.readthedocs.io/en/master/roam%5Fprotocol/>
+Related link: <https://org-roam.readthedocs.io/en/master/roam%5Fprotocol/>

content/notes/2020-05-30--22-53-04Z--the_communist_manifesto.md

@@ -4,15 +4,14 @@ author = ["Ben Mezger"]
 date = 2020-05-30T19:53:00-03:00
 slug = "communist-manifesto"
 tags = ["books", "reading"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 tags
 : [Politics]({{< relref "2020-06-02--11-52-08Z--politics" >}})
 
-
 ## READING The Communist Manifesto {#reading-the-communist-manifesto}
 
 <div class="table-caption">
@@ -21,12 +20,12 @@ tags
 </div>
 
 | Headline                | Time     |
-|-------------------------|----------|
+| ----------------------- | -------- |
 | **Total time**          | **2:36** |
 | The Communist Manifesto | 2:36     |
 
 :BOOK_CATEGORY: politics
 :BOOK_AUTHORS: Karl Marx, Friedrich Engels
 :START_DATE: <span class="timestamp-wrapper"><span class="timestamp">&lt;2020-05-25 Mon&gt;</span></span>
 :END_DATE: nil
-:URL: <https://www.amazon.com/Communist-Manifesto-Karl-Marx/dp/1508475660>
+:URL: <https://www.amazon.com/Communist-Manifesto-Karl-Marx/dp/1508475660>

content/notes/2020-05-30--22-57-32Z--the_pragmatic_programmer_from_journeyman_to_master.md

@@ -4,15 +4,14 @@ author = ["Ben Mezger"]
 date = 2020-05-30T19:57:00-03:00
 slug = "the-pragmatic-programmer"
 tags = ["reading", "books"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 tags
 : [Programming]({{< relref "2020-05-31--15-33-23Z--programming" >}}) [Computer Science]({{< relref "2020-05-31--15-29-21Z--computer_science" >}}) [Computer Architecture]({{< relref "2020-05-31--16-01-33Z--computer_architecture" >}})
 
-
 ## READING The Pragmatic Programmer: From Journeyman to Master {#reading-the-pragmatic-programmer-from-journeyman-to-master}
 
 <div class="table-caption">
@@ -21,12 +20,12 @@ tags
 </div>
 
 | Headline                          | Time      |
-|-----------------------------------|-----------|
+| --------------------------------- | --------- |
 | **Total time**                    | **10:04** |
 | The Pragmatic Programmer: From... | 10:04     |
 
 :BOOK_CATEGORY: Computer science, software architecture, software engineering
 :BOOK_AUTHORS: Andy Hunt, David Thomas
 :START_DATE: <span class="timestamp-wrapper"><span class="timestamp">&lt;2020-05-25 Mon&gt;</span></span>
 :END_DATE: nil
-:URL: <https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X>
+:URL: <https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X>

content/notes/2020-05-30--22-58-52Z--operating_systems_internals_and_design_principles_9th_edition.md

@@ -4,15 +4,14 @@ author = ["Ben Mezger"]
 date = 2020-05-30T19:58:00-03:00
 slug = "operating-systems"
 tags = ["reading", "books", "cs", "operating-systems"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 tags
 : [Computer Science]({{< relref "2020-05-31--15-29-21Z--computer_science" >}}) [Operating Systems]({{< relref "2020-05-31--15-29-38Z--operating_systems" >}})
 
-
 ## READING Operating Systems: Internals and Design Principles (9th Edition) {#reading-operating-systems-internals-and-design-principles--9th-edition}
 
 <div class="table-caption">
@@ -21,66 +20,65 @@ tags
 </div>
 
 | Headline                            | Time     |
-|-------------------------------------|----------|
+| ----------------------------------- | -------- |
 | **Total time**                      | **3:24** |
 | Operating Systems: Internals and... | 3:24     |
 
-
 ### Exercises {#exercises}
 
 1.1. CPU: Takes care of processing data
-   Main memory: Volatile memory for storing data and program instructions
-   Secondary storage: Non-volatile for permantely storing data.
-   I/O: External peripherals such as USB drive, printer and etc.
+Main memory: Volatile memory for storing data and program instructions
+Secondary storage: Non-volatile for permantely storing data.
+I/O: External peripherals such as USB drive, printer and etc.
 
 1.2. Memory address register (MAR): specifies the memory address for the next
-   read or write.
-   Memory buffer register (MBR): contains data to be written to memory or
-   receives data read from memory.
+read or write.
+Memory buffer register (MBR): contains data to be written to memory or
+receives data read from memory.
 
 1.3. Processor-memory: Data may be transferred from processor to memory or from
-   memory to processor.
-   Processor-IO: Process may transfer data to I/O module or from I/O module to
-   processor
-   Data processing: Processor may perform arithmetic or logical operation
-   Control: The instruction may specify a different location to fetch the next
-   instruction from, altering the sequence of execution.
+memory to processor.
+Processor-IO: Process may transfer data to I/O module or from I/O module to
+processor
+Data processing: Processor may perform arithmetic or logical operation
+Control: The instruction may specify a different location to fetch the next
+instruction from, altering the sequence of execution.
 
 1.4. Interrupts the current execution of the CPU. This allows external
-   peripherals to process data while the CPU works on something else. When the
-   data processing is over, the peripheral may trigger an interrupt requesting
-   CPU attention. A CPU interrupt handler may take care of interrupt or ignore it.
+peripherals to process data while the CPU works on something else. When the
+data processing is over, the peripheral may trigger an interrupt requesting
+CPU attention. A CPU interrupt handler may take care of interrupt or ignore it.
 
 1.5. There are two types of handling interrupts: sequentially or by
-   priority-policy. In sequential interrupts, if an interrupt happens within the
-   handler of a current interrupt, the interrupt will be ignored for the moment
-   by setting a pending interrupt. After it the current interrupt has been
-   dealt, it then treats the next pending interrupt. Priority-based interrupts
-   allows one interrupt to be handled by priority. Whiling handling one
-   interrupt, if another interrupt occurs and the priority is higher than the
-   current interrupt being dealt, it stores the current context and handles the
-   higher priority interrupt.
+priority-policy. In sequential interrupts, if an interrupt happens within the
+handler of a current interrupt, the interrupt will be ignored for the moment
+by setting a pending interrupt. After it the current interrupt has been
+dealt, it then treats the next pending interrupt. Priority-based interrupts
+allows one interrupt to be handled by priority. Whiling handling one
+interrupt, if another interrupt occurs and the priority is higher than the
+current interrupt being dealt, it stores the current context and handles the
+higher priority interrupt.
 
 1.6. Cost, speed, size are characteristics that are important
 
 <!--list-separator-->
 
--  Notes
+- Notes
 
-    <!--list-separator-->
+   <!--list-separator-->
 
-    -  Program execution
+  - Program execution
 
-        A program consists of a set of instructions stored in memory. The processor
-        fetches one instruction at a time and executes each instruction. The processing
-        required for one instruction is called the **instruction cycle**. The instruction
-        cycle is composed of three main stages:
+    A program consists of a set of instructions stored in memory. The processor
+    fetches one instruction at a time and executes each instruction. The processing
+    required for one instruction is called the **instruction cycle**. The instruction
+    cycle is composed of three main stages:
 
-        1.  Fetch stage: The process fetches an instruction from memory. Most processor
-            hold some type of PC (Program counter) register which points to the next
-            instruction in memory. Each time a new instruction has been fetched, the PC
-            is incremented to the next instruction. The fetch stage usually consists of the
-            following "substages"
-            -   Address of PC is copied to the MAR (Memory address register), which either
-                stores the memory address from where data will be fetched or the address to
-                which data will be sent or stored.
+    1.  Fetch stage: The process fetches an instruction from memory. Most processor
+        hold some type of PC (Program counter) register which points to the next
+        instruction in memory. Each time a new instruction has been fetched, the PC
+        is incremented to the next instruction. The fetch stage usually consists of the
+        following "substages"
+        - Address of PC is copied to the MAR (Memory address register), which either
+          stores the memory address from where data will be fetched or the address to
+          which data will be sent or stored.

content/notes/2020-05-30--23-00-17Z--clean_architecture.md

@@ -4,13 +4,12 @@ author = ["Ben Mezger"]
 date = 2020-05-30T20:00:00-03:00
 slug = "clean-architecture"
 tags = ["reading", "books"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 tags
 : [Computer Science]({{< relref "2020-05-31--15-29-21Z--computer_science" >}}) [Computer Architecture]({{< relref "2020-05-31--16-01-33Z--computer_architecture" >}}) [Programming]({{< relref "2020-05-31--15-33-23Z--programming" >}})
 
-
-## HOLD Clean Architecture {#hold-clean-architecture}
+## HOLD Clean Architecture {#hold-clean-architecture}

content/notes/2020-05-30--23-01-43Z--clean_code.md

@@ -4,13 +4,12 @@ author = ["Ben Mezger"]
 date = 2020-05-30T20:01:00-03:00
 slug = "clean-code"
 tags = ["toread", "books"]
-type = "posts"
+type = "notes"
 draft = false
 bookCollapseSection = true
 +++
 
 tags
 : [Computer Science]({{< relref "2020-05-31--15-29-21Z--computer_science" >}}) [Programming]({{< relref "2020-05-31--15-33-23Z--programming" >}}) [Computer Architecture]({{< relref "2020-05-31--16-01-33Z--computer_architecture" >}})
 
-
-## NEXT Clean Code {#next-clean-code}
+## <span class="org-todo todo NEXT">NEXT</span> Clean Code {#clean-code}