From mboxrd@z Thu Jan  1 00:00:00 1970
From: Melanie Bacou <mel@mbacou.com>
Subject: Re: [ox, patch] Add #+SUBTITLE
Date: Sat, 28 Mar 2015 04:26:19 -0400
Message-ID: <mf5ojj$m73$1@ger.gmane.org>
References: <87a8z7z20k.fsf@gmx.us>
	<87k2y9m77m.fsf@ericabrahamsen.net>	<87oanl6o9j.fsf@gmx.us>
	<877fu8ms0p.fsf@ericabrahamsen.net>	<mevs14$73f$1@ger.gmane.org>
	<87pp7w9jba.fsf@gmx.us> <877fu49h0c.fsf@gmx.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33721)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1Ybm50-0004RL-8E
	for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 04:26:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1Ybm4u-0002uF-F1
	for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 04:26:54 -0400
Received: from plane.gmane.org ([80.91.229.3]:60018)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1Ybm4u-0002tl-3L
	for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 04:26:48 -0400
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1Ybm4r-0004ft-Au
	for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 09:26:45 +0100
Received: from c-69-137-228-217.hsd1.dc.comcast.net ([69.137.228.217])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <emacs-orgmode@gnu.org>; Sat, 28 Mar 2015 09:26:45 +0100
Received: from mel by c-69-137-228-217.hsd1.dc.comcast.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <emacs-orgmode@gnu.org>; Sat, 28 Mar 2015 09:26:45 +0100
In-Reply-To: <877fu49h0c.fsf@gmx.us>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

See inline.

On 3/26/2015 6:42 AM, Rasmus wrote:
> Rasmus <rasmus@gmx.us> writes:
>
>>> <div class="page-header">
>>>    <h1>This would be the title <small>and this the subtitle</small></h1>
>>> </div>
>>>
>>> ref: http://getbootstrap.com/components/#page-header
>
> According to html5doctor.com:
>
>      Note: Some have been advocating of the use of the small element to
>      signify subtitles. This has been under discussion in the HTML working
>      group, but no compelling arguments for its use have been
>      made. Therefore it is not advised to use small to mark up subtitles.
>
> That puts the nail in that coffin. . .

Right, not saying Bootstrap's implementation is pretty. More on Twitter 
Bootstrap (TWBS) though, as this has become one of the easiest and most 
expandable CSS frameworks (due to many contributed plugins). There is an 
existing org export backend for TWBS at 
https://github.com/marsmining/ox-twbs defining a series of TWBS export 
options in `org-export-twbs`.

I found this package very useful because it allows:
- using TWBS default CSS theme, or any other CSS theme found for example 
at https://bootswatch.com/
- using any available TWBS JS plugin to add nifty features, like dynamic 
sidebar (useful for navigating long documents), menubar (when publishing 
more than 1 page), dynamic/sortable tables, etc.
- support code highlighting
- is mobile-ready

Just FYI, but if you use Org to maintain technical documents or publish 
entire websites, this is very useful.


>>> Another commonly seen approach is this (many web CMS use this pseudo
>>> standard):
>>>
>>> <h1 class="title">My Title</h1>
>>> <h2 class="subtitle">My Subtitle</h1>
>>
>> This is basically how it's handled.  I guess you could get the former by
>> writing a custom preamble and disabling title export.
>
> The same page as above leads to this interesting documents, which
> unfortunately has draft in its name.
>
>      http://www.w3.org/html/wg/drafts/html/master/semantics.html#sub-head
>
> It suggests the following:
>
>      <header>
>      <h1>title</h1>
>      <p>subtitle</p>
>      </header>
>
> I really like this one!  This is the HTML5 solution, it seems.  Then this
> could be used for non-HTML5:
>
>      <h1>Ramones <br>
>      <span>Hey! Ho! Let's Go</span>
>      </h1>
>
> WDYT?
>
> —Rasmus
>

I like the HTML5 solution as well, I'd vote for using this one as 
default in ox-html.

I also suggested in an earlier message adding (LaTeX, ODT, and HTML) 
support for the most common meta tags as well (all optional).

The multiple Authors, Emails, and Affiliation are required in quite a 
few LaTeX journal classes, but currently not supported in Org. I'd vote 
for using a similar markup approach as in YAML (with indented new 
lines), e.g.


#+TITLE:          Document Title
#+SUBTITLE:       Document Subtitle
#+DATE:           2015-03-28
#+AUTHOR:         Author 1
                   Author 2
#+EMAIL:          author1@email.com
                   author2@email.com
#+AFFILIATION:    Affiliation 1
                   Affiliation 2
#+CLASSIFICATION: JEL
#+KEYWORDS:       H00, H87, F2, F12
#+DESCRIPTION:    Document description
#+REVISION:       1.0
#+COPYRIGHT:      Right Owner, 2015. All rights reserved.

ox-html could use these extra tags as follows:

<head>
<title>Document Title</title>
<meta name="title" content="Document Title" />
<meta name="date" content="2015-03-28" />
<meta name="author" content="Author 1, Author 2" />
<meta name="keywords" content="JEL: H00, H87, F2, F12" />
<meta name="description" content="Document description" />
<meta name="classification" content="JEL" />
<meta name="copyright" content="Right Owner, 2015. All rights reserved."/>
<meta name="version" content="revision"/>

<meta name="citation_title" content="Document Title" />
<meta name="citation_publication_date" content="2015-03-28" />
<meta name="citation_author" content="Author 1" />
<meta name="citation_author" content="Author 2" />
</head>

<body>

<header>
<h1>Document Title</h1>
<p>Document Subtitle</p>
<p>Revision 1.0, <time datetime="2015-03-28">2015-03-28</time></p>
</header>

<address>
Author 1
<a href="mailto:author1@email.com">author1@email.com</a>
Affiliation 1
</address>

<address>
Author 2
<a href="mailto:author2@email.com">author2@email.com</a>
Affiliation 2
</address>

<div class="classification"><label>Classification</label> JEL: H00, H87, 
F2, F12</div>
<div class="copyright"><label>Copyright</label> Right Owner, 2015. All 
rights reserved.</div>
<div class="description"><label>Description</label> Document 
description</div>

<div class="abstract"><label>Abstract</label> Document abstract</div>

<div class="toc"><label>Contents</label> [TOC]</div>
<div class="toc"><label>Tables</label> [TOC:tables]</div>
<div class="toc"><label>Figures</label> [TOC:figures]</div>
<div class="toc"><label>Equations</label> [TOC:equations]</div>
<div class="toc"><label>Listings</label> [TOC:listings]</div>

[...]


<div class="bibliography">
<h2>References</h2>
[BIBLIOGRAPHY]
</div>

</body>

See ref:
- 
http://dev.w3.org/html5/spec-author-view/the-meta-element.html#the-meta-element
- https://scholar.google.com/intl/en/scholar/inclusion.html#indexing
- http://html5doctor.com/the-address-element/

I'm probably opening Pandora's box here, but in my long experience this 
is the information that's most commonly found or required in any type of 
publication or technical document.

Would be useful to hear others' opinions.

-- 
Melanie BACOU
International Food Policy Research Institute
Snr. Program Manager, HarvestChoice
E-mail m.bacou@cgiar.org
Visit www.harvestchoice.org