search

TiddlyWiki / TiddlyWikiClassic

TiddlyWiki Classic (not to be confused with TiddlyWiki5: https://github.com/Jermolene/TiddlyWiki5)
https://classic.tiddlywiki.com/
492 stars 114 forks source link

docs: improve Advanced download options #262

Closed markkerrigan closed 4 years ago

markkerrigan commented 4 years ago

Add link to [[Setting up saving]] and de-emphasize TiddlySaver info

YakovL commented 4 years ago

Hi Mark, these are fine suggestions, but remember, deleting a tiddler without changing split.recipe will break building the TW of the site, so this should be fixed in the same PR.

I also suggest to create separate PRs for changes unrelated one to the other, since those are easier to review and merge (and if something blocks immediate merge, others can still be merged).

Finally, a note for myself, for safer deleting of some tiddlers, RenameTiddlersPlugin may be installed or a similar one can be created.

markkerrigan commented 4 years ago

somehow I didn't see the iPhone.tid in the split recipe initially. I will see if multiple PR can reference the same patch in my own personal fork as I'm trying not to create multiple patch branches.

YakovL commented 4 years ago

Right, ready to merge I guess. Good call about simplifying the download thing.

The awkward bit is, systemServer is not referenced anywhere, nor is any of the tagged servers and the merged content is still not very visible. At some point it will be useful to create a list of extensions repositories somewhere and these systemServer-tagged tiddlers may be a good starting point (although the list is now far from being complete/comprehensive). For instance, it doesn't list Tobias' repository(ies): https://github.com/tobibeer/TiddlyWikiPlugins http://web.archive.org/web/20140803030727/http://tobibeer.tiddlyspace.com/ or lewcid (http://tiddlywiki.squize.org/ → http://lewcid.tiddlyspace.com/ → [web archive or may be available somewhere at github]) Many are listed at the old customize space (this is from my small collection of TS backups) Just some thoughts for the future.

YakovL commented 4 years ago

I'm trying not to create multiple patch branches

why so? This is actually a proper workflow for git (one branch per one "feature")