Fossil SCM
Tightened up a paragraph in point 8 of the new whyallinone doc to be less redundant, both within itself and with respect to the surrounding material.
Commit
216ef76e701e22a7fa78836de0499689137cc9baa2c194ace1aaa03e6fcc042b
Parent
5e12c6251658ba1…
1 file changed
+3
-5
+3
-5
| --- www/whyallinone.md | ||
| +++ www/whyallinone.md | ||
| @@ -164,15 +164,13 @@ | ||
| 164 | 164 | to simply matching colors and fonts; you *might* also get the |
| 165 | 165 | ability to add a common logo to the header of all of these |
| 166 | 166 | independent pieces. The pieces won’t look unified, because they |
| 167 | 167 | weren’t developed that way. |
| 168 | 168 | |
| 169 | - The Fossil project, being a unified software development effort, | |
| 170 | - not only offers a unified web UI design, it gives you a common | |
| 171 | - skinning system for all of its elements so that if you want to | |
| 172 | - customize its appearance, your improvements affect all elements of | |
| 173 | - Fossil. | |
| 169 | + The Fossil project’s | |
| 170 | + skinning system lets you affect all of its elements globally from the | |
| 171 | + single skin editor. | |
| 174 | 172 | |
| 175 | 173 | Or not: there’s a feature in Fossil that lets skin customizations |
| 176 | 174 | apply to only *some* Fossil features. The initial impetus behind |
| 177 | 175 | this feature was that one of our users wanted Markdown to be |
| 178 | 176 | rendered with different indentation in forum posts than in |
| 179 | 177 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -164,15 +164,13 @@ | |
| 164 | to simply matching colors and fonts; you *might* also get the |
| 165 | ability to add a common logo to the header of all of these |
| 166 | independent pieces. The pieces won’t look unified, because they |
| 167 | weren’t developed that way. |
| 168 | |
| 169 | The Fossil project, being a unified software development effort, |
| 170 | not only offers a unified web UI design, it gives you a common |
| 171 | skinning system for all of its elements so that if you want to |
| 172 | customize its appearance, your improvements affect all elements of |
| 173 | Fossil. |
| 174 | |
| 175 | Or not: there’s a feature in Fossil that lets skin customizations |
| 176 | apply to only *some* Fossil features. The initial impetus behind |
| 177 | this feature was that one of our users wanted Markdown to be |
| 178 | rendered with different indentation in forum posts than in |
| 179 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -164,15 +164,13 @@ | |
| 164 | to simply matching colors and fonts; you *might* also get the |
| 165 | ability to add a common logo to the header of all of these |
| 166 | independent pieces. The pieces won’t look unified, because they |
| 167 | weren’t developed that way. |
| 168 | |
| 169 | The Fossil project’s |
| 170 | skinning system lets you affect all of its elements globally from the |
| 171 | single skin editor. |
| 172 | |
| 173 | Or not: there’s a feature in Fossil that lets skin customizations |
| 174 | apply to only *some* Fossil features. The initial impetus behind |
| 175 | this feature was that one of our users wanted Markdown to be |
| 176 | rendered with different indentation in forum posts than in |
| 177 |