Fossil SCM
Tweaks to the 101-reasons document.
Commit
696ae599c670ce9b21026547bd52a69b23e10208c4a37da27be36f01d0797ec3
Parent
a1e9fe364eb0588…
1 file changed
+11
-4
+11
-4
| --- www/hundredandone.md | ||
| +++ www/hundredandone.md | ||
| @@ -187,10 +187,15 @@ | ||
| 187 | 187 | <https://fossil-scm.org/home/timeline?t=release>. |
| 188 | 188 | |
| 189 | 189 | 1. **Fossil has a built-in wiki**.<p> |
| 190 | 190 | Wiki pages are stored in the same repository file as your code, so that |
| 191 | 191 | they push, pull, sync, and clone together with your code. |
| 192 | + <p> | |
| 193 | + Git does not itself have a wiki. The various Git forges usually add | |
| 194 | + wikis, and store the wiki content in Git, though in a separate | |
| 195 | + Git repository. There is no option to store the wiki and source code | |
| 196 | + together such that they clone and sync as one, in the Git ecosystem. | |
| 192 | 197 | |
| 193 | 198 | 1. **Fossil can associate a wiki page with a particular check-in.**<p> |
| 194 | 199 | Rather than including an oversized check-in comment on an |
| 195 | 200 | important check-in (such as the merge of a big new feature), Fossil |
| 196 | 201 | allows you to assign a wiki page to that check-in. That wiki page |
| @@ -767,18 +772,20 @@ | ||
| 767 | 772 | The current library of skins are mostly derived from custom skins that |
| 768 | 773 | users of Fossil have created over the years and generously donated |
| 769 | 774 | to the project. If none of the default skins work for you, you can |
| 770 | 775 | create your own, perhaps using one of the existing skins as a template. |
| 771 | 776 | |
| 772 | - 1. **Most Fossil web-interface skins include a hamburger (☰) menu.**<p> | |
| 777 | + 1. **Most Fossil web-interface skins include a detailed hamburger | |
| 778 | + (☰) menu.**<p> | |
| 773 | 779 | Clicking on the hamburger menu brings up a dropdown "site-map" |
| 774 | 780 | page that lets you quickly navigate to the information you want. |
| 775 | 781 | (Note: The presence and operation of the hamburger menu is a |
| 776 | 782 | skin-specific feature and might not be available on every skin, but |
| 777 | - it is used on the more popular skins.) Curiously, none of GitHub, | |
| 778 | - GitLab, Gitea, nor Forgejo have a hamburger menu, which in my | |
| 779 | - experience makes those sites harder to navigate. | |
| 783 | + it is used on the more popular skins.) Git itself has nothing like | |
| 784 | + this. The various Git forges sometimes have a limited hamburger | |
| 785 | + menu, that it is not nearly as complete. I find it difficult to | |
| 786 | + locate the screens I want without consulting an AI. | |
| 780 | 787 | |
| 781 | 788 | 1. **The Fossil web interface /sitemap page is responsive to |
| 782 | 789 | individual user permissions and capabilities.**<p> |
| 783 | 790 | Each user on the Fossil web interface, including the special |
| 784 | 791 | user "nobody" used if no login is attempted, has |
| 785 | 792 |
| --- www/hundredandone.md | |
| +++ www/hundredandone.md | |
| @@ -187,10 +187,15 @@ | |
| 187 | <https://fossil-scm.org/home/timeline?t=release>. |
| 188 | |
| 189 | 1. **Fossil has a built-in wiki**.<p> |
| 190 | Wiki pages are stored in the same repository file as your code, so that |
| 191 | they push, pull, sync, and clone together with your code. |
| 192 | |
| 193 | 1. **Fossil can associate a wiki page with a particular check-in.**<p> |
| 194 | Rather than including an oversized check-in comment on an |
| 195 | important check-in (such as the merge of a big new feature), Fossil |
| 196 | allows you to assign a wiki page to that check-in. That wiki page |
| @@ -767,18 +772,20 @@ | |
| 767 | The current library of skins are mostly derived from custom skins that |
| 768 | users of Fossil have created over the years and generously donated |
| 769 | to the project. If none of the default skins work for you, you can |
| 770 | create your own, perhaps using one of the existing skins as a template. |
| 771 | |
| 772 | 1. **Most Fossil web-interface skins include a hamburger (☰) menu.**<p> |
| 773 | Clicking on the hamburger menu brings up a dropdown "site-map" |
| 774 | page that lets you quickly navigate to the information you want. |
| 775 | (Note: The presence and operation of the hamburger menu is a |
| 776 | skin-specific feature and might not be available on every skin, but |
| 777 | it is used on the more popular skins.) Curiously, none of GitHub, |
| 778 | GitLab, Gitea, nor Forgejo have a hamburger menu, which in my |
| 779 | experience makes those sites harder to navigate. |
| 780 | |
| 781 | 1. **The Fossil web interface /sitemap page is responsive to |
| 782 | individual user permissions and capabilities.**<p> |
| 783 | Each user on the Fossil web interface, including the special |
| 784 | user "nobody" used if no login is attempted, has |
| 785 |
| --- www/hundredandone.md | |
| +++ www/hundredandone.md | |
| @@ -187,10 +187,15 @@ | |
| 187 | <https://fossil-scm.org/home/timeline?t=release>. |
| 188 | |
| 189 | 1. **Fossil has a built-in wiki**.<p> |
| 190 | Wiki pages are stored in the same repository file as your code, so that |
| 191 | they push, pull, sync, and clone together with your code. |
| 192 | <p> |
| 193 | Git does not itself have a wiki. The various Git forges usually add |
| 194 | wikis, and store the wiki content in Git, though in a separate |
| 195 | Git repository. There is no option to store the wiki and source code |
| 196 | together such that they clone and sync as one, in the Git ecosystem. |
| 197 | |
| 198 | 1. **Fossil can associate a wiki page with a particular check-in.**<p> |
| 199 | Rather than including an oversized check-in comment on an |
| 200 | important check-in (such as the merge of a big new feature), Fossil |
| 201 | allows you to assign a wiki page to that check-in. That wiki page |
| @@ -767,18 +772,20 @@ | |
| 772 | The current library of skins are mostly derived from custom skins that |
| 773 | users of Fossil have created over the years and generously donated |
| 774 | to the project. If none of the default skins work for you, you can |
| 775 | create your own, perhaps using one of the existing skins as a template. |
| 776 | |
| 777 | 1. **Most Fossil web-interface skins include a detailed hamburger |
| 778 | (☰) menu.**<p> |
| 779 | Clicking on the hamburger menu brings up a dropdown "site-map" |
| 780 | page that lets you quickly navigate to the information you want. |
| 781 | (Note: The presence and operation of the hamburger menu is a |
| 782 | skin-specific feature and might not be available on every skin, but |
| 783 | it is used on the more popular skins.) Git itself has nothing like |
| 784 | this. The various Git forges sometimes have a limited hamburger |
| 785 | menu, that it is not nearly as complete. I find it difficult to |
| 786 | locate the screens I want without consulting an AI. |
| 787 | |
| 788 | 1. **The Fossil web interface /sitemap page is responsive to |
| 789 | individual user permissions and capabilities.**<p> |
| 790 | Each user on the Fossil web interface, including the special |
| 791 | user "nobody" used if no login is attempted, has |
| 792 |