diff options
| -rw-r--r-- | doc/todo/Option_to_make_title_an_h1__63__.mdwn | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/todo/Option_to_make_title_an_h1__63__.mdwn b/doc/todo/Option_to_make_title_an_h1__63__.mdwn index 6673d7f24..b54934948 100644 --- a/doc/todo/Option_to_make_title_an_h1__63__.mdwn +++ b/doc/todo/Option_to_make_title_an_h1__63__.mdwn @@ -1 +1,6 @@ -Currently, the page title (either the name of the page or the title specified with `\[[meta title="..."]]`) shows up in a `<div class="header">`. I tend to follow the [w3c guideline recommending the use of h1 for the title](http://www.w3.org/QA/Tips/Use_h1_for_Title); for this purpose, how about an option to make the page title an `<h1 class="header">`, and shift the markdown headings down by one (making # an h2, ## an h3, etc; or alternatively making # equivalent to `\[[meta title="..."]]`)?
\ No newline at end of file +Currently, the page title (either the name of the page or the title specified with `\[[meta title="..."]]`) shows up in a `<div class="header">`. I tend to follow the [w3c guideline recommending the use of h1 for the title](http://www.w3.org/QA/Tips/Use_h1_for_Title); for this purpose, how about an option to make the page title an `<h1 class="header">`, and shift the markdown headings down by one (making # an h2, ## an h3, etc; or alternatively making # equivalent to `\[[meta title="..."]]`)? + +> The reason I don't use a h1 for the navbar is that while it incorporates +> the page title, it's not just a page title, it has the links to parent pages. +> I also don't want to get in the business of munging up markdown's semantics. This +> way, # is reserved for h1 if you choose to use headers in your page. --[[Joey]]
\ No newline at end of file |