From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Tuning the layout of published html
Date: Fri, 22 Jul 2016 10:19:55 +0300 [thread overview]
Message-ID: <87y44u16n8.fsf@iki.fi> (raw)
In-Reply-To: m2wpkhec1b.fsf@christianmoe.com
Christian Moe <mail@christianmoe.com> writes:
> Jarmo Hurri writes:
>
>>> and position the different parts as needed with CSS.
>>
>> This is where I don't know what exactly is going to happen. Org writes
>> quite a bit of CSS in each exported HTML file. If I add in, say, a
>> vertical navigation bar, how am I going to control its placement with
>> respect to everything else that is already in the CSS?
>
> Say you put the navbar at the end of the HTML preamble and give it a
> #navbar id (<div id="navbar">). Org already gives the main content a
> #content id. Then this should be all the CSS you need to get started:
>
> #navbar { float: left;
> ...loads more CSS here...
> }
> #content { float: left;
> ...and more CSS here...
> }
Yes indeed, something like this seems to work.
For anyone embarking on a similar trip, a tight placement of the
horizontal title bar on top of the page requires, among other things,
something along the following lines in your CSS:
body
{
margin: 0;
}
All the best,
Jarmo
next prev parent reply other threads:[~2016-07-22 7:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 13:09 Tuning the layout of published html Jarmo Hurri
2016-07-19 13:30 ` Christian Moe
2016-07-19 14:27 ` Jarmo Hurri
2016-07-19 15:49 ` Scott Randby
2016-07-19 18:08 ` Christian Moe
2016-07-22 7:19 ` Jarmo Hurri [this message]
2016-07-19 13:59 ` Robert Klein
2016-07-19 14:28 ` Jarmo Hurri
2016-07-19 14:39 ` Robert Klein
2016-07-19 17:27 ` Scott Randby
2016-07-19 18:33 ` Eric Abrahamsen
2016-07-22 7:17 ` Jarmo Hurri
2016-07-22 12:21 ` Eric Abrahamsen
2016-07-19 14:07 ` Scott Randby
2016-07-19 14:26 ` Marcin Borkowski
[not found] <d8104ff6e802459f95c95f82c799c646@DB5PR01MB1895.eurprd01.prod.exchangelabs.com>
2016-07-19 13:35 ` Eric S Fraga
2016-07-19 13:48 ` Josiah Schwab
2016-07-19 14:35 ` Jarmo Hurri
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=87y44u16n8.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--cc=emacs-orgmode@gnu.org \
/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).