X-Git-Url: https://www.kengrimes.com/gitweb/?p=kengrimes.com%2Fcontent.git;a=blobdiff_plain;f=content.org;h=714e4f063bee59f3b96d75773a4a08949af13a38;hp=9de9616b2588d78f41b75e8c2cf4251a93513961;hb=HEAD;hpb=ef2968208b0629b49479959703ca092e4e034816

diff --git a/content.org b/content.org
index 9de9616..714e4f0 100644
--- a/content.org
+++ b/content.org
@@ -636,12 +636,39 @@ This will make any ~:EXPORT_DESCRIPTION:~ properties export, instead, to a
 able to replace exported values in the Org body:
 #+begin_src org
 ,#+begin_description
-This is the description, but will export as the Summary value in front-matter
+This is the description, 
+it has multiple lines too!
+It will export as the Summary value in front-matter
 ,#+end_description
 #+end_src
 To do this on a per-heading basis, simply add the
 ~:EXPORT_HUGO_FRONT_MATTER_KEY_REPLACE:~ property to a heading's property block,
 and the replacements will only occur within that heading.
+
+**** Why not use Hugo's internal Org parser?
+It's true that Hugo has an internal Org parser that is well maintained. It
+provides this as an alternative to markdown files. You may wonder, then, why
+someone would use Org mode to export to markdown instead of just letting Hugo
+parse the Org files itself. The answer is two-fold:
+1. Hugo's Org format is currently less feature complete than markdown, so
+   exporting from Org mode to the Hugo Org Format would limit potential output.
+2. Org mode is a lot more than just a file format, and its integration with your
+   system allows all kinds of benefits you can never get out of a simple Org
+   file parser.
+Therefore, supporting the Org format in another tool will give you a superior
+text format for organizing information, but it will be crippled when compared to
+an actual Org mode implementation. Ox-hugo gives you the ability to use Org mode
+itself to generate content.
+
+If Hugo's Org parser gains parity with, or eclipses, the Blackfriday Markdown
+format currently used by Hugo, ox-hugo could certainly be used to output those
+Org-Hugo files instead of the current markdown. This would be nice because it
+would allow Org mode users to view their output content more easily, but the
+advantages of ox-hugo and a real, bona fide Org mode would still remain.
+
+So you see, Hugo's Org parser isn't really in competition with ox-hugo, it's in
+competition with the /other/ Hugo parsers (e.g. markdown).
+
 *** Thanks
 Thanks to Kaushal Modi, who found this article on the googs within days of me
 posting it, for reaching out to me and providing thorough feedback and error
@@ -709,5 +736,5 @@ At Large
 Hi! I'm Ken, a 34-year-old computer scientist currently living in Irvine,
 California. This is a website I've constructed for the purpose of developing
 web-facing software. I will probably blog with it once development is
-complete. In the mean time, if you're curious, this is my [[file:static/cv.pdf][curriculum vitae]]
+complete. In the meantime, if you're curious, this is my [[file:static/cv.pdf][curriculum vitae]]