Fossil SCM

Reworked the final paragraph of the whyallinone doc to be clearer in pointing out that external web apps can be linked bidirectionally with Fossil.

wyoung 2024-10-26 09:10 trunk
Commit 7d50f6142cc0e925a382b925348c3a190d9ae54ab3796ce24ec1d2c7708a6945
1 file changed +7 -4
--- www/whyallinone.md
+++ www/whyallinone.md
@@ -141,11 +141,11 @@
141141
142142
7. Hosting all of these elements within a single service gives a
143143
consistent look-and-feel across all aspects of the project.
144144
145145
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
147147
in Fossil, and even then, you can’t make independently-developed
148148
software look like it was produced by a single entity without
149149
resorting to heroic levels of customization. If you use a separate
150150
DVCS web front end, chat system, forum manager, documentation
151151
system, ticket tracker, and so on, you are likely to be relegated
@@ -217,16 +217,19 @@
217217
configuration change to its [role-based access control system](./caps/).
218218
When you’re ready to turn these additional features on, you can do so
219219
with a few mouse clicks.
220220
221221
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.
225227
226228
[Discord]: https://discord.com/
227229
[edoc]: ./embeddeddoc.wiki
228230
[Jira]: https://www.atlassian.com/software/jira
229231
[MediaWiki]: https://www.mediawiki.org/
232
+[skinning]: ./customskin.md
230233
[Sphinx]: https://www.sphinx-doc.org/en/master/
231234
[SSO]: https://en.wikipedia.org/wiki/Single_sign-on
232235
[srckl]: https://www.sqlite.org/src/ext/checklist/top/index
233236
--- 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

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button