Fossil SCM
Documented the use of $current_page in hand-rolled "body" tags in the customskin doc.
Commit
1864217625ffb56fa2fbd5d1dd26a90edab63c3b4b929ebc535c58cf6962808e
Parent
8ac0830bfce807c…
1 file changed
+13
-1
+13
-1
| --- www/customskin.md | ||
| +++ www/customskin.md | ||
| @@ -84,11 +84,23 @@ | ||
| 84 | 84 | <meta http-equiv="Content-Security-Policy" content="...." /> |
| 85 | 85 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 86 | 86 | <title>....</title> |
| 87 | 87 | <link rel="stylesheet" href="..." type="text/css" /> |
| 88 | 88 | </head> |
| 89 | - <body> | |
| 89 | + <body class="FEATURE"> | |
| 90 | + | |
| 91 | +…where `FEATURE` is either the top-level URL element (e.g. `doc`) or a | |
| 92 | +feature class that groups multiple URLs under a single name such as | |
| 93 | +`forum` to contain `/forummain`, `/forumpost`, `/forume2`, etc. This | |
| 94 | +allows per-feature CSS such as | |
| 95 | + | |
| 96 | + body.forum div.markdown blockquote { | |
| 97 | + margin-left: 10px; | |
| 98 | + } | |
| 99 | + | |
| 100 | +That is, affect HTML `<blockquote>` tags specially only for forum posts | |
| 101 | +written in Markdown, leaving all other block quotes alone. | |
| 90 | 102 | |
| 91 | 103 | In most cases, it is best to leave the Fossil-generated HTML Header |
| 92 | 104 | alone. (One exception is when the administrator needs to include links |
| 93 | 105 | to additional CSS files.) The configurable part of the skin begins |
| 94 | 106 | with the Content Header section which should follow this template: |
| 95 | 107 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -84,11 +84,23 @@ | |
| 84 | <meta http-equiv="Content-Security-Policy" content="...." /> |
| 85 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 86 | <title>....</title> |
| 87 | <link rel="stylesheet" href="..." type="text/css" /> |
| 88 | </head> |
| 89 | <body> |
| 90 | |
| 91 | In most cases, it is best to leave the Fossil-generated HTML Header |
| 92 | alone. (One exception is when the administrator needs to include links |
| 93 | to additional CSS files.) The configurable part of the skin begins |
| 94 | with the Content Header section which should follow this template: |
| 95 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -84,11 +84,23 @@ | |
| 84 | <meta http-equiv="Content-Security-Policy" content="...." /> |
| 85 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 86 | <title>....</title> |
| 87 | <link rel="stylesheet" href="..." type="text/css" /> |
| 88 | </head> |
| 89 | <body class="FEATURE"> |
| 90 | |
| 91 | …where `FEATURE` is either the top-level URL element (e.g. `doc`) or a |
| 92 | feature class that groups multiple URLs under a single name such as |
| 93 | `forum` to contain `/forummain`, `/forumpost`, `/forume2`, etc. This |
| 94 | allows per-feature CSS such as |
| 95 | |
| 96 | body.forum div.markdown blockquote { |
| 97 | margin-left: 10px; |
| 98 | } |
| 99 | |
| 100 | That is, affect HTML `<blockquote>` tags specially only for forum posts |
| 101 | written in Markdown, leaving all other block quotes alone. |
| 102 | |
| 103 | In most cases, it is best to leave the Fossil-generated HTML Header |
| 104 | alone. (One exception is when the administrator needs to include links |
| 105 | to additional CSS files.) The configurable part of the skin begins |
| 106 | with the Content Header section which should follow this template: |
| 107 |