|
|
|
|
|
by gorgoiler
1658 days ago
|
|
I wrote a school textbook in asciidoc. It was a wonderful tool to use but it soon became rather painful and I wish I had used something more lightweight. 30s build times are misery for tweaking. Whatever was going on in the background — Prawn::PDF or something — was very slow about churning PNGs to format them into a PDF. I added some build logic to make “draft” PDFs with low res PNGs to speed things along, but it felt messy. Ultimately, I wish I had authored with HTML and CSS instead. Markdown isn’t a document format — it’s a means to creating HTML, sort of like an IDE except you write in test instead of use a specific editor runtime. The beauty is being able to drop HTML into your markdown and not have the processor trip over it. <aside>, <figure> etc all because first class entities as opposed to by products of some arbitrary ascii syntax fencing, and it brought me closer to the resultant HTML that made formatting with CSS much easier (in a later, much smaller project.) Print CSS is still very challenging unless you have the budget for Prince. You can do a lot if you give up hope of having everything happen automatically a la LaTeX. When you focus on the content over the formatting, these worries tend to evaporate. |
|