# Libasciidoc - a Golang Asciidoc renderer

**URL:** <https://discourse.gohugo.io/t/libasciidoc-a-golang-asciidoc-renderer/21702>\
**Category:** feature\
**Tags:** asciidoc\
**Created:** [November 9, 2019, 11:01am UTC](https://discourse.gohugo.io/t/libasciidoc-a-golang-asciidoc-renderer/21702 "2019-11-09T11:01:49Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![pgr](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/pgr/32/5329_2.png) [@pgr](https://discourse.gohugo.io/u/pgr)\
**Post date:** [December 31, 2023, 5:56pm UTC](https://discourse.gohugo.io/t/libasciidoc-a-golang-asciidoc-renderer/21702/19 "2023-12-31T17:56:54Z")

</div>

Good news regarding speed when integrating Hugo with the ruby asciidoctor:

> [@Asciidoctor Server](https://discourse.gohugo.io/t/asciidoctor-server/47475):
>
> I came up with asciidoctor-server to try improve the integration between asciidoctor and hugo. If you couldn’t guess by the name it uh … runs asciidoctor as a server. I use asciidoctor and hugo together, and really enjoy the combo. However, the performance is quite poor since hugo forks a process per file. Asciidoctor has a long startup time, in the 100’s of ms, and this adds up. I’d appreciate as much feedback and assistance as possible (the installation instructions make me cringe). Try it o…

@bep the principle behind that is pretty simple (keep it running as a server, avoid the repeated startup costs) maybe it could be worked into the Hugo architecture for every integration? I’m not sure this makes sense, I’m just dreaming out loud

Happy new year everyone! 🎉

---

_[View the full topic](https://discourse.gohugo.io/t/libasciidoc-a-golang-asciidoc-renderer/21702)._