I visited Wiki today for the first time in several years. Though I've
never used Wiki much, I am always wowed by its simplicity and
elegance.
It reminded me of my hacked version of YukiWiki that I used as an
engine for a collaborative web site for the family reunion back in
2007. It's still working, and even looks OK on a cell phone, though I
haven't touched it in years, either.
These wikis feel so close to what I want for managing and presenting
my commonplace site, I want to reevaluate the posibility of
implementing TIR with further modifications to YukiWiki instead of
continuing original programming.
* TIR functions YukiWiki lacks
- Partitioning document files with directories
+ directory prefix in WikiLinks and [[free links]]:
e.g. dir/WikiPage, [[dir/wiki page]]
(dir hidden in rendered link text)
+ directory content functions (dir, link, exits, files, exclude)
- Database outside web server file tree.
- File name extensions other than ".txt".
- Customizable per-page style sheets.
- Per-page edit permission.
- Integrate edit-locked document and public comments.
- Robot prevention.
- Title format.
- Templates (Text::Template?)
- Imbed images(?)
- Multi-wiki.
I think the last time I considered a solution like this I rejected it
do to the trouble of patching another author's code, but most of the
items on the list above don't sound that hard.
Alternatively, using YukiWiki as a reference point for new program
TirWiki might also be more effective than continuing with all new
code.
