[tw5] Re: Monowikis vs. Microwikis
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. On Wednesday, June 10, 2020 at 8:42:59 PM UTC-5, Damon Pritchett wrote: > > 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 wiki. I use external links instead. > > Hope this helps. > > Damon > > On Wednesday, June 10, 2020 at 1:18:39 PM UTC-7, Michael McDermott wrote: >> >> I'm sure this has come up before, but what are the downsides to keeping >> one large wiki vs. several smaller ones? I mostly use mine as a sort of >> commonplace book and have two wikis, one that is related to work (technical >> stuff + project notes) and the other that is everything else of interest. >> I've been considering merging them together and the couldn't really think >> of a reason not to. >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/63c21fdd-fa25-41e4-a12f-6ca32713f56fo%40googlegroups.com.
[tw5] Re: Monowikis vs. Microwikis
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 takes about 8 seconds to save (too long for me). As my coding skills improve I have used tags and lists extensively (such as `<$list filter=[all[current]tagging[]!tag[Topic]!sort[modified]] template=IncTemplate/>`) where IncTemplate is a macro I created that places the target inside a checkbox. Thankfully "AdvancedSearch" has a filter tab that lets me export (as JSON) a file that quickly populates a new purpose-built wiki. In short, I have pendulum swung to both extremes of your question. My current state is to have a massive wiki (21MB) and am breaking out smaller wikis when I am comfortable that the line of separation is clearly demarcated (in my mind) to I do not have to search in more than one location. I need to research the plugin mentioned above in this thread... JWHoneycutt -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a55df684-085a-411c-b661-57e43e98b585o%40googlegroups.com.
[tw5] Re: Monowikis vs. Microwikis
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. If I could
pull in tiddlers from my commonplace book with something like
{{quote>TITLE}} in a different tiddler.It could also extend this to the
SearchWikis plugin like pulling in the updated index whenever I open my
main wiki.
Regards,
Xavier
On Thursday, 11 June 2020 07:28:51 UTC+5:30, TW Tones wrote:
>
> 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
> keeping them separate. Tiddlywikis work well as smart documents as well.
>
> I have a large consolidated personal organiser but I am now starting to
> move projects or clients out to their own wiki because I can customise and
> grow them further without overlapping the functionality of the key wiki,
> however I keep project metadata in the key wkii to drive regular reviews
> and project level time frames, but the project wiki has all the detail.
> Having a wiki edition for say project makes creating a new project easier.
>
> In my tiddlywiki development suite I have dozens if not hundreds of wikis,
> usually created to some "end" in particular, or subject, once the activity
> comes to a close the essence is extracted and packaged and the original
> wiki archived. I then place the result in a consolidated wiki.
>
> Integrations
>
>- Jeds bob wiki has a number of integrations will all its child wikis,
>whilst I place dev wikis under it, one consolidates resources which I drag
>to the wiki in use, eg images, icons.
>- another has all the plugins I come across, another my business plan,
>another social media content in writing
>- Mohammad's indexing solution .
>https://kookma.github.io/TW-Searchwikis/ is a great advance for
>integration, even fo0r single file wikis, you can include locally
>searchable content that comes from another wiki, with links to that
> content.
>- TiddlyWikis versatility allows numerous integrations and
>interactions at a designer and user perspective you can make almost
>anything as an integration
> - Eg you can drag and drop between one wiki and another in an
> iframe in the current wiki.
>
> Regards
> tony
>
>
> On Thursday, June 11, 2020 at 6:18:39 AM UTC+10, Michael McDermott wrote:
>>
>> I'm sure this has come up before, but what are the downsides to keeping
>> one large wiki vs. several smaller ones? I mostly use mine as a sort of
>> commonplace book and have two wikis, one that is related to work (technical
>> stuff + project notes) and the other that is everything else of interest.
>> I've been considering merging them together and the couldn't really think
>> of a reason not to.
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/11252774-0c9c-4b25-b8a5-28fbe6a21f32o%40googlegroups.com.
[tw5] Re: Monowikis vs. Microwikis
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 keeping them separate. Tiddlywikis work well as smart documents as well. I have a large consolidated personal organiser but I am now starting to move projects or clients out to their own wiki because I can customise and grow them further without overlapping the functionality of the key wiki, however I keep project metadata in the key wkii to drive regular reviews and project level time frames, but the project wiki has all the detail. Having a wiki edition for say project makes creating a new project easier. In my tiddlywiki development suite I have dozens if not hundreds of wikis, usually created to some "end" in particular, or subject, once the activity comes to a close the essence is extracted and packaged and the original wiki archived. I then place the result in a consolidated wiki. Integrations - Jeds bob wiki has a number of integrations will all its child wikis, whilst I place dev wikis under it, one consolidates resources which I drag to the wiki in use, eg images, icons. - another has all the plugins I come across, another my business plan, another social media content in writing - Mohammad's indexing solution .https://kookma.github.io/TW-Searchwikis/ is a great advance for integration, even fo0r single file wikis, you can include locally searchable content that comes from another wiki, with links to that content. - TiddlyWikis versatility allows numerous integrations and interactions at a designer and user perspective you can make almost anything as an integration - Eg you can drag and drop between one wiki and another in an iframe in the current wiki. Regards tony On Thursday, June 11, 2020 at 6:18:39 AM UTC+10, Michael McDermott wrote: > > I'm sure this has come up before, but what are the downsides to keeping > one large wiki vs. several smaller ones? I mostly use mine as a sort of > commonplace book and have two wikis, one that is related to work (technical > stuff + project notes) and the other that is everything else of interest. > I've been considering merging them together and the couldn't really think > of a reason not to. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/402b5d89-9965-40f1-a42b-32c0d346fb88o%40googlegroups.com.
[tw5] Re: Monowikis vs. Microwikis
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 wiki. I use external links instead. Hope this helps. Damon On Wednesday, June 10, 2020 at 1:18:39 PM UTC-7, Michael McDermott wrote: > > I'm sure this has come up before, but what are the downsides to keeping > one large wiki vs. several smaller ones? I mostly use mine as a sort of > commonplace book and have two wikis, one that is related to work (technical > stuff + project notes) and the other that is everything else of interest. > I've been considering merging them together and the couldn't really think > of a reason not to. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d6a28535-661e-48bf-9284-ca177089a244o%40googlegroups.com.
[tw5] Re: Monowikis vs. Microwikis
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 often combine wiki, just make share I use a consistent Tiddler naming system so I can easily identify what to export if things got slow. Rarely happened to me. TT On Wednesday, 10 June 2020 22:18:39 UTC+2, Michael McDermott wrote: > > I'm sure this has come up before, but what are the downsides to keeping > one large wiki vs. several smaller ones? I mostly use mine as a sort of > commonplace book and have two wikis, one that is related to work (technical > stuff + project notes) and the other that is everything else of interest. > I've been considering merging them together and the couldn't really think > of a reason not to. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0a77bdf7-011f-44af-8698-da087000d6fco%40googlegroups.com.
