tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: Proposed wiki formatting guidelines
Date Wed, 01 Dec 2010 01:53:52 GMT
I prefer the second.

A few other notes.

Method and property names in code font:  {{myProperty}}, {{someMethod()}}

Class names (qualified or not) in default font.

Path names in default font.

First reference to a type on a page should be a link to
http://tapestry.apache.org/current/apidocs/...  (or the component reference)


Use {code} for listings, not {noformat}.

Use {noformat} for console output.

Images and diagrams are small sized thumbnails, centered, no border.

Page names a headings are All Words Captialized

Treat the page title as if an h0. element, and put top level sections within
the page as h1.  If the font size is too large we can fix that using CSS
rather than choosing a header level for visual size.

I'm pretty sure I've been consistent about doing these things on the first
couple of pages of the tutorial.

On Tue, Nov 30, 2010 at 5:36 PM, Bob Harner <bobharner@gmail.com> wrote:

> Style question: Which form of heading capitalization should we used?
>    h2. All Words Capitalized
> or
>    h2. Only the first word capitalized
> The old doc pages seemed to use the first, Wikipedia style guidelines
> require the second. Either is fine with me, but I'm seeing an
> inconsistent mix on the Tapestry pages so far.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org

Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!

(971) 678-5210

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message