From: Karsten Schmidt <info@toxi.co.uk>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] thi.ng/org-spec template for tech specs & HTML export theme
Date: Wed, 3 Aug 2016 12:00:23 +0100 [thread overview]
Message-ID: <CAKoXdG5PAw0eyMg2emWQS2ft95ojgjAA19qT+=WdVFMoa=i=Yw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3Y3GGqO+fPGrg24LGLZ14h0qz_26+0iWrn5WT4GqzPYw@mail.gmail.com>
Thanks Kaushal! :)
I also think that we generally need more examples showing how flexible
& powerful org-mode is for these use cases. The majority raves about
Markdown, but for me it just lacks a ton of features I've become so
accustomed to w/ org-mode, especially when it comes to writing and
managing larger docs (i.e. the latest tech spec I've been working on
is 9000+ words) and dozens of diagrams (all text based!)
Re: PDF export - for me going the route via HTML is just easier & more
time saving (can control important print features via a few lines of
CSS). Plus I don't need to install 2.5GB of MacTex :) Also, the
generated PDF looks same as HTML, has hyperlinks etc. Haven't tried w/
MathJax yet, though...
Expect a few more updates over the coming weeks:
- move to SASS for style sheets, for easier re-skinning via variables
- improve TOC
- add back-to-top links
- add more diagram examples (incl. data extraction from tables)
- add optional support for highlight.js
Cheers!
On 1 August 2016 at 23:35, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Sun, Jul 31, 2016 at 8:55 AM Karsten Schmidt <info@toxi.co.uk> wrote:
>>
>>
>> To give a little back to this amazing group of people, I've just
>> published a skeleton template for writing tech docs and publishing
>> them as HTML.
>>
>> GH project: http://thi.ng/org-spec
>> Demo: http://demo.thi.ng/org-spec
>
>
> Thanks Karsten! I had a look through those and it looks awesome! I think
> they serve as very good examples in general on how to use org for technical
> documentation.
>
> I yet have to try out printing PDF from the browser using your style.css. I
> generally rely on the org exporter to generate both HTML and PDF. What
> limitations did you face when using the org latex exporter for generating
> the PDF?
> --
>
> Kaushal Modi
--
Karsten Schmidt
http://postspectacular.com | http://thi.ng | http://toxiclibs.org
next prev parent reply other threads:[~2016-08-03 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 12:53 [ANN] thi.ng/org-spec template for tech specs & HTML export theme Karsten Schmidt
2016-08-01 22:35 ` Kaushal Modi
2016-08-03 11:00 ` Karsten Schmidt [this message]
2016-08-01 23:47 ` Adam Porter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKoXdG5PAw0eyMg2emWQS2ft95ojgjAA19qT+=WdVFMoa=i=Yw@mail.gmail.com' \
--to=info@toxi.co.uk \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).