Fossil SCM
Merge whyallinone.md from trunk.
Commit
31b8605e08be817f20455657f1d9fa4ad44003422138afae23cbad8f8ef40592
Parent
0af46e5dc8c2de1…
1 file changed
+7
-4
+7
-4
| --- www/whyallinone.md | ||
| +++ www/whyallinone.md | ||
| @@ -141,11 +141,11 @@ | ||
| 141 | 141 | |
| 142 | 142 | 7. Hosting all of these elements within a single service gives a |
| 143 | 143 | consistent look-and-feel across all aspects of the project. |
| 144 | 144 | |
| 145 | 145 | Skinning independent software packages’ web interfaces to make |
| 146 | - them appear unified is more work than skinning everything once, as | |
| 146 | + them appear unified is more work than [skinning] everything once, as | |
| 147 | 147 | in Fossil, and even then, you can’t make independently-developed |
| 148 | 148 | software look like it was produced by a single entity without |
| 149 | 149 | resorting to heroic levels of customization. If you use a separate |
| 150 | 150 | DVCS web front end, chat system, forum manager, documentation |
| 151 | 151 | system, ticket tracker, and so on, you are likely to be relegated |
| @@ -217,16 +217,19 @@ | ||
| 217 | 217 | configuration change to its [role-based access control system](./caps/). |
| 218 | 218 | When you’re ready to turn these additional features on, you can do so |
| 219 | 219 | with a few mouse clicks. |
| 220 | 220 | |
| 221 | 221 | Because Fossil is web-native out of the box, if you’ve delegated these |
| 222 | -features to outside systems to flesh out Git’s DVCS-only nature, Fossil | |
| 223 | -can link out to these systems, and they back into Fossil, letting you | |
| 224 | -use Fossil in the same DVCS-only mode. | |
| 222 | +features to outside systems to flesh out Git’s DVCS-only nature, you are | |
| 223 | +free to do the same with Fossil. One of the many things the [skinning] | |
| 224 | +facility allows is replacing the built-in links to the wiki, forum, | |
| 225 | +ticket system, etc. with links to external systems. How easy those | |
| 226 | +systems make it to link back into Fossil is up to their developers. | |
| 225 | 227 | |
| 226 | 228 | [Discord]: https://discord.com/ |
| 227 | 229 | [edoc]: ./embeddeddoc.wiki |
| 228 | 230 | [Jira]: https://www.atlassian.com/software/jira |
| 229 | 231 | [MediaWiki]: https://www.mediawiki.org/ |
| 232 | +[skinning]: ./customskin.md | |
| 230 | 233 | [Sphinx]: https://www.sphinx-doc.org/en/master/ |
| 231 | 234 | [SSO]: https://en.wikipedia.org/wiki/Single_sign-on |
| 232 | 235 | [srckl]: https://www.sqlite.org/src/ext/checklist/top/index |
| 233 | 236 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -141,11 +141,11 @@ | |
| 141 | |
| 142 | 7. Hosting all of these elements within a single service gives a |
| 143 | consistent look-and-feel across all aspects of the project. |
| 144 | |
| 145 | Skinning independent software packages’ web interfaces to make |
| 146 | them appear unified is more work than skinning everything once, as |
| 147 | in Fossil, and even then, you can’t make independently-developed |
| 148 | software look like it was produced by a single entity without |
| 149 | resorting to heroic levels of customization. If you use a separate |
| 150 | DVCS web front end, chat system, forum manager, documentation |
| 151 | system, ticket tracker, and so on, you are likely to be relegated |
| @@ -217,16 +217,19 @@ | |
| 217 | configuration change to its [role-based access control system](./caps/). |
| 218 | When you’re ready to turn these additional features on, you can do so |
| 219 | with a few mouse clicks. |
| 220 | |
| 221 | Because Fossil is web-native out of the box, if you’ve delegated these |
| 222 | features to outside systems to flesh out Git’s DVCS-only nature, Fossil |
| 223 | can link out to these systems, and they back into Fossil, letting you |
| 224 | use Fossil in the same DVCS-only mode. |
| 225 | |
| 226 | [Discord]: https://discord.com/ |
| 227 | [edoc]: ./embeddeddoc.wiki |
| 228 | [Jira]: https://www.atlassian.com/software/jira |
| 229 | [MediaWiki]: https://www.mediawiki.org/ |
| 230 | [Sphinx]: https://www.sphinx-doc.org/en/master/ |
| 231 | [SSO]: https://en.wikipedia.org/wiki/Single_sign-on |
| 232 | [srckl]: https://www.sqlite.org/src/ext/checklist/top/index |
| 233 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -141,11 +141,11 @@ | |
| 141 | |
| 142 | 7. Hosting all of these elements within a single service gives a |
| 143 | consistent look-and-feel across all aspects of the project. |
| 144 | |
| 145 | Skinning independent software packages’ web interfaces to make |
| 146 | them appear unified is more work than [skinning] everything once, as |
| 147 | in Fossil, and even then, you can’t make independently-developed |
| 148 | software look like it was produced by a single entity without |
| 149 | resorting to heroic levels of customization. If you use a separate |
| 150 | DVCS web front end, chat system, forum manager, documentation |
| 151 | system, ticket tracker, and so on, you are likely to be relegated |
| @@ -217,16 +217,19 @@ | |
| 217 | configuration change to its [role-based access control system](./caps/). |
| 218 | When you’re ready to turn these additional features on, you can do so |
| 219 | with a few mouse clicks. |
| 220 | |
| 221 | Because Fossil is web-native out of the box, if you’ve delegated these |
| 222 | features to outside systems to flesh out Git’s DVCS-only nature, you are |
| 223 | free to do the same with Fossil. One of the many things the [skinning] |
| 224 | facility allows is replacing the built-in links to the wiki, forum, |
| 225 | ticket system, etc. with links to external systems. How easy those |
| 226 | systems make it to link back into Fossil is up to their developers. |
| 227 | |
| 228 | [Discord]: https://discord.com/ |
| 229 | [edoc]: ./embeddeddoc.wiki |
| 230 | [Jira]: https://www.atlassian.com/software/jira |
| 231 | [MediaWiki]: https://www.mediawiki.org/ |
| 232 | [skinning]: ./customskin.md |
| 233 | [Sphinx]: https://www.sphinx-doc.org/en/master/ |
| 234 | [SSO]: https://en.wikipedia.org/wiki/Single_sign-on |
| 235 | [srckl]: https://www.sqlite.org/src/ext/checklist/top/index |
| 236 |