Plone Blog notes 0.1 2007-03-01T0524

1. spam

think it displays all recent comments with tickboxes to delete spam more easily.

not sure if same for trackback spam.

if not may be desirable to use a link for list of trackbacks instead of showing them together with the main entry (or may already do that)

see:

trackback spam

comment spam

there is some file that can block urls in each current trackback spam wave so may be sufficient to just know how to edit that.

for comment spam delete the members and block their email addresses (simple - disallow duplicate email address and disable spam member instead of deleting spam member - so cannot use same email address again)

1. google analytics available as product (make available to reveiwers+ only)
2. delicious etc available as product PloneBookmarklets - essential
3. test with latest zope, plone and quills 1.5rc3. by the time familiar enough with it and associated products and other config 1.5 final may be released. if not it will provide migration from 0.9 when ready and problems discovered can be entered into their issue tracker to speed fixing.

should be ok

though multiple authors might be broken at the moment.

1. if unsatisfactory could look at Coreblog i haven't checked but looks unlikely to be better.
2. major performance issues are likely when site takes off. am assuming we would just pay to cope rather than considering drupal etc.
3. get a subdomain name pointing to your ip so can let others look/play while working on tests eg:

test1.lastsuperpower.net (keza)

test2.lastsuperpower.net (djm)

essential for playing with permissions, trackbacks and spam filters.

1. tagcloudsexplorer (included) is nice.

disciplined use of keywords and keyword combinations essential. requires folder structure. can be combined with separate navigable dynamic folders/tabs and category searches on non-weblog stuff.

1. also look at qPloneBlog worth looking at anyway for better understanding even if quills is the one chosen
2. do NOT make either of them main page eg use test1.lastsuperpower.net/blog/ for quills and test1.lastsuperpower.net/blog2/ for qPloneBloc (similar flexibility required on production site).
3. suspect production will be to zope 2.8 or 2.9 if possible and run cmfboard (closed) for access to old threads and PloneBoard for internal discussion fora etc but i haven't checked versions etc.
4. if necessary could run separate zope instance for existing closed cmfboard and rest of site on current version to avoid migration issues.
5. if necessary could have entirely different software for blogs and forums still under same domain name. requires common member logon only.
6. try using performancing