[elpa] externals/denote b651200fdf 236/355: Include "hackability" in the manual's overview

[ELPA Syncer]

branch: externals/denote
commit b651200fdff29957e0e1f9357087bfa5c3d1b46c
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Include "hackability" in the manual's overview
---
 README.org | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/README.org b/README.org
index fed52e00ac..89630b723b 100644
--- a/README.org
+++ b/README.org
@@ -106,8 +106,15 @@ principles:
   per note) and have a unique identifier.  However, Denote does not
   enforce a particular methodology for knowledge management, such as a
   restricted vocabulary or mutually exclusive sets of keywords.  It is
-  up to the user to apply the requisite rigor in pursuit of their
-  preferred workflow.
+  up to the user to apply the requisite rigor and/or creativity in
+  pursuit of their preferred workflow 
([[#h:6060a7e6-f179-4d42-a9de-a9968aaebecc][Writing metanotes]]).
+
++ Hackability :: Denote's code base consists of small and reusable
+  functions.  They all have documentation strings.  The idea is to make
+  it easier for users of varying levels of expertise to understand what
+  is going on and make surgical interventions where necessary (e.g. to
+  tweak some formatting).  In this manual, we provide concrete examples
+  on such user-level configurations 
([[#h:4a6d92dd-19eb-4fcc-a7b5-05ce04da3a92][Keep a journal or diary]]).
 
 Now the important part...  "Denote" is the familiar word, though it also
 is a play on the "note" concept.  Plus, we can come up with acronyms,