Nota bene: the manual pages have not been updated
completely from the prototyped version to the current version.
To do
priorities
- Comment management / comment notices.
- Fix disconnect between session user and db user.
- Fix potential for circular comment threads and
categories. _not_self_parent is insufficient b/c it's only one
level deep.
- Backup or db-dump system.
- Migrate from Class::DBI to Rose::DB or DBIx::Class. This is pretty far
down the road however b/c Class::DBI is boss, it just isn't as fast as
possible and is harder to do complex queries with.
- Editor/etc should have site favicon.
- Seriously reconsider /aux strategy. Why split site that way? Better to
do it like WP with child/parent stand alone pages.
- Along those lines. Images should be in the DB. That's it, end of
story. Otherwise management is ridiculous.
- Instructions for Google ads.
- Post form should have a browser (with pager) as well as the search.
- Post form should show a publish calendar too.
- /cat/cat%20name for browsing those only.
- /auth/author for same.
- Recommended robots.txt using the EGO_CUSTOM.
- User setting for splash page (aux/home) or else forward to /post once
site is configured.
- Add the screenplay.css but leave it out of the mix.
- Break sidebar css into its own file?
- Collapse malicious comments (no empty block tags, no more than one
consecutive br. Check length. 2K?
- Ad stuff.
- Amazon plugin. Probably XSLT/XML is the way to go here to avoid all
the mushy SOAP stuff.
- Subscribe to comments, so you get mailed new comments as they are
added to a particular post? Only direct replies. All comments.
- Upload for posts.
- Debug mode turned on by a URI change? that writes out path, var, and
template info to screen, drill down clicks.
- Private link lists...?
- Spam proof referrer page by doing a per referrer check back for the
link and then saving it as a valid referrer in the DB.
- XHTML::Allowed SHOULD strip empty tags and pointless repetition but it
might have to move to HTML::TreeBuilder to do this reasonably...?
Manually instead with a substitution at the end?
- Comment limits by count or by date?
- Have a tag that does '|html' so that users don't have to.
Link to daily from post form is busted.
- make enpara into a parser, it's not smart enough right now
- Impose char limit on comments!
- Collapse bad spacing in comments.
- Consider letting those post images which are served from the same
domain as their email?
- Gravatars?
- Ask TT list about post processing so asins may be curried and queried
in 10s.
- Down the road: Catalyst::Plugin::Authentication
Done
- A tool that shows all diffs and undifferentiated files for the
EGO_CUSTOM vs the /default.
- Categories. (However I believe this is the wrong way to go. It should
be more oriented toward a tag taxonomy.)
- Don't let "not live" items show in year view.
- Post preview.
- Page of newest comments.
- RSS.
Post form feedback is not plugged in correctly--500s on problems.
Wishlist
$c->response->content_type('application/xhtml+xml');
- Image uploader, trimmer, downsizer, optimizer, filer. Image notes.
- Link management. So that all links come through one URI but which
accurately set the referrer and can be configured with things like
"external" so that the site in question doesn't get a search engine
bump. Would also let you track your own clicks to see what you never
visit or visit often.
- Standardized comment categories... (absolute id but renamable within
synonyms for the topic)? Whose taxonomy? Categorization is difficult
but valuable. Users won't do it when it's not easy. This makes it easy
and pan net.
- TAGS directive in all default templates to allow user to set their own
via the config if they prefer another style.
- Post stats. Posts per day. Per user, etc.
- Wikiwyg.
- Banned/trusted IPs for comments too? As the referrer stuff?
- Utility script to spell-check whole document tree.
- Utility script to validate classes in all present documents.
- Utility to validate all links in entire site.
- Utility to validate XHTML per page.
- Easy drafting and priority stuff...? So that you can start a piece and
not have it get buried. Track what you're working on in "draft."
- Errors redirect? So that you can't repost and error?
- Controller to edit any tt file by showing the default or the custom if
there is one with highlighted markup and a textarea. Would also be a
simple browser for all the files.
Master class of regexes matching possible errors to provide directed
and clear feedback about error amelioration. Mostly done.
- Put Catalyst.log.debug() messages into incorrectly used templates...?
Where HTML comments currently are.
- Acronym helper/inserter.
- Podcast support?
- Email to post. (PGP signed mail?)