From: Mehul Sanghvi <mehul.sanghvi@gmail.com>
To: Marc Seibert <org@foogu.de>
Cc: ML Emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: best way of customizing generated css to match bootstrap css
Date: Wed, 22 Jan 2014 15:35:06 -0500 [thread overview]
Message-ID: <CAPo9-A__Hmf-GyA=17WUx=xWXQfyj-xXJmzBwd8eUfKX-y5-UQ@mail.gmail.com> (raw)
In-Reply-To: <2084947337.63635.1365241040623.JavaMail.root@foogu.de>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Sat, Apr 6, 2013 at 5:37 AM, Marc Seibert <org@foogu.de> wrote:
> Hi,
>
> After using jekyll and o-blog a while I just fiddled around more in depth
> with org-publishing.
> I must say it is starting to convince me to stop using to wrapp my org
> generated html files with a wrapper like jekyll etc.
> Org-publishing seems to have all I need to do it directly.
>
> But I need an advice how to get better integration with twitter bootstrap
> css which I realy like.
> I know there is HTML_CONTAINER_CLASS etc. but I don't want to define the
> class and the id once for every heading, table etc.
> What would be the best option for setting this globally?
> Should I edit org-htmlize.el or something like this or is there a way of
> defining the different class names with an easier way?
>
> Regards
> Marc Seibert
>
>
I find myself in the same situation, having gone through both o-blog and
jekyll previously. Were you able to find a solution ?
What was it ? Is there anyone using anything else than the CSS that
ogr-mode uses ?
--
Mehul N. Sanghvi
email: mehul.sanghvi@gmail.com
[-- Attachment #2: Type: text/html, Size: 1632 bytes --]
next prev parent reply other threads:[~2014-01-22 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1582057433.63623.1365240622588.JavaMail.root@foogu.de>
2013-04-06 9:37 ` best way of customizing generated css to match bootstrap css Marc Seibert
2014-01-22 20:35 ` Mehul Sanghvi [this message]
2014-01-22 20:41 ` Peter Salazar
2014-01-22 21:17 ` Mehul Sanghvi
2014-01-24 5:00 ` Peter Salazar
2014-01-24 19:46 ` Mehul Sanghvi
2014-01-24 20:56 ` Peter Salazar
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='CAPo9-A__Hmf-GyA=17WUx=xWXQfyj-xXJmzBwd8eUfKX-y5-UQ@mail.gmail.com' \
--to=mehul.sanghvi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=org@foogu.de \
/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).