This is a simple list of possible changes to BSE.
+Some of these I'll do myself.
+
=over
=item *
-all some sort of id to be used to identify articles (rather than numbers)
+add some sort of id to be used to identify articles (rather than
+numbers) for use in templates. Possibly they could automatically be
+added as tag names too. So if shop were defined as article 3, then
+you could do:
+
+ <a href="<:url shop:>"><:shop title:></a>
+
+to get a shop link instead of:
+
+ <a href="/shop/">The blah blah Shop</a>
+
+since the first would be more maintainable. This could be useful for
+other special articles.
=item *
=item *
-move the distribution into my local CVS repository, RCS is annoying
+use a proper config file - this is getting more important
+
+=item *
+
+automated way of updating the links for articles that include $SECURLBASE
+
+=item *
+
+move RSS template out of common (this has some other issues though)
+
+=item *
+
+some way of showing expired/hidden articles in browse mode
+
+=item *
+
+support for other embedable 'image' types such as flash and quicktime.
+
+Preferably this would be extendable. We need some way to get size
+information too (entry from the user I suppose, this could also be
+used to override image sizes.)
+
+=item *
+
+move most of the shop.pl code into modules to make it more accessible
+from other scripts (especially for custom card payment.) The first
+steps towards this have been made, see BSE::Util::Shop. The shop.pl
+code will be modified to use these functions.
+
+=item *
+
+make the shopadmin product list better. The nested catalog display
+sucks, especially in Netscape. Some possible options:
+
+=over
+
+=item *
+
+make it act like some tree controls - with expanding and unexpanding
+subtrees
+
+=item *
+
+we have a mix of buttons and links, maybe they should all be links
+
+=item *
+
+sometimes the tree structure isn't clear - either some way of
+presenting lines making the tree, or some other method, like nested
+boxes (using tables?) to show the tree structure.
+
+=back
+
+=item *
+
+better handling of title images? the ability to call a generator function
+or script? (cool use for Imager. :)
+
+=item *
+
+some form of error handling that deals well with IIS' broken handling
+of STDERR. Sometimes it seems to drop it, sometimes it seems to write
+it to the web page.
+
+This is especially a problem for errors in the mail sending code,
+since these can fail when an invalid address is supplied.
+
+=item *
+
+document the body tags
+
+=item *
+
+more general access to the date tag from the search page (maybe with
+more formatting options)
+
+=item *
+
+a central image repository, so images can be shared between articles
+
+=item *
+
+table editor
+
+=item *
+
+change makeIndex.pl to avoid overflowing the fields
+
+=item *
+
+add a test suite
=item *
-use a proper config file
+level parameter to add.pl isn't checked for validity
=back
-=cut
\ No newline at end of file
+=cut