I do this same thing.
In my mind, if TW is my external brain, I should only have one! If
performance was never an issue, one could always just use actually use tags
to completely split content apart, giving you the same workflow as having
separate wikis. I use tags but not so extensively.
I started with numerous micro-wikis. I had too many edge cases where I had
difficulty determining if a tiddler belonged in one or another, and started
finding duplicates with diverging information.
So I decided about a year ago to combine them all. It became a 23 MB file
(with no images), and
Michael,
I also follow the same approach as mine. It is easier to spin up a new wiki
for a particular task. I have a catch-all wiki that pulls in data from
other wikis using the SearchWikis plugin. It is a great piece of work .
The one thing I would really love to have is interwiki linking.
Michael,
Whilst combining wikis has its value, and it takes some time to reach
limits, if you do so carefully they can be easy to pull apart later.
If you have a way to logically keep two wikis separate make use of this
fact and keep it separate, there are plenty of integration options while
I use what you call a monowiki that is approximately 10MB in size with
thousands of tiddlers. As TiddlyTweeter mentioned, extensive use of tags
can slow things down. I use tags only as little as possible. I use fields
for everything else. I also don't embed any images (or very, very few) in
my
Try it and see. If you know what you imported you can always delete it.
TW scales pretty well. A known issue on performance hit is if you use tags
extensively (like tagging hundreds upon hundreds) and use tag tiddlers that
have populated list fields to order those tagged Tiddlers.
FWIW I
6 matches
Mail list logo
