Deploying to gh-pages from @ ca4a7421bc 🚀

manual/The-Templating-System.html

@@ -69,8 +69,9 @@ Next: <a href="Concepts-and-Configuration.html#Concepts-and-Configuration" acces
 <a name="The-Templating-System-1"></a>
 <h2 class="chapter">6 The Templating System</h2>
 
-<p>Rather than creating blank files on &lsquo;<samp>org-roam-insert</samp>&rsquo; and &lsquo;<samp>org-roam-find-file</samp>&rsquo;, it
+<p>Rather than creating blank files on <code>org-roam-insert</code> and <code>org-roam-find-file</code>,
-may be desirable to prefill the file with templated content. This may include:
+it may be desirable to prefill the file with templated content. This may
+include:
 </p>
 <ul>
 <li> Time of creation
@@ -80,15 +81,17 @@ may be desirable to prefill the file with templated content. This may include:
 </li></ul>
 
 <p>This requires a complex template insertion system. Fortunately, Org ships with a
-powerful one: &lsquo;<samp>org-capture</samp>&rsquo;. However, org-capture was not designed for such use.
+powerful one: <code>org-capture</code> (see <a href="http://www.gnu.org/software/emacs/manual/html_node/org/capture.html#capture">(org)capture</a>). However, org-capture was not
-Org-roam abuses &lsquo;<samp>org-capture</samp>&rsquo;, extending its syntax. To first understand how
+designed for such use. Org-roam abuses <code>org-capture</code>, extending its syntax and
-org-roam&rsquo;s templating system works, it may be useful to look into basic usage of
+capabilities. To first understand how org-roam&rsquo;s templating system works, it may
-&lsquo;<samp>org-capture</samp>&rsquo;.
+be useful to look into basic usage of <code>org-capture</code>.
 </p>
-<p>Org-roam&rsquo;s templates can be customized by modifying the variable
+<p>For these reasons, Org-roam capture templates are not compatible with regular
-&lsquo;<samp>org-roam-capture-templates</samp>&rsquo;. Just like the base &lsquo;<samp>org-capture</samp>&rsquo; this variable can
+<code>org-capture</code>. Hence, Org-roam&rsquo;s templates can be customized by instead
-contain multiple templates, in which case you will be prompted on which one to
+modifying the variable <code>org-roam-capture-templates</code>. Just like
-use when capturing a new note.
+<code>org-capture-templates</code>, <code>org-roam-capture-templates</code> can contain multiple
+templates. If <code>org-roam-capture-templates</code> only contains one template, there
+will be no prompt for template selection.
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top">&bull; <a href="Template-Walkthrough.html#Template-Walkthrough" accesskey="1">Template Walkthrough</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">

org-roam.org

@@ -349,8 +349,9 @@ The backlinks buffer will show any cites of this key: e.g.
 [[file:images/org-ref-citelink.png]]
 * The Templating System
 
-Rather than creating blank files on =org-roam-insert= and =org-roam-find-file=, it
+Rather than creating blank files on ~org-roam-insert~ and ~org-roam-find-file~,
-may be desirable to prefill the file with templated content. This may include:
+it may be desirable to prefill the file with templated content. This may
+include:
 
 - Time of creation
 - File it was created from
@@ -358,15 +359,17 @@ may be desirable to prefill the file with templated content. This may include:
 - Any other data you may want to input manually
 
 This requires a complex template insertion system. Fortunately, Org ships with a
-powerful one: =org-capture=. However, org-capture was not designed for such use.
+powerful one: ~org-capture~ (see info:org#capture). However, org-capture was not
-Org-roam abuses =org-capture=, extending its syntax. To first understand how
+designed for such use. Org-roam abuses ~org-capture~, extending its syntax and
-org-roam's templating system works, it may be useful to look into basic usage of
+capabilities. To first understand how org-roam's templating system works, it may
-=org-capture=.
+be useful to look into basic usage of ~org-capture~.
 
-Org-roam's templates can be customized by modifying the variable
+For these reasons, Org-roam capture templates are not compatible with regular
-=org-roam-capture-templates=. Just like the base =org-capture= this variable can
+~org-capture~. Hence, Org-roam's templates can be customized by instead
-contain multiple templates, in which case you will be prompted on which one to
+modifying the variable ~org-roam-capture-templates~. Just like
-use when capturing a new note.
+~org-capture-templates~, ~org-roam-capture-templates~ can contain multiple
+templates. If ~org-roam-capture-templates~ only contains one template, there
+will be no prompt for template selection.
 
 ** Template Walkthrough
 

org-roam.texi

@@ -525,8 +525,9 @@ The backlinks buffer will show any cites of this key: e.g.
 @node The Templating System
 @chapter The Templating System
 
-Rather than creating blank files on @samp{org-roam-insert} and @samp{org-roam-find-file}, it
+Rather than creating blank files on @code{org-roam-insert} and @code{org-roam-find-file},
-may be desirable to prefill the file with templated content. This may include:
+it may be desirable to prefill the file with templated content. This may
+include:
 
 @itemize
 @item
@@ -540,15 +541,17 @@ Any other data you may want to input manually
 @end itemize
 
 This requires a complex template insertion system. Fortunately, Org ships with a
-powerful one: @samp{org-capture}. However, org-capture was not designed for such use.
+powerful one: @code{org-capture} (see @ref{capture,,,org,}). However, org-capture was not
-Org-roam abuses @samp{org-capture}, extending its syntax. To first understand how
+designed for such use. Org-roam abuses @code{org-capture}, extending its syntax and
-org-roam's templating system works, it may be useful to look into basic usage of
+capabilities. To first understand how org-roam's templating system works, it may
-@samp{org-capture}.
+be useful to look into basic usage of @code{org-capture}.
 
-Org-roam's templates can be customized by modifying the variable
+For these reasons, Org-roam capture templates are not compatible with regular
-@samp{org-roam-capture-templates}. Just like the base @samp{org-capture} this variable can
+@code{org-capture}. Hence, Org-roam's templates can be customized by instead
-contain multiple templates, in which case you will be prompted on which one to
+modifying the variable @code{org-roam-capture-templates}. Just like
-use when capturing a new note.
+@code{org-capture-templates}, @code{org-roam-capture-templates} can contain multiple
+templates. If @code{org-roam-capture-templates} only contains one template, there
+will be no prompt for template selection.
 
 @menu
 * Template Walkthrough::