Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Questions / Feature Requests (maybe)... seeing what I can do with MWS compared with what i did with TWS

Aperta
  • Qualcosa non va?
#147 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

Start by reading the MultiWikiServer documentation and its existing wiki configuration and plugin handling entry points; the issue does not name files or tests. Compare the requested plugin stores, shared files, included wiki templates, and tag based organization with what the project supports. Done would require clarifying which capabilities are missing and defining their scope; this issue alone does not identify a specific change or completion test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Question on MWS compared with what I was doing in TWS
a lot of this is wrapped in rpg management because that is what I was using it for, could apply to uses in a lot of wikis types
i could have made the questions more generic but I used what I know

Trying to figure out if MWS would work with my projects workflow.
Basically is this possible? Is this something that would work now or will come later?

PluginStore...
In TiddlyServer I had a folder "MyPluginStore"
I did "twplugins='./wikis/MyPluginStore'" in my "start.sh" file.
All I had to do was put the plugin in the "MyPluginStore" folder under the correct name space.
Then in the Wiki's "tiddlywiki.info" I wanted to use that plugin I just included the correct name space under plugins.

MyPlugins...
In TiddlyServer I had a folder MyCustomPlugins.
I had one wiki for each plugin or plugin family with documentation and tests.
I then did "twplugins+=':./wikis/MyCustomPlugins/FieldRunnerPlugin/plugins'" in my "start.sh" for each custom plugin that I would require.
Then in the Wiki's "tiddlywiki.info" I wanted to use that plugin I just included the correct name space under plugins.

Unattached shared .tid and .json...
In TiddlyServer I used "FileSystemPaths" to direct the output of certain tagged tiddlers into a common shared folder in my wikis folder.
Mostly just .json tiddlers.
Before I figured out how to use the FileSystemPaths I moved them by hand.
Another reason for moving them by hand was I created a lot, A LOT, of them before understanding shares as well.

WikiTemplate...
My own designation for a Wiki that had the default look and feel I wanted along with some common css, and by default the settings I had made on that wiki.
All my later wikis pulled this wiki in first using "includeWikis". Any time I wanted to make a change I changed the WikiTemplate and refreshed the server, changes would then be reflected on the wikis unless of course I messed up and had changed something on the target wikis... that was fun figuring out at times where I had overrrided the included wiki.

I had even created a bit of a hierarchy (a inheritance of included wikis)...
with a BaseTemplate wiki
A CampaignTemplate that pulled in "includeWikis" the BaseTemplate than had things custom to displaying campaigns
A ManualTemplate that pulled in "includeWikis" the BaseTemplate and again was customized for diplaying manuals.
Then My wikis would load "includeWikis" one of the three templates.

Organizing tiddlers...
Guessing this one would be a given for being able to pull just specific tagged tiddlers from other wikis but asking to clarify.
I used "FileSystemPaths" to organize tiddlers in wikis under folders and subfolders based on tags.
I mean the tags were already there and used for sorting and such why not use them to organize the folder structure.
End result I could use the "shared" folder and the "tiddlywiki.files" using "directories" to point to all the "monster folder" or the subfolder "undead" or to the sub-subfolder "skeleton", as an example. I could cast a wide net or be specific on what was available in the wiki accessing the shares.
This worked well for dealing with NPC wikis, especially with versions of NPC's where the NPC grows over a campaign. Then monsters, items, etc. etc.

Ultimately when I needed a module wiki for a game I would save out a standalone wiki and everything was wrapped up in a neat ready to use stand alone wiki. I think the worst case scenario I ran into was I had to drag drop some plugins into the stand alone wiki, I may have fixed that though because I do not remember it being a problem later on.

Thanks, frakier
And sorry to be a pain.

Lingua principale
TypeScript
Stelle
60
Fork
17
Merge medio
4m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TiddlyWiki/MultiWikiServer

Tutte le issue di TiddlyWiki/MultiWikiServer

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.