- flat file backend
- support Japanese characters
- shell access
- static rendering
- standard-compliant output
X simple source markup (org or wiki-like)
--> pages are delivered as-is. Only navigation files are
ornamented.
- ?Do I want multiple blogs for family news, technical projects,
etc., or do I want to maintain these as categories within a single
blog?
[Multi-blogs] -> Easier for readers to focus on portion of my
output most interesting to them, but readers of multiple content
partitions will have additional overhead to view everything.
[Categories] -> Easier to monitor all my output, but content type
will be mixed.
[2009-06-30 Tue] Ironic, but though I really like the concept of
Blosxom and several other lightweight blog/CMS engines I've looked
at, I'm becoming reconvinced that finishing TIR will be no more
difficult than customizing any of these others to do what I want.
[2009-07-02 Thu] Do give WebAPP a shot, though. Does it do static
rendering?
* Content management
- Flat category structure: all category directories under single
nexus -> short path to files, category list easily derived from
nexus directory contents.
- OR two-level system with alphabetic directories in nexus and
category directories sorted under initial -> compact directory
listing for shell.
- OR support both of the above, with one dynamicaly generated from
the other -> advantages of both at cost of developing and/or
operating generator program and additional data space.
* Views
- Blog: 1-page reverse-chronological list of recently added or
changed files on site.
- RSS
- Archive: Chronological list of all files on site (divisions?)
- Nexus: All categories
- Category room: List category contents and intra-site links like MUD
room.
- Blinks
- Category index: partitioned alphabetically
- Page index: by name or title (alphabetic partitions?)
- Gopher hole
* Navigation bar
- Nexus/Home
- Blog
-- Archives
- Indices/Site map
-- Category index
-- File index
- Blinks/Links
- Mirror
-- Gopher
- About
- Contact
* Blosxom standard views
Reverse-chronological list of text files on site, or year, month,
day, or directory path subset. Files listed per page and path search
depth settable per blog.
Problem is I don't need or want a blog view of every node in the
content tree. One site-wide blog with archive is enough.
