diff options
Diffstat (limited to 'articles/asciideck/index.html')
| -rw-r--r-- | articles/asciideck/index.html | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/articles/asciideck/index.html b/articles/asciideck/index.html index d15bac27..0b83d8d2 100644 --- a/articles/asciideck/index.html +++ b/articles/asciideck/index.html @@ -75,7 +75,7 @@ <p>Asciideck has been tested against around 600 Asciidoc documents that I wrote. This website is now generated using Asciideck (Hugo will use the <a href="https://github.com/ninenines/asciideck/blob/master/scripts/asciidoc">asciidoc</a> script to generate HTML). But a lot of elements are not parsed properly, or are ignored by translator modules. It will take many more documents to get close to the original Asciidoc implementation in terms of features.</p> <p>I wrote this project twice: first as an ugly prototype that generated man pages, and then I rewrote that using a different technique for parsing. I looked at a few different Asciidoc and Markdown implementations and found the Markdown code in Pandoc to be surprisingly readable despite being written in Haskell. I could not fully understand how it worked, but I could follow it based on my knowledge of the syntax.</p> <p>I decided to write small functions that only contain the "happy path" for each possible blocks in an Asciidoc document. Take this function for example:</p> -<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8 +<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.9 by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> @@ -110,6 +110,10 @@ http://www.gnu.org/software/src-highlite --> + <li><a href="https://ninenines.eu/articles/cowboy-2.7.0/">Cowboy 2.7</a></li> + + + <li><a href="https://ninenines.eu/articles/gun-2.0.0-pre.1/">Gun 2.0 pre-release 1</a></li> |